Techniques for scheduling passive internet of things communications

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may send a passive Internet of Things (IoT) traffic report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The UE may receive a scheduling grant from a network entity in response to the passive IoT traffic report. The scheduling grant may indicate a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices. Thus, the UE may perform the set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant. The techniques described herein may enable the UE to perform passive IoT communications with less signal collisions and lower communications resource overhead.

Description

Technical Field

[0001] The following relates to wireless communications, including techniques for scheduling passive Internet of Things (IoT) communications. Background Art

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

[0003] Some wireless communication systems may support NR communications as well as Internet of Things (IoT) communications. However, in some cases, NR communications and IoT communications may utilize different waveforms or modulation schemes, which may increase the complexity of scheduling NR communications and IoT communications in the same radio frequency (RF) band. Summary of the invention

[0004] The described technology relates to improved methods, systems, devices and apparatuses that support technology for scheduling passive Internet of Things (IoT) communications. For example, the described technology provides for scheduling passive IoT communications with higher efficiency and lower communication resource overhead. According to the technology described herein, a user equipment (UE) may send a passive IoT service report, which indicates a passive IoT communication set to be performed between the UE and one or more passive IoT devices. The UE may receive a scheduling grant from a network entity in response to the passive IoT service report. The scheduling grant may indicate a set of time and frequency resources allocated for the passive IoT communication set between the UE and the one or more passive IoT devices. Therefore, the UE may perform the passive IoT communication set with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant. The technology described herein may enable the UE to perform a passive IoT communication set with fewer signal conflicts and lower communication resource overhead, as well as other benefits.

[0005] A method for wireless communication at a UE is described. The method may include sending a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices; receiving a scheduling grant based on the passive IoT service report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices; and performing the set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and a memory (e.g., operatively, communicatively, functionally, electronically, or electrically) coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to perform the following operations: send a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices; receive a scheduling grant based on the passive IoT service report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices; and perform the set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include means for sending a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices; means for receiving a scheduling grant based on the passive IoT service report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices; and means for performing the set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to cause the UE to perform the following operations: send a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices; receive a scheduling grant based on the passive IoT service report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices; and perform the set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a passive IoT traffic report may include operations, features, components, or instructions for: signaling a number of one or more passive IoT devices in the passive IoT traffic report.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a quantity of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to a quantity signaled by a passive IoT traffic report of one or more passive IoT devices.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a passive IoT traffic report may include operations, features, components, or instructions for: signaling a default value corresponding to an unknown number of one or more passive IoT devices in the passive IoT traffic report.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a number of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to a default value signaled by the passive IoT traffic report.

[0013] In some examples of the methods, devices, and non-transitory computer-readable media described herein, sending a passive IoT service report may include operations, features, components, or instructions for the following actions: signaling a cast type associated with a passive IoT communication set in a passive IoT service report, wherein the cast type includes one or more of a broadcast type, a unicast type, or a multicast (groupcast) type.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a broadcast type signaled in a passive IoT traffic report indicates a quantity of one or more passive IoT devices.

[0015] 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 message indicating conflict information associated with a passive IoT communication set, an estimated time period for the passive IoT communication set, or both.

[0016] In some examples of the methods, apparatus and non-transitory computer-readable media described herein, the collision information indicates a probability of a collision occurring during a set of passive IoT communications, a probability that a set of time and frequency resources includes an unused time slot, or both.

[0017] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second scheduling grant based on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the set of passive IoT communications.

[0018] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending a request for a second scheduling grant based on the number of one or more passive IoT devices, the estimated time period of the passive IoT communication set, the number of resources allocated by the scheduling grant, the time period of the resources allocated by the scheduling grant, or a combination thereof; and receiving the second scheduling grant based on a time period between the sending of the request and the start of the second scheduling grant satisfying a threshold, wherein the second scheduling grant indicates a second set of time and frequency resources allocated for the passive IoT communication set.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a request for a continuous scheduling grant within a time period of a set of time and frequency resources; and performing a passive IoT communication set using a second set of time and frequency resources in accordance with the continuous scheduling grant.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of at least one unused time or frequency resource upon completion of a passive IoT communication set.

[0021] A method for wireless communication at a network entity is described. The method may include obtaining a passive IoT service report indicating a set of passive IoT communications to be performed between a UE and one or more passive IoT devices; determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based on the passive IoT service report; and outputting a scheduling grant indicating the set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0022] An apparatus for wireless communication at a network entity is described. The apparatus may include at least one processor and a memory (e.g., operatively, communicatively, functionally, electronically, or electrically) coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to: obtain a passive IoT service report indicating a set of passive IoT communications to be performed between a UE and one or more passive IoT devices; determine a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based on the passive IoT service report; and output a scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0023] Another apparatus for wireless communication at a network entity is described. The apparatus may include a component for obtaining a passive IoT service report indicating a set of passive IoT communications to be performed between a UE and one or more passive IoT devices; a component for determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based on the passive IoT service report; and a component for outputting a scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0024] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by at least one processor to cause the network entity to perform the following operations: obtain a passive IoT service report indicating a set of passive IoT communications to be performed between a UE and one or more passive IoT devices; determine a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based on the passive IoT service report; and output a scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a passive IoT traffic report signals a quantity of one or more passive IoT devices.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining a set of time and frequency resources may include operations, features, components, or instructions for determining a number of resources to be included in the set of time and frequency resources based on a number of passive IoT devices signaled by a passive IoT service report.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a passive IoT traffic report signals a default value corresponding to an unknown number of one or more passive IoT devices.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining a set of time and frequency resources may include operations, features, components, or instructions for determining a number of resources to be included in the set of time and frequency resources based on a default value signaled by a passive IoT service report.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a passive IoT traffic report signals a broadcast type associated with a passive IoT communication set, the broadcast type comprising one or more of a broadcast type, a unicast type, or a multicast type.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a quantity of one or more passive IoT devices based on a broadcast type signaled in a passive IoT traffic report.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining a message indicating conflict information associated with a passive IoT communication set, an estimated time period for the passive IoT communication set, or both.

[0032] In some examples of the methods, apparatus and non-transitory computer-readable media described herein, the collision information indicates a probability of a collision occurring during a set of passive IoT communications, a probability that a set of time and frequency resources includes an unused time slot, or both.

[0033] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a second scheduling grant based on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the set of passive IoT communications.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a request for a continuous scheduling grant within a time period of a set of time and frequency resources; and allocating a second set of time and frequency resources to a passive IoT communication set based on the continuous scheduling grant.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving an indication of at least one unused time or frequency resource in a set of time and frequency resources allocated for a passive IoT communication set; and allocating the at least one unused time or frequency resource to a second UE different from the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 and Figure 2 An example of a wireless communication system supporting techniques for scheduling passive Internet of Things (IoT) communications in accordance with one or more aspects of the present disclosure is illustrated.

[0037] Figure 3A and Figure 3B An example of a resource graph supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is illustrated.

[0038] Figure 4A and Figure 4B An example of a resource graph supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 5A and Figure 5B An example of a resource graph supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 6 An example of a process flow supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 7 and Figure 8 A block diagram of a device supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0042] Fig. 9 A block diagram of a communication manager supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0043] Fig.10A diagram of a system including devices supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0044] Fig.11 and Fig.12 A block diagram of a device supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0045] Fig.13 A block diagram of a communication manager supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0046] Fig.14 A diagram of a system including devices supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is shown.

[0047] Figures 15 to 18 A flow chart illustrating a method of supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0048] Passive Internet of Things (IoT) devices may refer to communication devices that can perform passive (e.g., low-power) communications using technologies such as backscatter and radio frequency identification (RFID). Some wireless communication systems may support both passive IoT communications and new radio (NR) communications. In some cases, passive IoT communications (also referred to herein as ambient power-enabled IoT communications) and NR communications may utilize different waveforms or modulation schemes. For example, NR communications may utilize orthogonal frequency division multiplexing (OFDM) waveforms, while passive IoT communications may utilize single carrier waveforms. These distinctions may lead to different scheduling considerations for NR communications and IoT communications.

[0049] For NR communication, a network entity may allocate resources to a user equipment (UE) based on the buffer status of the UE (e.g., the amount of data stored in the buffer of the UE). However, for passive IoT communication, a network entity may allocate resources to a UE based on the number of passive IoT devices participating in the passive IoT communication. For example, if the UE is intended to perform passive IoT communication with an unknown number of passive IoT devices, the network entity may not be able to determine an appropriate amount of resources to be allocated for the passive IoT communication. Allocating too few resources to the UE may result in signal collisions and reduced communication reliability, while allocating too many resources to the UE may result in higher communication resource overhead.

[0050] Various aspects of the present disclosure provide for improving the reliability and efficiency of passive IoT communications between a UE and one or more passive IoT devices (also referred to herein as passive UEs or backscatter devices). According to the techniques described herein, a UE may send a passive IoT service report before initiating passive IoT communications with one or more passive IoT devices. The passive IoT service report may serve as a scheduling request for passive IoT communications and may include information that enables a network entity to allocate an appropriate amount of resources for the passive IoT communications. For example, the passive IoT service report may indicate the number of passive IoT devices participating in the passive IoT communications.

[0051] For example, if the UE is intended to communicate with an unknown number of passive IoT devices, the UE may include a default value in the passive IoT service report. Therefore, the network entity may allocate the default number of resources for passive IoT communication. If the UE determines that the default number of resources provided by the network entity is insufficient for passive IoT communication, the UE may request additional resources from the network entity. Conversely, if there are unused resources in the default number of resources (for example, if the default number of resources is too large), the UE may send an indication of the unused resources to the network entity so that the network entity can allocate the unused resources to other communication devices.

[0052] Various aspects of the present disclosure may be implemented to achieve one or more of the following advantages. The described techniques may enable a network entity to schedule passive IoT communications with reduced communication resource overhead. For example, configuring a UE to send a passive IoT service report to a network entity according to the techniques described herein may enable the network entity to allocate an appropriate amount of resources for passive IoT communications. In addition, the described techniques may enable a UE to perform passive IoT communications with fewer conflicts and greater reliability. For example, a network entity may dynamically adjust the amount of resources allocated for passive IoT communications using conflict information provided by a UE, which may reduce the likelihood of signal conflicts occurring during passive IoT communications.

[0053] Various aspects of the present disclosure are first described in the context of wireless communication systems, resource diagrams, and process flows. Various aspects of the present disclosure are further illustrated by apparatus diagrams, system diagrams, and flow diagrams relating to techniques for scheduling passive IoT communications, and are described with reference to these diagrams.

[0054] Figure 1An example of a wireless communication system 100 supporting techniques for passive IoT communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a fifth generation (5G) NR network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

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

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

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

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

[0059] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which 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 a base station 140).

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

[0061] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

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

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

[0064] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other appropriate terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client. UE 115 may be a device such as a cellular phone, a smart phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, a Moving Picture Experts Group Layer 3 (MP3) player, or a video device), a camera, a gaming device, a navigation / positioning device (e.g., a Global Navigation Satellite System (GNSS) device based on, for example, Global Positioning System (GPS), Beidou, Global Navigation Satellite System (GLONASS), or Galileo, or a ground-based device), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, a vehicle device, a meter (e.g., a parking meter, an electricity meter, a gas meter, a water meter), a monitor, a gas pump, an appliance (e.g., a kitchen appliance, a washing machine, a dryer), a location tag, a medical / healthcare device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, UE 115 may also refer to a wireless local loop (WLL) station, an IoT device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, which may be implemented in various items such as appliances, drones, robots, vehicles, instruments, and the like.

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

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

[0067] The signal waveform sent on the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as OFDM or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, 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 amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate for the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

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

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

[0070] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems, the time slot may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0072] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of the control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0073] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

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

[0075] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging. The technology disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UE may include MTC or enhanced MTC (eMTC) (also referred to as Category M (CAT-M) or Category (CAT) M1 UE, NB-IoT (also referred to as CAT NB1) UE, and other types of UEs. eMTC and NB-IoT may refer to future technologies based on or evolved from these technologies. For example, eMTC may include further eMTC (FeMTC), enhanced further eMTC (eFeMTC), and large-capacity MTC (mMTC), and NB-IoT may include enhanced NB-IoT (eNB-IoT) and further enhanced NB-IoT (FeNB-IoT).

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

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

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

[0079] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but the waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0080] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of a spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may differ by country or regulatory agency.

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

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

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

[0084] As described herein, some wireless communication systems may support passive IoT technology, and passive IoT devices may refer to devices that use passive communication technology such as backscatter communication. These technologies are compatible with low-cost and low-power devices. Some commercial communication systems may utilize UHF RFID technology that uses backscatter communication technology. However, some UHF RFID systems may be incompatible with NR systems. For example, RFID systems may operate in the ISM band, while NR systems may operate in licensed bands. The interference level between these systems may be defined or not. The technology described herein generally provides support for coexistence between passive IoT and NR.

[0085] Passive IoT devices may be able to receive using envelope decoding techniques and transmit using backscatter communication techniques. In order to perform passive IoT communication, UE 115 may request a scheduling grant from network entity 105. Therefore, network entity 105 may assign the scheduling grant to UE 115 so that UE 115 can perform passive IoT communication with one or more passive IoT devices using the scheduling grant. In some cases, UE 115 may apply the scheduling grant (e.g., communication resources) from network entity 105 to perform passive IoT communication with one or more passive IoT devices (the number of which is known). In other cases, UE 115 may apply the scheduling grant from network entity 105 to perform passive IoT communication with an unknown number of passive IoT devices.

[0086] As described herein, passive IoT communications and NR communications may utilize different waveforms and modulation schemes. For example, NR communications may utilize an OFDM waveform, while passive IoT communications may utilize a single carrier waveform. Similarly, NR communications may utilize a quadrature amplitude modulation (QAM) scheme, while passive IoT communications may utilize an FMO or Miller modulated subcarrier (MMS) modulation scheme. Therefore, IoT communications and NR communications with the same amount of data may occupy different resource allocations. The network entity 105 may take these differences into account when scheduling IoT communications and NR communications.

[0087] According to the techniques described herein, UE 115 may send a passive IoT traffic report to network entity 105. The passive IoT traffic report may indicate that UE 115 intends to conduct passive IoT communications with one or more passive IoT devices. Thus, if UE 115 intends to perform uplink communications with network entity 105, UE 115 may send a scheduling request to network entity 105. Conversely, if UE 115 intends to perform sidelink communications with another UE 115, UE 115 may send a sidelink scheduling request to network entity 105. However, if UE 115 intends to perform passive IoT communications with one or more passive IoT devices, UE 115 may send a passive IoT traffic report (equivalently referred to herein as a passive IoT scheduling request) to network entity 105.

[0088] Various aspects of the wireless communication system 100 may be implemented to achieve one or more of the following advantages. Figure 1The described techniques and operations may enable the network entity 105 to schedule passive IoT communications with reduced communication resource overhead. For example, configuring the UE 115 to send passive IoT service reports to the network entity 105 according to the techniques described herein may enable the network entity 105 to allocate an appropriate amount of resources for passive IoT communications. In addition, the described techniques may enable the UE 115 to perform passive IoT communications with fewer conflicts and greater reliability. For example, the network entity 105 may use the conflict information provided by the UE 115 to dynamically adjust the amount of resources allocated for passive IoT communications, which may reduce the likelihood of signal conflicts occurring during passive IoT communications.

[0089] Figure 2 An example of a wireless communication system 200 that supports techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100, or be implemented by it. For example, the wireless communication system 200 may include a UE 115-a and a network entity 105-a, which may be reference Figure 1 UE 115-a and network entity 105-a may communicate within coverage area 110-a, which may be a reference area. Figure 1 An example of a coverage area 110 is depicted. The wireless communication system 200 may also include a passive IoT device 205-a, a passive IoT device 205-b, and a passive IoT device 205-c. The UE 115-a may communicate with the passive IoT device 205 using resources allocated by the network entity 105-a.

[0090] The wireless communication system 200 may support NR communications (e.g., between a UE 115-a and a network entity 105-a) and passive IoT communications 220 (e.g., between a UE 115-a and passive IoT devices 205). For NR communications, the network entity 105-a may allocate resources to the UE 115-a based on the buffer status of the UE 115-a. However, for passive IoT communications 220, the network entity 105-a may allocate resources to the UE 115-a based on the number of passive IoT devices 205 participating in the passive IoT communications 220. For example, if the UE 115-a is intended to perform passive IoT communications 220 with an unknown number of passive IoT devices 205, the network entity 105-a may not be able to determine an appropriate amount of resources to be allocated for the passive IoT communications 220. Allocating insufficient (eg, too few) resources to UE 115-a may result in signal collisions and reduced communication reliability, while allocating excess (eg, too many) resources to UE 115-a may result in higher communication resource overhead.

[0091] According to aspects of the present disclosure, the UE 115-a may send a passive IoT traffic report 210 to the network entity 105-a prior to initiating passive IoT communications 220 with the passive IoT devices 205. In some examples, the passive IoT traffic report 210 may indicate the number of passive IoT devices 205 participating in the passive IoT communications 220. Upon receiving the passive IoT traffic report 210 from the UE 115-a, the network entity 105-a may allocate an appropriate amount of resources to the UE 115-a via a scheduling grant 215. More specifically, the network entity 105-a may allocate resources to the UE 115-a based on the number of passive IoT devices 205 that will participate in the passive IoT communications 220.

[0092] However, if the UE 115-a cannot determine how many passive IoT devices 205 will participate in the passive IoT communication 220 before sending the passive IoT service report 210, the UE 115-a may include a default value in the passive IoT service report 210 (or omit the value therein). The default value may signal (e.g., to the network entity 105-a) that the UE 115-a intends to perform passive IoT communications 220 with an unknown number of passive IoT devices 205. In such an example, the network entity 105-a may allocate the default amount of resources for the passive IoT communication 220 (e.g., via the scheduling grant 215). As a result, the UE 115-a may perform the passive IoT communication 220 using the resources allocated by the scheduling grant 215. For example, the UE 115 - a may perform passive IoT communications 220 - a with the passive IoT device 205 - a , passive IoT communications 220 - b with the passive IoT device 205 - b , and passive IoT communications 220 - c with the passive IoT device 205 - c .

[0093] If the resources allocated by the scheduling grant 215 are insufficient for the passive IoT communication 220, the UE 115-a may send a request 225 from the network entity 105-a for a continuous scheduling grant. In some examples, the network entity 105-a may allocate a continuous scheduling grant (e.g., a persistent resource allocation) to the UE 115-a in response to the request 225. In some examples, the UE 115-a may send conflict information 230 to the network entity 105-a. The conflict information 230 may indicate a probability of a conflict occurring during the passive IoT communication 220, a probability of an empty time slot occurring during the passive IoT communication 220, or other supplemental information related to the passive IoT communication 220. The network entity 105-a may use the conflict information 230 provided by the UE 115-a to dynamically adjust the amount of resources allocated for the passive IoT communication 220.

[0094] Various aspects of the wireless communication system 200 may be implemented to achieve one or more of the following advantages. Figure 2 The described techniques and operations may enable the network entity 105-a to schedule passive IoT communications 220 with reduced communication resource overhead. For example, configuring the UE 115-a to send a passive IoT service report 210 to the network entity 105-a according to the techniques described herein may enable the network entity 105-a to allocate an appropriate amount of resources for the passive IoT communications 220. In addition, the described techniques may enable the UE 115-a to perform passive IoT communications 220 with fewer conflicts and greater reliability. For example, the network entity 105-a may use the conflict information 230 provided by the UE 115-a to dynamically adjust the amount of resources allocated for the passive IoT communications 220, which may reduce the likelihood of signal conflicts occurring during the passive IoT communications 220.

[0095] Figure 3A and Figure 3B Examples of resource maps 300 and 301 that support techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure are illustrated. Resource maps 300 and 301 may implement or be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, resource maps 300 and 301 may be implemented by reference to Figure 1 and Figure 2 The resource map 300 and the resource map 301 may include a passive IoT device 305-a, a passive IoT device 305-b, and a passive IoT device 305-c, which may be referenced. Figure 2 An example of a passive IoT device 205 is depicted. Resource graph 300 and resource graph 301 may support techniques for reducing conflicts between passive IoT communications performed by passive IoT device 305.

[0096] In some wireless communication systems, if the UE has uplink data available for transmission, the UE may send a buffer status report to the network entity. The buffer status report may indicate the buffer size of the UE (e.g., the amount of uplink data stored in the buffer of the UE). Therefore, the network entity may allocate resources to the UE based on the buffer status report. Therefore, the amount of resources allocated to the UE (e.g., for uplink communication) may correspond to the buffer size of the UE. However, for passive IoT communication, the amount of resources may depend on the number of passive IoT devices 305 (also referred to herein as attachments) participating in the passive IoT communication. If not enough resources are allocated to the UE, the passive IoT communication may result in signal conflicts and reduced communication reliability.

[0097] To ensure that an appropriate amount of resources are allocated for passive IoT communication, the UE may report the passive IoT service (e.g., Figure 2 210) indicates to the network entity the number of passive IoT devices. However, in some examples, the number of passive IoT devices participating in the passive IoT communication may be unknown. That is, the UE may not be able to determine how many passive IoT devices will participate in the passive IoT communication before sending the passive IoT service report. To alleviate this problem, the UE may report a default (e.g., pre-configured) value in the passive IoT service report. Alternatively, the UE may omit a value in the passive IoT service report (e.g., a value corresponding to the number of passive IoT devices).

[0098] Upon receiving a passive IoT traffic report with a default (or omitted) value for the number of passive IoT devices, the network entity may allocate a default (e.g., preconfigured) number of resources for passive IoT communications. The network entity may schedule grants (e.g., with reference to Figure 2 The default amount of resources allocated by the network entity may include insufficient (e.g., too few) resources or excessive (e.g., too many) resources. If the default amount of resources includes insufficient resources, passive IoT communications may result in signal collisions and interference. This may occur when a relatively large number of passive IoT devices 305 attempt to communicate with the UE using the same resources.

[0099] exist Figure 3A In an example of , a UE may receive a scheduling grant indicating a first set of resources 310 (e.g., initial resources) allocated for passive IoT communication between the UE and a passive IoT device 305. The UE may attempt to perform passive IoT communication with the passive IoT device 305 using the first set of resources 310 indicated by the scheduling grant. However, in some cases, the amount or duration of resources in the first set of resources 310 may be insufficient for passive IoT communication. For example, if all three passive IoT devices 305 perform passive IoT communication using the first set of resources 310, a signal from the passive IoT device 305-a may collide with a signal from the passive IoT device 305-b. This may reduce the likelihood of successful communication between the UE and the passive IoT device 305.

[0100] exist Figure 3B In the example of , the UE may determine that the quantity or duration of resources in the first resource set 310 is insufficient for passive IoT communication. The UE may determine this information by measuring or estimating the frequency of signal collisions occurring on the first resource set. At 315, the UE may send collision information (e.g., reference to Figure 2Upon receiving this information from the UE, the network entity may allocate a second set of resources 320 (e.g., supplemental resources) for passive IoT communications between the UE and the passive IoT device 305. Allocating additional resources to the UE may reduce the likelihood of signal collisions occurring during passive IoT communications.

[0101] Aspects of resource map 300 and resource map 301 may be implemented to achieve one or more of the following advantages. Figure 3A and Figure 3B The described techniques and operations may enable a network entity to schedule passive IoT communications with reduced communication resource overhead. For example, configuring a UE to send a passive IoT service report to a network entity according to the techniques described herein may enable the network entity to allocate an appropriate amount of resources for passive IoT communications. In addition, the described techniques may enable the passive IoT device 305 to perform passive IoT communications with fewer conflicts and greater reliability. For example, the network entity may dynamically adjust the amount of resources allocated for passive IoT communications using conflict information provided by the UE, which may reduce the likelihood of signal conflicts occurring during passive IoT communications.

[0102] Figure 4A and Figure 4B Examples of resource maps 400 and 401 that support techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure are illustrated. Resource maps 400 and 401 may implement or be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, resource maps 400 and 401 may be implemented by reference to Figure 1 and Figure 2 As shown in resource diagram 400 and resource diagram 401, the UE may perform passive IoT communication on resources allocated by continuous scheduling grants (e.g., referring to Figure 2 Passive IoT communication 220 described).

[0103] As reference Figure 1 As described in FIG. 3 , the UE may send a passive IoT service report before initiating passive IoT communication with one or more passive IoT devices. The passive IoT service report may serve as a scheduling request for passive IoT communication and may include information that enables the network entity to allocate an appropriate amount of resources for the passive IoT communication. For example, the passive IoT service report may indicate the number of passive IoT devices participating in the passive IoT communication. For example, if the UE intends to communicate with an unknown number of passive IoT devices, the UE may include a default value in the passive IoT service report. Therefore, the network entity may allocate a default amount of resources for the passive IoT communication.

[0104] If the UE determines that the resources provided by the network entity are insufficient for passive IoT communication, the UE may request additional resources from the network entity. Conversely, if some of the resources provided by the network entity are not used, the UE may send an indication of the unused resources to the network entity (so that the network entity can allocate the unused resources to other communication devices). In some examples, the UE may also provide conflict information related to passive IoT communication to the network entity. The network entity may use this information to dynamically adjust the amount or duration of resources allocated for passive IoT communication. The described techniques may enable low-cost devices to perform passive IoT communication with greater efficiency.

[0105] exist Figure 4A In an example of , a UE (e.g., a first UE) may attempt to perform passive IoT communications with one or more passive IoT devices using resources 410 allocated by a network entity. In some cases, the amount or duration of resources 410 may be insufficient for passive IoT communications. In this case, at 415, the UE may send a request for a continuous scheduling grant (e.g., a persistent resource allocation) to the network entity. However, in some cases, if the UE sends the request after a specified time, the UE may not be able to apply the continuous scheduling grant. For example, there may be a threshold (e.g., preconfigured) time period between the UE sending the request for the continuous scheduling grant and the UE being able to use the resources allocated by the continuous scheduling grant. Therefore, if the UE sends a request within the threshold time period (e.g., if there is not enough time between the sending of the request and the start of the continuous scheduling grant), the UE may not be able to use the continuous scheduling grant for passive IoT communications.

[0106] exist Figure 4B In an example of , at 415, the UE may send a request for a continuous scheduling grant. The UE may send the request in response to determining that the duration of the resource 410 (e.g., the initial resource allocation) is insufficient for passive IoT communication. If the UE sends the request early enough, the network entity may have enough time to process the request and reserve the resource 425 (e.g., supplemental resource) for the UE. In other words, the UE may use the resource 425 for passive IoT communication as long as the time period between the sending of the request and the start of the resource 425 meets (e.g., exceeds) a threshold. Therefore, the UE may perform passive IoT communication on the resource 425 according to the continuous scheduling grant. In some examples, the network entity may reserve the resource 425 for the UE by reallocating the resource 420 previously allocated to the second UE.

[0107] Aspects of resource map 400 and resource map 401 may be implemented to achieve one or more of the following advantages. Figure 4A and Figure 4BThe described techniques and operations may enable a network entity to schedule passive IoT communications with reduced communication resource overhead. For example, configuring a UE to send a passive IoT service report to a network entity according to the techniques described herein may enable the network entity to allocate an appropriate amount of resources for passive IoT communications. In addition, if the UE determines that insufficient resources are allocated for passive IoT communications, the network entity may allocate additional resources to the UE via continuous scheduling grants.

[0108] Figure 5A and Figure 5B Examples of resource maps 500 and 501 that support techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure are illustrated. Resource maps 500 and 501 may implement or be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, resource maps 500 and 501 may be implemented by reference to Figure 1 and Figure 2 The resource map 500 and the resource map 501 may include a passive IoT device 505-a, a passive IoT device 505-b, and a passive IoT device 505-c, which may be referenced. Figure 2 3 and the example of the passive IoT device 205 or the passive IoT device 305. The resource map 500 and the resource map 501 may support techniques for reducing communication resource overhead associated with passive IoT communications between a UE and the passive IoT device 505.

[0109] As reference Figure 1 As described in FIG. 4 , the UE may send a passive IoT service report (eg, reference to FIG. 4 ) before initiating passive IoT communication with the passive IoT device 505. Figure 2 The passive IoT service report 210 described in the foregoing description). The passive IoT service report may serve as a scheduling request for passive IoT communication and may include information that enables the network entity to allocate an appropriate amount of resources for the passive IoT communication. For example, the passive IoT service report may indicate the number of passive IoT devices 505 participating in the passive IoT communication. For example, if the UE intends to communicate with an unknown number of passive IoT devices 505, the UE may include a default value in the passive IoT service report. Thus, the network entity may allocate a default amount of resources for the passive IoT communication.

[0110] If the UE determines that the resources provided by the network entity are insufficient for passive IoT communication, the UE may request additional resources from the network entity. Conversely, if some of the resources provided by the network entity are not used, the UE may send an indication of the unused resources to the network entity (so that the network entity can allocate the unused resources to other communication devices). In some examples, the UE may also provide conflict information related to passive IoT communication to the network entity. The network entity may use this information to dynamically adjust the amount or duration of resources allocated for passive IoT communication. The described techniques may enable low-cost devices to perform passive IoT communication with greater efficiency.

[0111] exist Figure 5A In the example of 515, the UE may use resources 510 allocated by the network entity to perform passive IoT communication with passive IoT device 505. However, in some examples, resources 510 may include excess (e.g., too many) resources. This may occur when the UE initiates passive IoT communication with an unknown number of passive IoT devices 505 (e.g., when the network entity allocates a default number of resources to the UE). In such an example, the UE may determine at 515 that the passive IoT communication is complete. As a result, resources 520 may not be used for passive IoT communication between the UE and the passive IoT device 505.

[0112] exist Figure 5B In the example of , the UE may use resources 525 to perform passive IoT communication with passive IoT device 505. For example, if the UE determines at 515 that the passive IoT communication is complete, the UE may send an indication of any unused resources to the network entity so that the network entity can reallocate (e.g., recycle) these resources to other communication devices. For example, if the initial set of resources allocated to the UE includes resources 530, the UE may send an indication of resources 530 to the network entity when the passive IoT communication is complete. Therefore, the network entity may allocate resources 530 to the second UE, thereby reducing the communication resource overhead associated with the passive IoT communication between the UE and the passive IoT device 505.

[0113] Aspects of resource map 500 and resource map 501 may be implemented to achieve one or more of the following advantages. Figure 5A and Figure 5BThe described techniques and operations may enable a network entity to schedule passive IoT communications with reduced communication resource overhead. For example, configuring a UE to send a passive IoT service report to a network entity according to the techniques described herein may enable the network entity to allocate an appropriate amount of resources for passive IoT communications. In addition, the described techniques may enable a passive IoT device 505 to perform passive IoT communications with fewer conflicts and greater reliability. For example, the network entity may dynamically adjust the amount of resources allocated for passive IoT communications using conflict information provided by the UE, which may reduce the likelihood of signal conflicts occurring during passive IoT communications.

[0114] Figure 6 An example of a process flow 600 supporting techniques for scheduling passive IoT communications in accordance with one or more aspects of the present disclosure is illustrated. The process flow 600 may implement or be implemented by aspects of the wireless communication system 100 or the wireless communication system 200. For example, the process flow 600 may include the UE 115-b and the network entity 105-b, which may be reference Figure 1 and Figure 2 The process flow 600 may also include a passive IoT device 605, which may be a reference Figure 2 , and corresponding devices described in FIG. 3 and FIG. 5 . In the following description of process flow 600, operations between UE 115-b, network entity 105-b, and passive IoT device 605 may be performed in a different order or at a different time. Additionally or alternatively, some operations may be omitted from process flow 600 and other operations may be added to process flow 600.

[0115] At 610, UE 115-b may send a passive IoT traffic report (also referred to herein as a passive IoT scheduling request) to network entity 105-b. A passive IoT traffic report may be distinct from an uplink scheduling request (e.g., a request for uplink resources) and a sidelink scheduling request (e.g., a request for sidelink resources). The passive IoT traffic report may indicate one or more passive IoT communications to be performed between UE 115-b and passive IoT devices 605. In some examples, the passive IoT traffic report may indicate a number of passive IoT devices 605. In other examples, the passive IoT traffic report may indicate a default value corresponding to an unknown number of passive IoT devices 605.

[0116] Additionally or alternatively, the passive IoT service report may indicate a broadcast type (also referred to herein as a service type) associated with the passive IoT communication. For example, the passive IoT service report may indicate a broadcast type, a unicast type, or a multicast type associated with the passive IoT communication. In such examples, the network entity 105-b may implicitly determine (e.g., infer) the number of passive IoT devices 605 based on the broadcast type indicated in the passive IoT service report. For example, if the passive IoT service report indicates that the passive IoT communication is associated with a broadcast type, the network entity 105-b may determine that the UE 115-b is intended to perform passive IoT communications with an unknown number of passive IoT devices 605.

[0117] Alternatively, if the passive IoT traffic report indicates that the passive IoT communication is associated with a unicast type, the network entity 105-b may determine that the UE 115-b is intended to perform passive IoT communication with a single passive IoT device (e.g., one of the passive IoT devices 605). Likewise, if the passive IoT traffic report indicates a multicast type associated with passive IoT communication, the network entity 105-b may determine that the UE 115-b is intended to perform passive IoT communication with a specific number of passive IoT devices 605. Thus, the network entity 105-b may implicitly determine the number of passive IoT devices 605 that will participate in the passive IoT communication, even though such information is not explicitly signaled in the passive IoT traffic report.

[0118] At 615, the network entity 105-b may determine a number of resources to be allocated for passive IoT communications between the UE 115-b and the passive IoT device 605. For example, if the passive IoT service report indicates a number of passive IoT devices 605, the network entity 105-b may allocate resources to the UE 115-b based on the indicated number. Alternatively, if the passive IoT service report indicates a default value for the number of passive IoT devices 605, the network entity 105-b may allocate the default number of resources to the UE 115-b. At 620, the UE 115-b may receive a scheduling grant from the network entity 105-b. The scheduling grant may indicate a set of time and frequency resources allocated for passive IoT communications between the UE 115-b and the passive IoT device 605. At 625, the UE 115-b may perform passive IoT communications with the passive IoT device 605 using the set of time and frequency resources allocated by the scheduling grant.

[0119] In some examples, UE 115-b may send conflict information to network entity 105-b at 630. The conflict information may indicate a probability (e.g., likelihood) that a conflict occurs during passive IoT communication, a probability that a set of time and frequency resources includes an unused time slot (e.g., time resources), or both. Additionally or alternatively, UE 115-b may send an indication of an expected time period for a set of passive IoT communications to network entity 105-b. Network entity 105-b may use the information to update (e.g., adjust) an amount or duration of resources allocated for passive IoT communication. For example, network entity 105-b may send (e.g., output) a second scheduling grant indicating a second set of time and frequency resources (e.g., supplemental resources) allocated for passive IoT communication.

[0120] For example, if UE 115-b determines that the time and frequency resources allocated by network entity 105-b are insufficient for passive IoT communication, at 635, UE 115-b may send a request for a continuous scheduling grant (e.g., a persistent resource allocation) to network entity 105-b. Accordingly, UE 115-b may perform (e.g., continue) passive IoT communication on the resources allocated by the continuous scheduling grant. Alternatively, if UE 115-b determines that the time and frequency resources allocated by network entity 105-b include unused resources, UE 115-b may send an indication of the unused resources to network entity 105-b at 640 (e.g., upon completion of passive IoT communication). In some examples, network entity 105-b may allocate these unused resources to other communication devices, thereby reducing communication resource overhead associated with passive IoT communication.

[0121] Various aspects of process flow 600 may be implemented to achieve one or more of the following advantages. Figure 6 The described techniques and operations may enable the network entity 105-b to schedule passive IoT communications with reduced communication resource overhead. For example, configuring the UE 115-b to send passive IoT service reports to the network entity 105-b according to the techniques described herein may enable the network entity 105-b to allocate an appropriate amount of resources for passive IoT communications. In addition, the described techniques may enable the UE 115-b to perform passive IoT communications with fewer conflicts and greater reliability. For example, the network entity 105-b may use conflict information provided by the UE 115-b to dynamically adjust the amount of resources allocated for passive IoT communications, which may reduce the likelihood of signal conflicts occurring during passive IoT communications.

[0122] Figure 7A block diagram 700 of a device 705 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0123] Receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling passive IoT communications). The information may be communicated to other components of device 705. Receiver 710 may utilize a single antenna or a set of multiple antennas.

[0124] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the technology for scheduling passive IoT communications). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0125] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the techniques for scheduling passive IoT communications as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0126] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include at least one processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in the present disclosure. In some examples, at least one processor and a memory coupled to the at least one processor (e.g., operatively, communicatively, functionally, electronically, or electrically) may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory).

[0127] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware, software (e.g., executed by at least one processor), or any combination thereof. If implemented in code executed by at least one processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0128] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0129] According to examples disclosed herein, the communication manager 720 may support wireless communications at the device 705. For example, the communication manager 720 may be configured as or otherwise support a component for outputting a passive IoT service report to the transmitter 715 for transmission by the device 705. The passive IoT service report may indicate a set of passive IoT communications to be performed between the device 705 and one or more passive IoT devices. The communication manager 720 may be configured as or otherwise support a component for obtaining a scheduling grant from the receiver 710 based on the passive IoT service report. The scheduling grant may indicate a set of time and frequency resources allocated for the set of passive IoT communications between the device 705 and the one or more passive IoT devices. The communication manager 720 may be configured as or otherwise support a component for performing a set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant.

[0130] By including or configuring the communication manager 720 according to the examples as described herein, the device 705 (e.g., at least one processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof) can support techniques for more efficiently utilizing communication resources. For example, by configuring the device 705 to send a passive IoT service report to a network entity according to the techniques described herein, the network entity can allocate an appropriate amount of resources for passive IoT communications, which can reduce the communication resource overhead associated with passive IoT communications.

[0131] Figure 8 A block diagram 800 of a device 805 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling passive IoT communications). The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

[0133] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the technology for scheduling passive IoT communications). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0134] Device 805 or its various components may be examples of components for performing various aspects of the technology for scheduling passive IoT communications as described herein. For example, communication manager 820 may include a business reporting component 825, a scheduling grant component 830, a passive IoT communication component 835, or any combination thereof. Communication manager 820 may be an example of various aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated with receiver 810, transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0135] According to examples disclosed herein, the communication manager 820 may support wireless communications at the device 805. The service reporting component 825 may be configured as or otherwise support a component for outputting a passive IoT service report to the transmitter 815 for transmission by the device 805. The passive IoT service report may indicate a set of passive IoT communications to be performed between the device 805 and one or more passive IoT devices. The scheduling grant component 830 may be configured as or otherwise support a component for obtaining a scheduling grant from the receiver 810 based on the passive IoT service report. The scheduling grant may indicate a set of time and frequency resources allocated for the set of passive IoT communications between the device 805 and the one or more passive IoT devices. The passive IoT communication component 835 may be configured as or otherwise support a component for performing a set of passive IoT communications with one or more passive IoT devices using a set of time and frequency resources indicated by the scheduling grant.

[0136] Fig. 9A block diagram 900 of a communication manager 920 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The communication manager 920 can be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components can be examples of components for performing various aspects of the techniques for scheduling passive IoT communications as described herein. For example, the communication manager 920 can include a service reporting component 925, a scheduling grant component 930, a passive IoT communication component 935, a conflict information component 940, a request component 945, a resource indication component 950, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0137] According to examples disclosed herein, the communication manager 920 may support wireless communications at the UE. The service reporting component 925 may be configured as or otherwise support a component for sending a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The scheduling grant component 930 may be configured as or otherwise support a component for receiving a scheduling grant based on the passive IoT service report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices. The passive IoT communication component 935 may be configured as or otherwise support a component for performing a set of passive IoT communications with one or more passive IoT devices using a set of time and frequency resources indicated by the scheduling grant.

[0138] In some examples, to support sending the passive IoT service report, the service reporting component 925 can be configured as or otherwise support means for signaling a number of one or more passive IoT devices in the passive IoT service report. In some examples, the number of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to the number of one or more passive IoT devices signaled by the passive IoT service report.

[0139] In some examples, to support sending a passive IoT service report, the service reporting component 925 can be configured as or otherwise support a means for signaling a default value corresponding to an unknown number of one or more passive IoT devices in the passive IoT service report. In some examples, the number of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to the default value signaled by the passive IoT service report.

[0140] In some examples, to support sending a passive IoT service report, the service reporting component 925 can be configured as or otherwise support a component for signaling a broadcast type associated with a passive IoT communication set in a passive IoT service report, wherein the broadcast type includes one or more of a broadcast type, a unicast type, or a multicast type. In some examples, the broadcast type signaled in the passive IoT service report indicates a number of one or more passive IoT devices.

[0141] In some examples, the conflict information component 940 can be configured as or otherwise support a component for sending a message indicating conflict information associated with the passive IoT communication set, an estimated time period of the passive IoT communication set, or both. In some examples, the conflict information indicates a probability of a conflict occurring during the passive IoT communication set, a probability that the time and frequency resource set includes an unused time slot, or both.

[0142] In some examples, scheduling grant component 930 can be configured as or otherwise support means for receiving a second scheduling grant based on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the set of passive IoT communications.

[0143] In some examples, request component 945 can be configured as or otherwise support a component for sending a request for a second scheduling grant based on the number of one or more passive IoT devices, the estimated time period of the passive IoT communication set, the number of resources allocated by the scheduling grant, the time period of the resources allocated by the scheduling grant, or a combination thereof. In some examples, scheduling grant component 930 can be configured as or otherwise support a component for receiving a second scheduling grant based on a time period between sending the request and starting the second scheduling grant satisfying a threshold, wherein the second scheduling grant indicates a second set of time and frequency resources allocated for the passive IoT communication set.

[0144] In some examples, scheduling grant component 930 can be configured as or otherwise support means for sending a request for a continuous scheduling grant within a time period of a set of time and frequency resources. In some examples, passive IoT communication component 935 can be configured as or otherwise support means for performing a set of passive IoT communications using a second set of time and frequency resources in accordance with the continuous scheduling grant.

[0145] In some examples, resource indication component 950 can be configured as or otherwise support means for sending an indication of at least one unused time or frequency resource upon completion of a passive IoT communication set.

[0146] Fig.10A diagram of a system 1000 including a device 1005 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

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

[0148] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, a wired link, or a wireless link as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1025 for transmission, and for demodulating packets received from one or more antennas 1025. The transceiver 1015, or the transceiver 1015 and one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or any components thereof as described herein.

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

[0150] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to enable device 1005 to perform various functions (e.g., functions or tasks that support techniques for scheduling passive IoT communications). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040 (e.g., operatively, communicatively, functionally, electronically, or electrically), and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0151] According to examples disclosed herein, the communication manager 1020 may support wireless communications at the device 1005. For example, the communication manager 1020 may be configured as or otherwise support a component for sending a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The communication manager 1020 may be configured as or otherwise support a component for receiving a scheduling grant based on the passive IoT service report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices. The communication manager 1020 may be configured as or otherwise support a component for performing a set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant.

[0152] By including or configuring the communication manager 1020 according to examples as described herein, the device 1005 can support techniques for improved communication reliability. For example, by configuring the device 1005 to send conflict information to a network entity according to the techniques described herein, the network entity can use the conflict information provided by the device 1005 to dynamically adjust the amount or duration of resources allocated for passive IoT communications between the device 1005 and one or more passive IoT devices, which can reduce the likelihood of signal collisions occurring during passive IoT communications.

[0153] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions executable by the processor 1040 to cause the device 1005 to perform various aspects of the techniques for scheduling passive IoT communications as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0154] Fig.11 A block diagram 1100 of a device 1105 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0157] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the techniques for scheduling passive IoT communications as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0158] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware may include at least one processor, DSP, CPU, GPU, ASIC, FPGA or other programmable logic device, microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in the present disclosure. In some examples, at least one processor and a memory coupled to the at least one processor (e.g., operatively, communicatively, functionally, electronically, or electrically) can be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory).

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

[0160] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0161] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the device 1105. For example, the communication manager 1120 may be configured as or otherwise support a component for obtaining a passive IoT service report from the receiver 1110. The passive IoT service report may indicate a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The communication manager 1120 may be configured as or otherwise support a component for determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based on the passive IoT service report. The communication manager 1120 may be configured as or otherwise support a component for outputting a scheduling grant to the transmitter 1115 for transmission by the device 1105. The scheduling grant may indicate a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0162] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 (e.g., at least one processor that controls or is otherwise coupled to the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof) can support techniques for more efficiently utilizing communication resources. For example, the device 1105 can use the passive IoT service report provided by the UE to determine appropriate resource allocations for passive IoT communications between the UE and one or more passive IoT devices, which can reduce the communication resource overhead associated with the passive IoT communications.

[0163] Fig.12 A block diagram 1200 of a device 1205 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0166] Device 1205 or its various components may be examples of components for performing various aspects of the technology for scheduling passive IoT communications as described herein. For example, communication manager 1220 may include IoT business reporting component 1225, resource determination component 1230, scheduling component 1235, or any combination thereof. Communication manager 1220 may be an example of various aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0167] According to examples disclosed herein, the communication manager 1220 may support wireless communications at the device 1205. The IoT service reporting component 1225 may be configured as or otherwise support a component for obtaining a passive IoT service report from the receiver 1210. The passive IoT service report may indicate a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The resource determination component 1230 may be configured as or otherwise support a component for determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based on the passive IoT service report. The scheduling component 1235 may be configured as or otherwise support a component for outputting a scheduling grant to the transmitter 1215 for transmission by the device 1205. The scheduling grant may indicate a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0168] Fig.13A block diagram 1300 of a communication manager 1320 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of the techniques for scheduling passive IoT communications as described herein. For example, the communication manager 1320 may include an IoT service reporting component 1325, a resource determination component 1330, a scheduling component 1335, a conflict message component 1340, a scheduling request component 1345, a resource indication component 1350, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0169] According to examples disclosed herein, the communication manager 1320 may support wireless communications at a network entity. The IoT service reporting component 1325 may be configured as or otherwise support a component for obtaining a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The resource determination component 1330 may be configured as or otherwise support a component for determining a set of time and frequency resources to be allocated for a set of passive IoT communications between the UE and one or more passive IoT devices based on the passive IoT service report. The scheduling component 1335 may be configured as or otherwise support a component for outputting a scheduling grant indicating a set of time and frequency resources allocated for a set of passive IoT communications between the UE and one or more passive IoT devices.

[0170] In some examples, the passive IoT service report signals a number of one or more passive IoT devices. In some examples, to support determining a set of time and frequency resources, resource determination component 1330 can be configured as or otherwise support means for determining a number of resources to be included in a set of time and frequency resources based on a number of one or more passive IoT devices signaled by the passive IoT service report.

[0171] In some examples, the passive IoT service report signals a default value corresponding to an unknown number of one or more passive IoT devices. In some examples, to support determining a set of time and frequency resources, the resource determination component 1330 can be configured as or otherwise support a component for determining a number of resources to be included in the set of time and frequency resources based on the default value signaled by the passive IoT service report.

[0172] In some examples, the passive IoT service report signals a broadcast type associated with the passive IoT communication set, the broadcast type comprising one or more of a broadcast type, a unicast type, or a multicast type. In some examples, the resource determination component 1330 can be configured as or otherwise support a component for determining a number of one or more passive IoT devices based on the broadcast type signaled in the passive IoT service report.

[0173] In some examples, the conflict message component 1340 can be configured as or otherwise support a component for obtaining a message indicating conflict information associated with the passive IoT communication set, an estimated time period of the passive IoT communication set, or both. In some examples, the conflict information indicates a probability of a conflict occurring during the passive IoT communication set, a probability that the time and frequency resource set includes an unused time slot, or both.

[0174] In some examples, scheduling component 1335 can be configured as or otherwise support means for outputting a second scheduling grant based on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the set of passive IoT communications.

[0175] In some examples, the scheduling request component 1345 can be configured as or otherwise support a component for obtaining a request for a continuous scheduling grant within a time period of the set of time and frequency resources. In some examples, the resource determination component 1330 can be configured as or otherwise support a component for allocating a second set of time and frequency resources for the passive IoT communication set according to the continuous scheduling grant.

[0176] In some examples, resource indication component 1350 can be configured as or otherwise support means for receiving an indication of at least one unused time or frequency resource in a set of time and frequency resources allocated for a passive IoT communication set. In some examples, resource determination component 1330 can be configured as or otherwise support means for allocating at least one unused time or frequency resource to a second UE different from the UE.

[0177] Fig.14A diagram of a system 1400 including a device 1405 supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein or include components thereof. The device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0178] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1410 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver), and demodulating the signal. Where applicable, transceiver 1410 or transceiver 1410 and one or more antennas 1415 or wired interfaces may be examples of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0180] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, a GPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to enable device 1405 to perform various functions (e.g., functions or tasks that support techniques for scheduling passive IoT communications). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435 (e.g., operatively, communicatively, functionally, electronically, or electrically), and processor 1435 and memory 1425 are configured to perform the various functions described herein. Processor 1435 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1430) to perform the functions of device 1405.

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

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

[0183] According to examples disclosed herein, the communication manager 1420 may support wireless communications at the device 1405. For example, the communication manager 1420 may be configured as or otherwise support a component for obtaining a passive IoT traffic report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The communication manager 1420 may be configured as or otherwise support a component for determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based on the passive IoT traffic report. The communication manager 1420 may be configured as or otherwise support a component for outputting a scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0184] By including or configuring the communication manager 1420 according to the examples described herein, the device 1405 can support techniques for improved communication reliability. For example, the device 1405 can dynamically adjust resource allocation for passive IoT communications between the UE and one or more passive IoT devices using conflict information provided by the UE, which can reduce the probability of signal conflicts occurring during the entire passive IoT communication, among other benefits.

[0185] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1435, the memory 1425, the code 1430, the transceiver 1410, or any combination thereof. For example, the code 1430 may include instructions executable by the processor 1435 to cause the device 1405 to perform various aspects of the techniques for scheduling passive IoT communications as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0186] Fig.15 1 is a flowchart illustrating a method 1500 for supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component of a UE as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component of a UE as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0187] At 1505, the method may include sending a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The operations of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The described business reporting component 925 is executed.

[0188] At 1510, the method may include receiving a scheduling grant based at least in part on the passive IoT traffic report, the scheduling grant indicating a set of time and frequency resources allocated for a set of passive IoT communications between the UE and one or more passive IoT devices. The operations of 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described scheduling is granted to component 930 for execution.

[0189] At 1515, the method may include performing a set of passive IoT communications with one or more passive IoT devices using a set of time and frequency resources indicated by the scheduling grant. The operations of 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The described passive IoT communication component 935 is used to perform.

[0190] Fig.16 1 is a flowchart illustrating a method 1600 for supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE or a component of a UE as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component of a UE as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0191] At 1605, the method may include sending a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig. 9 The described business reporting component 925 is executed.

[0192] At 1610, the method may include receiving a scheduling grant based at least in part on the passive IoT traffic report, the scheduling grant indicating a set of time and frequency resources allocated for a set of passive IoT communications between the UE and one or more passive IoT devices. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 The described scheduling is granted to component 930 for execution.

[0193] At 1615, the method may include sending a request for a second scheduling grant based at least in part on the number of one or more passive IoT devices, the estimated time period of the passive IoT communication set, the number of resources allocated by the scheduling grant, the time period of the resources allocated by the scheduling grant, or a combination thereof. The operations of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 The described request component 945 is executed.

[0194] At 1620, the method may include receiving a second scheduling grant based at least in part on a time period between the sending of the request and the start of the second scheduling grant satisfying a threshold, wherein the second scheduling grant indicates a second set of time and frequency resources allocated for the passive IoT communication set. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig. 9 The described scheduling is granted to component 930 for execution.

[0195] At 1625, the method may include performing a set of passive IoT communications with one or more passive IoT devices using a set of time and frequency resources indicated by the scheduling grant. The operations of 1625 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Fig. 9 The described passive IoT communication component 935 is used to perform.

[0196] Fig.17 1700 is a flowchart illustrating a method 1700 for supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or a component of a network entity as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component of a network entity as described herein. Figures 1 to 6 as well as Figures 11 to 14 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0197] At 1705, the method may include obtaining a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.13 The described IoT business reporting component 1325 is executed.

[0198] At 1710, the method may include determining a set of time and frequency resources to be allocated for a set of passive IoT communications between the UE and one or more passive IoT devices based at least in part on the passive IoT traffic report. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.13 The resource determination component 1330 is described to perform.

[0199] At 1715, the method may include outputting a scheduling grant indicating a set of time and frequency resources allocated for a set of passive IoT communications between the UE and one or more passive IoT devices. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.13 The described scheduling component 1335 is executed.

[0200] Fig.18 A flow chart illustrating a method 1800 for supporting techniques for scheduling passive IoT communications according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component of a network entity as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component of a network entity as described herein. Figures 1 to 6 as well as Figures 11 to 14 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0201] At 1805, the method may include obtaining a passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.13 The described IoT business reporting component 1325 is executed.

[0202] At 1810, the method may include determining a set of time and frequency resources to be allocated for a set of passive IoT communications between the UE and one or more passive IoT devices based at least in part on the passive IoT traffic report. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.13 The resource determination component 1330 is described to perform.

[0203] At 1815, the method may include outputting a scheduling grant indicating a set of time and frequency resources allocated for a set of passive IoT communications between the UE and one or more passive IoT devices. The operations of 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.13 The described scheduling component 1335 is executed.

[0204] At 1820, the method may include obtaining a message indicating conflict information associated with the passive IoT communication set, an estimated time period of the passive IoT communication set, or both. The operations of 1820 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.13 The described conflict message component 1340 is executed.

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

[0206] Aspect 1: A method for performing wireless communications at a UE, the method comprising: sending a passive IoT service report, the passive IoT service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices; receiving a scheduling grant based at least in part on the passive IoT service report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices; and performing the set of passive IoT communications with the one or more passive IoT devices using the set of time and frequency resources indicated by the scheduling grant.

[0207] Aspect 2: The method according to aspect 1, wherein sending the passive IoT service report comprises: signaling the number of the one or more passive IoT devices in the passive IoT service report.

[0208] Aspect 3: A method according to aspect 2, wherein the number of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to the number of the one or more passive IoT devices signaled by the passive IoT service report.

[0209] Aspect 4: The method according to aspect 1, wherein sending the passive IoT service report includes: signaling a default value corresponding to the unknown number of the one or more passive IoT devices in the passive IoT service report.

[0210] Aspect 5: The method according to aspect 4, wherein the number of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to the default value signaled by the passive IoT service report.

[0211] Aspect 6: A method according to any one of Aspects 1 to 5, wherein sending the passive IoT service report includes: signaling a broadcast type associated with the passive IoT communication set in the passive IoT service report, wherein the broadcast type includes one or more of a broadcast type, a unicast type, or a multicast type.

[0212] Aspect 7: The method according to aspect 6, wherein the broadcast type signaled in the passive IoT service report indicates the number of the one or more passive IoT devices.

[0213] Aspect 8: The method according to any one of aspects 1 to 7, the method further comprising: sending a message indicating conflict information associated with the passive IoT communication set, an estimated time period of the passive IoT communication set, or both.

[0214] Aspect 9: The method according to aspect 8, wherein the conflict information indicates a probability of a conflict occurring during the passive IoT communication set, a probability that the time and frequency resource set includes an unused time slot, or both.

[0215] Aspect 10: According to any one of aspects 8 to 9, the method further includes: receiving a second scheduling grant based at least in part on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the passive IoT communication set.

[0216] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: sending a request for a second scheduling grant based at least in part on the number of the one or more passive IoT devices, the estimated time period of the passive IoT communication set, the number of resources allocated by the scheduling grant, the time period of the resources allocated by the scheduling grant, or a combination thereof; and receiving the second scheduling grant based at least in part on a time period between the sending of the request and the start of the second scheduling grant satisfying a threshold, wherein the second scheduling grant indicates a second set of time and frequency resources allocated for the passive IoT communication set.

[0217] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: sending a request for continuous scheduling grant within a time period of the time and frequency resource set; and using a second time and frequency resource set to perform the passive IoT communication set according to the continuous scheduling grant.

[0218] Aspect 13: The method according to any one of Aspects 1 to 12, further comprising: sending an indication of at least one unused time or frequency resource upon completion of the passive IoT communication set.

[0219] Aspect 14: A method for performing wireless communications at a network entity, the method comprising: obtaining a passive IoT service report, the passive IoT service report indicating a set of passive IoT communications to be performed between a UE and one or more passive IoT devices; determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based at least in part on the passive IoT service report; and outputting a scheduling grant, the scheduling grant indicating the set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

[0220] Aspect 15: The method according to Aspect 14, wherein the passive IoT service report signals the number of the one or more passive IoT devices.

[0221] Aspect 16: A method according to Aspect 15, wherein determining the time and frequency resource set includes: determining the number of resources to be included in the time and frequency resource set based at least in part on the number of the one or more passive IoT devices signaled by the passive IoT service report.

[0222] Aspect 17: The method according to aspect 14, wherein the passive IoT traffic report signals a default value corresponding to an unknown number of the one or more passive IoT devices.

[0223] Aspect 18: The method according to Aspect 17, wherein determining the set of time and frequency resources includes: determining the number of resources to be included in the set of time and frequency resources based at least in part on the default value signaled by the passive IoT service report.

[0224] Aspect 19: A method according to any one of Aspects 14 to 18, wherein the passive IoT service report signals a broadcast type associated with the passive IoT communication set, the broadcast type comprising one or more of a broadcast type, a unicast type, or a multicast type.

[0225] Aspect 20: The method according to aspect 19, further comprising: determining the number of the one or more passive IoT devices based at least in part on the broadcast type signaled in the passive IoT service report.

[0226] Aspect 21: The method according to any one of aspects 14 to 20, the method further comprising: obtaining a message indicating conflict information associated with the passive IoT communication set, an estimated time period of the passive IoT communication set, or both.

[0227] Aspect 22: The method according to aspect 21, wherein the conflict information indicates a probability of a conflict occurring during the passive IoT communication set, a probability that the time and frequency resource set includes an unused time slot, or both.

[0228] Aspect 23: According to any one of aspects 21 to 22, the method further includes: outputting a second scheduling grant based at least in part on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the passive IoT communication set.

[0229] Aspect 24: According to the method described in any one of Aspects 14 to 23, the method further includes: obtaining a request for continuous scheduling grant within a time period of the time and frequency resource set; and allocating a second time and frequency resource set to the passive IoT communication set based on the continuous scheduling grant.

[0230] Aspect 25: According to the method described in any one of Aspects 14 to 24, the method further includes: receiving an indication of at least one unused time or frequency resource in the set of time and frequency resources allocated for the passive IoT communication set; and allocating the at least one unused time or frequency resource to a second UE different from the UE.

[0231] Aspect 26: An apparatus for performing wireless communications at a UE, the apparatus comprising at least one processor and a memory coupled to the at least one processor, the memory storing instructions that can be executed by the at least one processor to enable the UE to perform a method according to any one of Aspects 1 to 13.

[0232] Aspect 27: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 13.

[0233] Aspect 28: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by at least one processor to cause the UE to perform a method according to any one of aspects 1 to 13.

[0234] Aspect 29: An apparatus for wireless communication at a network entity, the apparatus comprising at least one processor and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to enable the network entity to perform a method according to any one of Aspects 14 to 25.

[0235] Aspect 30: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 14 to 25.

[0236] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a network entity, the code comprising instructions executable by at least one processor to cause the network entity to perform a method according to any one of aspects 14 to 25.

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

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

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

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

[0241] The functions described herein can be implemented in the form of hardware, software executed by at least one processor, or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, or functions, whether it is described in software, firmware, middleware, microcode, hardware description language, or other terms. When implemented in software executed by at least one processor, the function can be stored on a computer-readable medium as one or more instructions or codes, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software, firmware, hard wiring, or any combination thereof executed by at least one processor. The features that implement the functions can also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0242] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.As an example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change memory, compact disk (CD) ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transient medium that can be used to carry or store the desired program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer or a general or special-purpose processor.Moreover, any connection is appropriately referred to as computer-readable media.For example, if software is sent 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 in the definition of computer-readable media. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0243] As used herein (including in the claims), "or" used in a listing of items (e.g., a listing of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive listing, so that, for example, a listing of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on 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 "based at least in part 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 employed individually, or any combination of two or more of the listed items may be employed. For example, if a composition is described as comprising components A, B, and / or C, the composition can comprise A alone; B alone; C alone; A and B combined; A and C combined; B and C combined; or A, B, and C combined.

[0244] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as via searching in a table, database or other data structure), or ascertaining. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory). Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other similar actions.

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

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

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

Claims

1. A device for wireless communication at a user equipment (UE), the device include: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to: sending a passive Internet of Things (IoT) service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices; receiving a scheduling grant based at least in part on the passive IoT traffic report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices; and The set of passive IoT communications with the one or more passive IoT devices are performed using the set of time and frequency resources indicated by the scheduling grant.

2. The apparatus of claim 1, wherein the instruction for sending the passive IoT service report is executable by the at least one processor to cause the UE to: The number of the one or more passive IoT devices is signaled in the passive IoT traffic report.

3. The apparatus of claim 2, wherein the number of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to the number of the one or more passive IoT devices signaled by the passive IoT service report.

4. The apparatus of claim 1, wherein the instructions for sending the passive IoT service report are executable by the at least one processor to cause the UE to: A default value corresponding to the unknown number of the one or more passive IoT devices is signaled in the passive IoT traffic report. 5 . The apparatus of claim 4 , wherein the number of resources in the set of time and frequency resources indicated by the scheduling grant corresponds to the default value signaled by the passive IoT service report.

6. The apparatus of claim 1, wherein the instructions for sending the passive IoT service report are executable by the at least one processor to cause the UE to: A broadcast type associated with the passive IoT communication set is signaled in the passive IoT traffic report, wherein the broadcast type includes one or more of a broadcast type, a unicast type, or a multicast type. 7 . The apparatus of claim 6 , wherein the broadcast type signaled in the passive IoT traffic report indicates a quantity of the one or more passive IoT devices.

8. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: A message is sent indicating conflict information associated with the passive IoT communication set, an estimated time period for the passive IoT communication set, or both.

9. The apparatus of claim 8, wherein the collision information indicates a probability of collision occurring during the passive IoT communication set, a probability that the set of time and frequency resources includes an unused time slot, or both.

10. The apparatus of claim 8, wherein the instructions are further executable by the at least one processor to cause the UE to: A second scheduling grant is received based at least in part on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the set of passive IoT communications.

11. The apparatus of claim 1 , wherein the instructions are further executable by the at least one processor to cause the UE to: sending a request for a second scheduling grant based at least in part on the number of the one or more passive IoT devices, the estimated time period of the passive IoT communication set, the number of resources allocated by the scheduling grant, the time period of the resources allocated by the scheduling grant, or a combination thereof; and The second scheduling grant is received based at least in part on a time period between sending the request and starting the second scheduling grant satisfying a threshold, wherein the second scheduling grant indicates a second set of time and frequency resources allocated for the set of passive IoT communications.

12. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: sending a request for a continuous scheduling grant during a time period of the set of time and frequency resources; and The set of passive IoT communications is performed using a second set of time and frequency resources according to the continuous scheduling grant.

13. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: An indication of at least one unused time or frequency resource is sent upon completion of the passive IoT communication set.

14. An apparatus for wireless communication at a network entity, the apparatus include: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network entity to: obtaining a passive Internet of Things (IoT) traffic report indicating a set of passive IoT communications to be performed between a user equipment (UE) and one or more passive IoT devices; determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based at least in part on the passive IoT traffic report; and A scheduling grant is output, the scheduling grant indicating the set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

15. The apparatus of claim 14, wherein the passive IoT traffic report signals a number of the one or more passive IoT devices.

16. The apparatus of claim 15, wherein the instructions for determining the set of time and frequency resources are executable by the at least one processor to cause the network entity to: A quantity of resources to be included in the set of time and frequency resources is determined based at least in part on the quantity of the one or more passive IoT devices signaled by the passive IoT traffic report. 17 . The apparatus of claim 14 , wherein the passive IoT traffic report signals a default value corresponding to an unknown number of the one or more passive IoT devices.

18. The apparatus of claim 17, wherein the instructions for determining the set of time and frequency resources are executable by the at least one processor to cause the network entity to: A number of resources to be included in the set of time and frequency resources is determined based at least in part on the default value signaled by the passive IoT traffic report.

19. The apparatus of claim 14, wherein the passive IoT traffic report signals a broadcast type associated with the passive IoT communication set, the broadcast type comprising one or more of a broadcast type, a unicast type, or a multicast type.

20. The apparatus of claim 19, wherein the instructions are further executable by the at least one processor to cause the network entity to: A quantity of the one or more passive IoT devices is determined based at least in part on the broadcast type signaled in the passive IoT traffic report.

21. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the network entity to: A message is obtained indicating conflict information associated with the passive IoT communication set, an estimated time period of the passive IoT communication set, or both.

22. The apparatus of claim 21, wherein the collision information indicates a probability of a collision occurring during the set of passive IoT communications, a probability that the set of time and frequency resources includes an unused time slot, or both.

23. The apparatus of claim 21, wherein the instructions are further executable by the at least one processor to cause the network entity to: A second scheduling grant is output based at least in part on the message, the second scheduling grant indicating a second set of time and frequency resources allocated for the set of passive IoT communications.

24. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the network entity to: obtaining a request for a continuous scheduling grant over a period of time for the set of time and frequency resources; and A second set of time and frequency resources is allocated to the passive IoT communication set according to the continuous scheduling grant.

25. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the network entity to: receiving an indication of at least one unused time or frequency resource in the set of time and frequency resources allocated for the passive IoT communication set; and The at least one unused time or frequency resource is allocated to a second UE different from the UE.

26. A method for wireless communication at a user equipment (UE), the method include: sending a passive Internet of Things (IoT) service report indicating a set of passive IoT communications to be performed between the UE and one or more passive IoT devices; receiving a scheduling grant based at least in part on the passive IoT traffic report, the scheduling grant indicating a set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices; and The set of passive IoT communications with the one or more passive IoT devices are performed using the set of time and frequency resources indicated by the scheduling grant.

27. The method according to claim 26, wherein the passive IoT service report is sent include: The number of the one or more passive IoT devices is signaled in the passive IoT traffic report.

28. The method according to claim 26, wherein the passive IoT service report is sent include: A default value corresponding to the unknown number of the one or more passive IoT devices is signaled in the passive IoT traffic report.

29. The method according to claim 26, further comprising: include: sending a request for a second scheduling grant based at least in part on the number of the one or more passive IoT devices, the estimated time period of the passive IoT communication set, the number of resources allocated by the scheduling grant, the time period of the resources allocated by the scheduling grant, or a combination thereof; and The second scheduling grant is received based at least in part on a time period between sending the request and starting the second scheduling grant satisfying a threshold, wherein the second scheduling grant indicates a second set of time and frequency resources allocated for the set of passive IoT communications.

30. A method for wireless communication at a network entity, the method include: obtaining a passive Internet of Things (IoT) traffic report indicating a set of passive IoT communications to be performed between a user equipment (UE) and one or more passive IoT devices; determining a set of time and frequency resources to be allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices based at least in part on the passive IoT traffic report; and A scheduling grant is output, the scheduling grant indicating the set of time and frequency resources allocated for the set of passive IoT communications between the UE and the one or more passive IoT devices.

Images