Resource allocation for confirmatory response from ambient internet-of-things device
Resource allocation mechanisms for confirmatory responses in A-IoT devices address the challenge of limited power and processing, enabling efficient ACK/NACK transmissions and improving reader device operations.
Patent Information
- Application Number
- PCT/CN2024/110548
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-08
- Publication Date
- 2026-02-12
AI Technical Summary
Ambient Internet-of-Things (A-IoT) devices face challenges in providing confirmatory responses due to their limited power and processing resources, making it unclear how to allocate resources for ACK/NACK transmissions.
Mechanisms are provided for resource allocation in A-IoT devices to facilitate confirmatory response transmissions, including unicast and groupcast R2D transmissions.
Enables A-IoT devices to efficiently provide ACK/NACK and other assistance information, helping reader devices perform actions more effectively.
Smart Images

Figure CN2024110548_12022026_PF_FP_ABST
Abstract
Description
RESOURCE ALLOCATION FOR CONFIRMATORY RESPONSE FROM AMBIENT INTERNET-OF-THINGS DEVICE
[0001] Field of the Disclosure
[0002] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for providing control information from an ambient Internet-of-Things (IoT) device to a reader device.
[0003] Description of Related Art
[0004] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.
[0005] Although wireless communications systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuous desire to improve the technical performance of wireless communications systems, including, for example: improving speed and data carrying capacity of communications, improving efficiency of the use of shared communications mediums, reducing power used by transmitters and receivers while performing communications, improving reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability for different types of devices to intercommunicate, increasing the number and type of wireless communications mediums available for use, and the like. Consequently, there exists a need for further improvements in wireless communications systems to overcome the aforementioned technical challenges and others.SUMMARY
[0006] One aspect provides a method for wireless communications at an ambient Internet of things (IoT) device. The method includes receiving, from a reader device, signaling indicating at least one resource for confirmatory response transmission; receiving at least one reader to device (R2D) transmission from the reader device; and transmitting, using the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.
[0007] Another aspect provides a method for wireless communications at reader device. The method includes transmitting, to an ambient Internet of things (IoT) device, signaling indicating at least one resource for confirmatory response transmission; transmitting at least one reader to device (R2D) transmission to the ambient IoT device; and receiving, via the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.
[0008] Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and / or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed (e.g., directly, indirectly, after pre-processing, without pre-processing) by one or more processors of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and / or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.
[0009] The following description and the appended figures set forth certain features for purposes of illustration.BRIEF DESCRIPTION OF DRAWINGS
[0010] The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.
[0011] FIG. 1 depicts an example wireless communications network.
[0012] FIG. 2 depicts an example disaggregated base station architecture.
[0013] FIG. 3 depicts aspects of an example base station and an example user equipment.
[0014] FIGS. 4A, 4B, 4C, and 4D depict various example aspects of data structures for a wireless communications network.
[0015] FIG. 5 illustrates an example radio frequency identification (RFID) system.
[0016] FIG. 6 depicts an example system that utilizes a network to communicate with ambient internet of things (A-IoT) terminal devices or tags.
[0017] FIGS. 7A, 7B, 7C, and 7D illustrate different topologies of an A-IoT system.
[0018] FIG. 8 is a call flow diagram depicting confirmatory response signaling, in accordance with aspects of the present disclosure.
[0019] FIG. 9 is a timing diagram depicting confirmatory response signaling, in accordance with aspects of the present disclosure.
[0020] FIG. 10 is a timing diagram depicting confirmatory response signaling, in accordance with aspects of the present disclosure.
[0021] FIGs. 11A and 11B are timing diagrams depicting confirmatory response signaling, in accordance with aspects of the present disclosure.
[0022] FIGs. 12A and 12B are timing diagrams depicting confirmatory response signaling from multiple A-IoT devices, in accordance with aspects of the present disclosure.
[0023] FIG. 13 is a timing diagram depicting confirmatory response signaling from multiple A-IoT devices, in accordance with aspects of the present disclosure.
[0024] FIG. 14 depicts a method for wireless communications.
[0025] FIG. 15 depicts a method for wireless communications.
[0026] FIG. 16 depicts aspects of an example communications device.DETAILED DESCRIPTION
[0027] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for providing control information from an ambient Internet-of-Things (A-IoT) device to a reader device.
[0028] The rapid advancement of the Internet of Things (IoT) has led to the development of Ambient IoT (A-IoT) systems, which use low-power, low-complexity devices to monitor and manage various environments. These devices, typically operating with minimal power in the range of microwatts (μW) , are essential for applications like efficient inventory management and command in large-scale deployments.
[0029] Despite their advantages, A-IoT devices face potential challenges. For example, one potential challenge is whether or how to provide control information from an A-IoT device, given their limited power and processing resources. As a result, it may not be clear if or how to provide important information from an A-IoT device, such as acknowledgement (ACK) or negative acknowledgement (NACK) receipt of a reader to device (R2D) transmission.
[0030] ACK / NACK and other types of assistance information may be provided in signaling that may be referred to herein as a confirmatory response. As such, a confirmatory response may be used to indicate whether the R2D transmission is successfully received or not and / or provide other assistance information that may inform a reader device.
[0031] One potential challenge when considering confirmatory responses, is what resources to use for their transmission. Given limited processing and signaling capability of A-IoT devices, how to indicate what resources an A-IoT device is to use for confirmatory responses presents a challenge.
[0032] Aspects of the present disclosure provide various scenarios to indicate what resources an A-IoT device may use for sending confirmatory transmissions after receiving an R2D transmission. Certain aspects of the present disclosure provide mechanisms for resource allocation for confirmatory response to both unicast and groupcast R2D transmissions.
[0033] By helping enable confirmatory response transmission, aspects of the present disclosure may help A-IoT device provide ACK / NACK and other assistance information that may help a reader device perform an action more efficiently.
[0034] Introduction to Wireless Communications Networks
[0035] The techniques and methods described herein may be used for various wireless communications networks. While aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may likewise be applicable to other communications systems and standards not explicitly mentioned herein.
[0036] FIG. 1 depicts an example of a wireless communications network 100, in which aspects described herein may be implemented.
[0037] Generally, wireless communications network 100 includes various network entities (alternatively, network elements or network nodes) . A network entity is generally a communications device and / or a communications function performed by a communications device (e.g., a user equipment (UE) , a base station (BS) , a component of a BS, a server, etc. ) . For example, various functions of a network as well as various devices associated with and interacting with a network may be considered network entities. Further, wireless communications network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102) , and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipments.
[0038] In the depicted example, wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190, which interoperate to provide communications services over various communications links, including wired and wireless links.
[0039] FIG. 1 depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA) , satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor / actuator, display, internet of things (IoT) devices, always on (AON) devices, edge processing devices, or other similar devices. UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.
[0040] BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120. The communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.
[0041] BSs 102 may generally include: a NodeB, enhanced NodeB (eNB) , next generation enhanced NodeB (ng-eNB) , next generation NodeB (gNB or gNodeB) , access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and / or others. Each of BSs 102 may provide communications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of a macro cell) . A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area) , a pico cell (covering relatively smaller geographic area, such as a sports stadium) , a femto cell (relatively smaller geographic area (e.g., a home) ) , and / or other types of cells.
[0042] While BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations. For example, one or more components of a base station may be disaggregated, including a central unit (CU) , one or more distributed units (DUs) , one or more radio units (RUs) , a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, to name a few examples. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., BS 102) may include components that are located at a single physical location or components located at various physical locations. In examples in which a base station includes components that are located at various physical locations, the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a base station that is located at a single physical location. In some aspects, a base station including components that are located at various physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. FIG. 2 depicts and describes an example disaggregated base station architecture.
[0043] Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., an S1 interface) . BSs 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN) ) may interface with 5GC 190 through second backhaul links 184. BSs 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over third backhaul links 134 (e.g., X2 interface) , which may be wired or wireless.
[0044] Wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz –7125 MHz, which is often referred to (interchangeably) as “Sub-6 GHz” . Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24, 250 MHz –71,000 MHz, which is sometimes referred to (interchangeably) as a “millimeter wave” ( “mmW” or “mmWave” ) . In some cases, FR2 may be further defined in terms of sub-ranges, such as a first sub-range FR2-1 including 24, 250 MHz –52, 600 MHz and a second sub-range FR2-2 including 52, 600 MHz –71,000 MHz. A base station configured to communicate using mmWave / near mmWave radio frequency bands (e.g., a mmWave base station such as BS 180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.
[0045] The communications links 120 between BSs 102 and, for example, UEs 104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) , and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) .
[0046] Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with a UE 104 to improve path loss and range. For example, BS 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate the beamforming. In some cases, BS 180 may transmit a beamformed signal to UE 104 in one or more transmit directions 182’. UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182” . UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182” . BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182’. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receive directions for BS 180 may or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.
[0047] Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.
[0048] Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. D2D communications link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and / or a physical sidelink feedback channel (PSFCH) .
[0049] EPC 160 may include various functional components, including: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and / or a Packet Data Network (PDN) Gateway 172, such as in the depicted example. MME 162 may be in communication with a Home Subscriber Server (HSS) 174. MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, MME 162 provides bearer and connection management.
[0050] Generally, user Internet protocol (IP) packets are transferred through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switched (PS) streaming service, and / or other IP services.
[0051] BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and / or may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0052] 5GC 190 may include various functional components, including: an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may be in communication with Unified Data Management (UDM) 196.
[0053] AMF 192 is a control node that processes signaling between UEs 104 and 5GC 190. AMF 192 provides, for example, quality of service (QoS) flow and session management.
[0054] Internet protocol (IP) packets are transferred through UPF 195, which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC 190. IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.
[0055] In various aspects, a network entity or network node can be implemented as an aggregated base station, as a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.
[0056] FIG. 2 depicts an example disaggregated base station 200 architecture. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a Non-Real Time (Non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) Framework 205, or both) . A CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 240.
[0057] Each of the units, e.g., the CUs 210, the DUs 230, the RUs 240, as well as the Near-RT RICs 225, the Non-RT RICs 215 and the SMO Framework 205, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally or alternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
[0058] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., Central Unit –User Plane (CU-UP) ) , control plane functionality (e.g., Central Unit –Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.
[0059] The DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230, or with the control functions hosted by the CU 210.
[0060] Lower-layer functionality can be implemented by one or more RUs 240. In some deployments, an RU 240, controlled by a DU 230, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 240 can be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU (s) 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU (s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0061] The SMO Framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240 and Near-RT RICs 225. In some implementations, the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.
[0062] The Non-RT RIC 215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 225. The Non-RT RIC 215 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 225. The Near-RT RIC 225 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.
[0063] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 225, the Non-RT RIC 215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from non-network data sources or from network functions. In some examples, the Non-RT RIC 215 or the Near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
[0064] FIG. 3 depicts aspects of an example BS 102 and a UE 104.
[0065] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340) , antennas 334a-t (collectively 334) , transceivers 332a-t (collectively 332) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339) . For example, BS 102 may send and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340, which may be configured to implement various functions described herein related to wireless communications.
[0066] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380) , antennas 352a-r (collectively 352) , transceivers 354a-r (collectively 354) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360) . UE 104 includes controller / processor 380, which may be configured to implement various functions described herein related to wireless communications.
[0067] In regards to an example downlink transmission, BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller / processor 340. The control information may be for the physical broadcast channel (PBCH) , physical control format indicator channel (PCFICH) , physical HARQ indicator channel (PHICH) , physical downlink control channel (PDCCH) , group common PDCCH (GC PDCCH) , and / or others. The data may be for the physical downlink shared channel (PDSCH) , in some examples.
[0068] Transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 320 may also generate reference symbols, such as for the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , PBCH demodulation reference signal (DMRS) , and channel state information reference signal (CSI-RS) .
[0069] Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.
[0070] In order to receive the downlink transmission, UE 104 includes antennas 352a-352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.
[0071] MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.
[0072] In regards to an example uplink transmission, UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH) ) from the controller / processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) . The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM) , and transmitted to BS 102.
[0073] At BS 102, the uplink signals from UE 104 may be received by antennas 334a-t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller / processor 340.
[0074] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.
[0075] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.
[0076] In various aspects, BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a-t, antenna 334a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 334a-t, transceivers 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.
[0077] In various aspects, UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, and / or other aspects described herein.
[0078] In some aspects, one or more processors may be configured to perform various operations, such as those associated with the methods described herein, and transmit (output) to or receive (obtain) data from another interface that is configured to transmit or receive, respectively, the data.
[0079] FIGS. 4A, 4B, 4C, and 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIG. 1.
[0080] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.
[0081] Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD) . OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIGS. 4B and 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and / or in the time domain with SC-FDM.
[0082] A wireless communications frame structure may be frequency division duplex (FDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. Wireless communications frame structures may also be time division duplex (TDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.
[0083] In FIG. 4A and 4C, the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL / UL. UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) , or semi-statically / statically through radio resource control (RRC) signaling) . In the depicted examples, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. Subframes may also include mini-slots, which generally have fewer symbols than an entire slot. Other wireless communications technologies may have a different frame structure and / or different channels.
[0084] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 6 allow for 1, 2, 4, 8, 16, 32, and 64 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing may be equal to 2μ×15 kHz, where μ is the numerology 0 to 6. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=6 has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGS. 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.
[0085] As depicted in FIGS. 4A, 4B, 4C, and 4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
[0086] As illustrated in FIG. 4A, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE 104 of FIGS. 1 and 3) . The RS may include demodulation RS (DMRS) and / or channel state information reference signals (CSI-RS) for channel estimation at the UE.The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and / or phase tracking RS (PT-RS) .
[0087] FIG. 4B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) , each CCE including, for example, nine RE groups (REGs) , each REG including, for example, four consecutive REs in an OFDM symbol.
[0088] A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104 of FIGS. 1 and 3) to determine subframe / symbol timing and a physical layer identity.
[0089] A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
[0090] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and / or paging messages.
[0091] As illustrated in FIG. 4C, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. UE 104 may transmit sounding reference signals (SRS) . The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0092] FIG. 4D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and / or UCI.
[0093] Introduction to Radio Frequency Identification (RFID) Systems
[0094] Radio frequency identification (RFID) is a rapidly growing technology impacting many industries due to its economic potential for inventory / asset management within warehouses, internet of things (IoT) , sustainable sensor networks in factories and / or agriculture, and smart homes, to name a few example applications. RFID technology consists of RFID devices (or backscatter devices) , such as transponders, or tags, that emit an information-bearing signal upon receiving an energizing signal.
[0095] RFID devices may be operated without a battery. Generally, RFID devices that are operated without a battery are known as passive RFID devices. Passive RFID devices may operate by harvesting energy from received radio frequency signals (e.g., “over the air” ) , thereby powering reception and transmission circuitry within the RFID devices. This harvested energy allows passive RFID devices to transmit information, sometimes referred to as backscatter modulated information, without the need for a local power source within the RFID device. On the other hand, in certain aspects, RFID device may be semi-passive and include on-board energy storage to supplement their ability to harvest energy from received signals (however, at higher cost) .
[0096] In some cases, in addition to harvesting power from RF sources, energy harvesting devices may accumulate energy from other direct energy sources, such as solar energy, in order to supplement its power demands. Semi-passive energy harvesting devices may, in some cases, include power consuming RF components, such as analog to digital converters (ADCs) , mixers, and oscillators.
[0097] The RFID device may be a type of user equipment (UE) that provides low-cost and low-power solutions for many applications in a wireless communications system. The RFID device may be power efficient, sometimes requiring less than 0.1mW of power to operate. Further, relatively simple architectures and, in some cases, lack of battery, mean that the RFID device can be small, lightweight, and easily installed or integrated in many types of environments or host devices. The RFID device provides practical and necessary solutions to many networking applications that require, low-cost, small footprint, durable, maintenance-free, and long lifespan communications devices. For example, the RFID device may be configured as long endurance industrial sensors, which mitigates the problems of replacing batteries in and around dangerous machinery.
[0098] FIG. 5 illustrates an example RFID system 500. As shown, RFID system 500 includes a reader 510 and an RFID tag 550. Reader 510 may also be referred to as an interrogator or a scanner. RFID tag 550 may also be referred to as an interrogator, RFID label, or an electronics label. In certain aspects, reader 510 is a network entity (e.g., such as a gNB) and RFID tag 550 is a user equipment (UE) .
[0099] Reader 510 includes an antenna 520 and an electronics unit 530. Antenna 520 radiates signals transmitted by reader 510 and receives signals from RFID tags and / or other devices. Electronics unit 530 may include a transmitter and a receiver for reading RFID tags such as RFID tag 550. The same pair of transmitter and receiver (or another pair of transmitter and receiver) may support bi-directional communication with wireless networks, wireless devices, etc. Electronics unit 530 may include processing circuitry (e.g., a processor) to perform processing for data being transmitted and received by the RFID reader 510.
[0100] RFID tag 550 includes an antenna 560 and a data storage element 570. Antenna 560 radiates signals transmitted by RFID tag 550 and receives signals from RFID reader 510 and / or other devices. Data storage element 570 stores information for RFID tag 550, for example, in an electrically erasable programmable read-only memory (EEPROM) or another type of memory. RFID tag 550 may also include an electronics unit that can process the received signal and generate the signals to be transmitted.
[0101] RFID tag 550 may be a passive RFID tag having no battery. In this case, induction may be used to power the RFID tag 550. For example, in some cases, a magnetic field from a signal transmitted by reader 510 may induce an electrical current in RFID tag 550, which may then operate based on the induced current. RFID tag 550 can radiate its signal in response to receiving a signal from RFID reader 510 or some other device. In certain other aspects, RFID tag 550 may optionally include an energy storage device 590, such as a battery, capacitor, etc., for storing energy harvested using energy harvesting circuitry 555, as described below.
[0102] RFID tag 550 may be read by placing the reader 510 within close proximity to RFID tag 550. Reader 510 may radiate a first signal 525 via the antenna 520. In some cases, the first signal 525 may be known as an interrogation signal or energy signal. In some cases, energy of the first signal 525 may be coupled from reader antenna 520 to RFID tag antenna 560 via magnetic coupling and / or other phenomena. In other words, the RFID tag 550 may receive the first signal 525 from reader 510 via antenna 560 and energy of the first signal 525 may be harvested using energy harvesting circuitry 555 (e.g., an RF transducer) and used to power RFID tag 550. For example, energy of the first signal 525 received by RFID tag 550 may be used to power a microprocessor 545 of RFID tag 550. Microprocessor 545 may, in turn, retrieve information stored in a data storage element 570 of RFID tag 550 and transmit the retrieved information via a second signal 535 using the antenna 560. For example, in some cases, microprocessor 545 may generate the second signal 535 by modulating a baseband signal (e.g., generated using energy of the first signal 525) with the information retrieved from the data storage element 570. In some cases, this second signal 535 may be known as a backscatter modulated information signal. Thereafter, as noted, microprocessor 545 transmits the second signal 535 to reader 510. Reader 510 may receive the second signal 535 from RFID tag 550 via antenna 520 and may process (e.g., demodulate) the received signal to obtain the information of data storage element 570 sent in second signal 535.
[0103] RFID system 500 may be designed to operate at 13.56 MHz or some other frequency (e.g., an ultra-high frequency (UHF) band at 900 MHz) . Reader 510 may have a specified maximum transmit power level, which may be imposed by the Federal Communication Commission (FCC) in the United Stated or other regulatory bodies in other countries. The specified maximum transmit power level of reader 510 may limit the distance at which RFID tag 550 can be read by reader 510.
[0104] Wireless technology is increasingly useful in industrial applications, such as ultra-reliable low-latency communication (URLLC) and machine type communication (MTC) . In such domains, and others, it is desirable to support devices (e.g., passive RFID tags) that are capable of harvesting energy from wireless energy sources (e.g., in lieu of or in combination with a battery or other energy storage device, such as a capacitor) , such as RF signals, thermal energy, solar energy, and the like.
[0105] Introduction to Ambient Internet of Things (IoT) Devices
[0106] An ambient internet of things (A-IoT) device (or tag) refers to a device that is much smaller and cheaper compared to previous generations of IoT devices, such as narrowband IoT (NB-IoT) and reduced capability (RedCap) devices. Ambient IoT devices may obtain energy from radio waves. Due to their size and ability to operate with little or no power source, A-IoT device may have broad applicability in tracking, monitoring, and managing various devices and processes, with consumer and industrial uses.
[0107] FIG. 6 depicts an example system 600 (e.g., an A-IoT system) that utilizes a network entity (e.g., a gNodeB (gNB) ) to communicate with A-IoT devices or tags. The A-IoT devices may be used to monitor a variety of devices and processes. For example, the A-IoT devices may be used to report sensor measurements, video signals / images, light readings, and control devices (e.g., as actuators) .
[0108] Typical networks may not be able to efficiently support the most pervasive radio frequency identification (RFID) type of sensors, implemented as passive IoT devices. Such devices may be used extensively in future use cases, such as asset management, logistics, warehousing and manufacturing. Certain systems may be required to manage A-IoT devices.
[0109] As illustrated in FIG. 6, a reader device, such as a gNB, may be able to read information stored on one or more A-IoT devices and / or write information to the one or more A-IoT devices. The gNB can provide energy to the one or more A-IoT devices (e.g., via a continuous wave (CW) signal) , and an information-bearing signal may be reflected back (e.g., backscattered) from the one or more A-IoT devices to the gNB. The gNB may read the reflected signal (e.g., a backscattered signal) from the one or more A-IoT devices to decode information transmitted by the one or more A-IoT devices.
[0110] The A-IoT devices may support various types of traffic. For example, A-IoT devices may support Device-Originated (DO) traffic, including Device-Originated autonomous (DO-DOA) and Device-Terminated triggered (DO-DTT) traffic, which may be reported periodically.
[0111] The A-IoT system is associated with different topologies such as a first topology, a second topology, a third topology with downlink assistance, and a third topology with uplink assistance. In all of these topologies, an A-IoT device may be provided with a carrier wave from other node (s) either inside or outside the topology. One or more links in each topology may be bidirectional or unidirectional.
[0112] FIG. 7A depicts a diagram 700A illustrating a first topology (Topology 1) of an A-IoT system. In Topology 1, an A-IoT device directly and bidirectionally communicates with a gNB. The communication between the gNB and the A-IoT device includes A-IoT data and / or signaling. This topology includes the possibility that the gNB transmitting to the A-IoT device is a different from the gNB receiving from the A-IoT device.
[0113] FIG. 7B depicts a diagram 700B illustrating a second topology (Topology 2) of an A-IoT system. In Topology 2, an A-IoT device communicates bidirectionally with an intermediate node between the A-IoT device and a gNB. In this topology, the intermediate node may be an intermediate reader device, such as a user equipment (UE) , a relay device, a repeater device, an integrated access and backhaul (IAB) device, etc. that is capable of an A-IoT operation. For example, the intermediate node may be configured to receive signals from the gNB and forward these signals to the A-IoT device using A-IoT communication. Similarly, the intermediate node may be configured to receive signals from the A-IoT device and forward these signals to the gNB. In some cases, the A-IoT device may measure a downlink signal strength from the gNB (e.g., per Topology 1) , and from the intermediate node (e.g., per Topology 2) .
[0114] FIG. 7C depicts a diagram 700C illustrating a third topology of an A-IoT system with downlink assistance (Topology 3-1) . As depicted, an A-IoT device transmits data and / or signalling to a gNB, and receives data and / or signalling from an assisting node (e.g., the assisting node for downlink operations) . The assisting node can be a relay device, an IAB device, a UE, or a repeater device which is capable of operating as an A-IoT device.
[0115] FIG. 7D depicts a diagram 700D illustrating a third topology of an A-IoT system with uplink assistance (Topology 3-2) . As depicted, an A-IoT device receives data and / or signalling from a gNB, and transmits data and / or signalling to an assisting node (e.g., the assisting node for uplink operations) .
[0116] Aspects Related to Resource Allocation for Confirmatory Response from Ambient Internet-of-Things Devices
[0117] As noted above, ACK / NACK and other types of assistance information may be provided in signaling that may be referred to herein as a confirmatory response. Aspects of the present disclosure provide various scenarios to indicate what resources an A-IoT device may use for sending confirmatory transmissions after receiving an R2D transmission.
[0118] FIG. 8 depicts an example call flow diagram 800 depicting resource allocation for confirmatory response from an ambient IoT device (or devices) , in accordance with aspects of the present disclosure. In some cases, the reader device 802 may be part of a plurality of reader devices that are configured to communicate with the IoT device (or devices) 904.
[0119] In some aspects, the reader device 802 may be a radio access network (RAN) entity, such as an example of the BS 102 depicted and described with respect to FIG. 1 and 3 or a disaggregated base station depicted and described with respect to FIG. 2. In some aspects, the reader device 802 may be a UE, such as the UE 104 depicted and described with respect to FIG. 1 and 3. In some aspects, the IoT device (s) 904 may be an example of the RFID tag 550 described with respect to FIG. 5 and / or one or more of the A-IoT devices described with respect to FIGS. 6 or 7.
[0120] As illustrated at 810, the reader device 802 may signal a resource allocation, indicating at least one resource for the IoT to use for confirmatory response transmission. The reader device 802 may then transmit a reader-to-device (R2D) signal. The R2D signal may be any suitable waveform (e.g., continuous wave CW) , for example, to prompt a response from the IoT device (e.g., to cause an action or read information) .
[0121] As illustrated at 820, the IoT device 804 may transmit a confirmatory response (e.g., acknowledging an R2D transmission) . The confirmatory response may be sent as a device-to-reader (D2R) signal of any suitable waveform. In some cases, the confirmatory response may be sent as a backscattered signal.
[0122] According to certain aspects, the resource allocation for confirmatory response may be signaled via a unicast R2D transmission (e.g., targeting a single A-IoT device) . In such cases, the unicast R2D transmission may indicate the resource for the A-IoT device to transmit the confirmatory response.
[0123] As illustrated in FIG. 9, in some cases, the resource 906 (for the confirmatory response) may be dynamically indicated via a signal (confirmatory response triggering signal 904) for the ambient-IoT device to transmit the confirmatory response.
[0124] In some cases, the reader device may only indicate the frequency resource and allowed transmission duration for the confirmatory response transmission. For example, as illustrated in FIG. 9 and FIG. 10, the triggering signal 904 may indicate a frequency domain resource allocation (FDRA) that includes a bitmap that indicates the frequency resources for confirmatory response.
[0125] There are various options for determining the starting transmission point of a confirmatory response.
[0126] For example, according to a first option, the ambient-IoT device may transmit the confirmatory response immediately after receiving the triggering signal. According to a second option, the starting transmission point may be predefined or dynamically indicated (e.g., indicated via control information of a corresponding R2D transmission 902) and there may be a minimum time duration between the end of reception of the triggering signal 904 and the start transmission time of confirmatory response as illustrated in FIG. 10.
[0127] There are also various options for determining a quantity of confirmatory responses that will be transmitted. According to a first option, a predefined number of confirmatory responses may be aggregated. For example, as illustrated in FIG. 9, a confirmatory response (may be aggregated) for the latest N R2D receptions 902. N=3 in the illustrated example. In some cases, a confirmatory response may not be transmitted until N R2D transmissions are received) . In some cases, the value of N may signaled, predefined, or (pre-) configured.
[0128] According to a second option, the triggering signal 904 may dynamically indicate the allowed number of R2D messages that can be aggregated in confirmatory response.
[0129] According to certain aspects, control information of a corresponding R2D reception may indicate whether a confirmatory response is to be transmitted or not. If the indication is the confirmatory response is to be transmitted, the ambient-IoT device may transmit the confirmatory response at the first valid resource after the end of R2D reception and, in some cases, the reception of confirmatory response triggering signal. In some cases, the resource may dynamically indicated by the control information scheduling the corresponding R2D reception.
[0130] In some cases, as illustrated in FIG. 11A, the resource allocation conveyed in an R2D reception 1102 may indicate both the starting transmission time (e.g., relative to an end of R2D reception 1102) , as well as a transmission duration for a confirmatory response resource 1106. This approach may be suitable, for example, if the ambient-IoT device have the enough energy to maintain a clock.
[0131] The resource allocation may also indicate a frequency resource (e.g., a frequency shift) for the ambient IoT device to transmit the confirmatory response (e.g., different ambient IoT devices may use different frequency shifts which may help a reader device distinguish confirmatory responses from the different ambient IoT devices.
[0132] As illustrated in FIG. 11B, in some cases, a resource allocation conveyed in an R2D reception 1152 may only indicate the frequency resource and allowed transmission duration of a resource 1156 for the ambient-IoT device to transmit the confirmatory response. In some cases, the ambient-IoT device may transmit the confirmatory response immediately after the R2D reception.
[0133] In other cases, the ambient-IoT device may transmit the confirmatory response immediately after the reception of a confirmatory response triggering signal 1154. In such cases, the triggering signal in this option may be different than in a previous option, as there may be no need to indicate a resource allocation for a confirmatory response transmission (e.g., the trigger signal may be sequence based triggering) . The options described above may be used to determine a number of R2D receptions to be acknowledged (aggregated) in a confirmatory response.
[0134] As illustrated in FIG. 12A, according to certain aspects, a periodic resource may be configured for the ambient-IoT device to transmit the confirmatory response. In such cases, a minimum time gap between the R2D reception and the confirmatory response may be defined. The minimum gap time may be pre-defined or the reader device may dynamically indicate the minimum gap time (e.g., which may be suitable for devices with higher clock reliability, such as device types 2a / 2b) .
[0135] In the example illustrated in FIG. 12A, a single time gap is defined for all type of ambient-IoT devices (e.g., types 1 / 2a / 2b) . As illustrated, a periodic resource 1206 may occur after the (common) minimum gap time. The reader may configure different periodic resources for different ambient-IoT devices, which may prevent collision. A single time gap, however, may results in a potentially larger latency for devices which have fast (er) decoding capabilities. Since different types of ambient-IoT devices may have different decoding capabilities, the time gap should consider the poorest decoding capability of the ambient-IoT device, resulting in the potentially larger latency for devices which have fast (er) decoding capabilities.
[0136] On the other hand, in the example illustrated in FIG. 12B, different minimum time gaps may be defined for different types of ambient-IoT device, which may result in confirmatory responses being transmitted in different periodic resources 1256 and 1258. In the illustrated example, the minimum gap time for device types 2a / 2b is shorter than the minimum gap time for device type 1 / 2a. The different minimum gap times for the different types of devices may be determined by considering the potentially different decoding capabilities and clock capabilities thereof.
[0137] According to certain aspects, a confirmatory response triggering signal may be transmitted before each configured resource. In such cases, an ambient-IoT device may transmit the confirmatory response at the first valid resource (that satisfies the minimum gap time) after the end of R2D reception and the reception of confirmatory response triggering signal.
[0138] In some cases, the ambient-IoT device may transmit the confirmatory response at the first valid resource after decoding an R2D signal and at least a number of received confirmatory response triggering signals (where the number may be predefined or indicated via control information scheduling an R2D reception) after the end of R2D reception.
[0139] According to certain aspects, the resource allocation for confirmatory response may be based on whether the confirmatory response is for reception results of the groupcast R2D transmission.
[0140] In some cases, the confirmatory response may be a NACK only with a single bit indication. In this case, there may be a payload based indication (i.e., to indicate a group ID and / or reader ID) or a group specified sequence based indication.
[0141] As illustrated in FIG. 13, for certain types of devices (e.g., device 2a / 2b) , a single resource 1306 may be enough (if no limit to received power at reader side) . This may work, for example, consider loose clock reliability of certain types of devices where a specified sequence (e.g., all ones) may be introduced to avoid the cancellation between two devices (transmitting on the same resource) .
[0142] For other types of devices, a resource pool 1310 may be used. In some cases, a single resource within the resource pool 1310 may be assigned, for example, for a device which has better clock reliability while the resource pool 1310 may be assigned for the device which has worse clock reliability. For such cases, the resource indication may be predefined or dynamically indicated.
[0143] In some cases, a periodic single resource may be assigned for a type of ambient IoT device with better clock reliability (i.e., device type 2a or 2b) to transmit the confirmatory response while the resource pool may be dynamically indicated for a type of device with loose clock reliability (i.e., device type 1) to transmit the confirmatory response.
[0144] According to certain aspects, if the resource pool allocation is predefined, the time duration and frequency range for the confirmatory response transmission may be indicated. In addition, a minimum time gap between the R2D reception and confirmatory response transmission may also be indicated. The minimum gap time may be predefined or the reader may dynamically indicate it. If dynamically indicated, for the time resource, the reader may indicate the time gap between the R2D reception and confirmatory response transmission, as well as the duration for the confirmatory response. For the frequency resource, the reader may indicate a frequency range and / or may also indicate candidates of the frequency shift.
[0145] According to certain aspects, if the confirmatory response is NACK only with a multiple-bit indication, an ACK only, or an ACK / NACK based indication, there may be a single resource pool is indicated or separate resources / resource pools may be indicated for ACK and NACK, respectively. Which is allocated may consider ACK / NACK based indication and one bit indication for either ACK or NACK indication (e.g., ACK only or NACK only) .
[0146] According to certain aspects, separate resources / resource pools may be indicated per type of response information. For example, a first resource / resource pool may be allocated for memory error indication and a second resource / resource pool may be allocated for reporting energy failure. In any case, the resource allocation and indication may follow any of the options mentioned above.
[0147] When there are multiple resources / resource pools allocated, the resource selection may be performed according to various options. According to a first option, the ambient-IoT device may select the resource randomly. According to a second option, the ambient-IoT device may select the resource based on the device ID. According to a third option, the ambient-IoT device may select the resource based on the resource ID. According to a fourth option, the ambient-IoT device may select the resource based on the device type. In some cases, an ambient-IoT device may select the resource based on a combination of these options.
[0148] According to certain aspects, when the ambient-IoT device transmits the confirmatory response with groupcast R2D transmission, it may also indicate various types of assistance information. For example, via such assistance information the ambient-IoT device may further indicate whether it will stay in the group or not within a timing window. In such cases, the timing window may be predefined or the ambient-IoT device may indicate the timing window (e.g., as part of the assistance information) .
[0149] Example Operations
[0150] FIG. 14 shows an example of a method 1400 of wireless communications at an ambient Internet of things (IoT) device. In some examples, the ambient Internet of things (IoT) device is a user equipment, such as a UE 104 of FIGS. 1 and 3. In some examples, the ambient Internet of things (IoT) device is a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0151] Method 1400 begins at step 1405 with receiving, from a reader device, signaling indicating at least one resource for confirmatory response transmission. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 16.
[0152] Method 1400 then proceeds to step 1410 with receiving at least one reader to device (R2D) transmission from the reader device. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 16.
[0153] Method 1400 then proceeds to step 1415 with transmitting, using the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 16.
[0154] In some aspects, the at least one R2D transmission comprises a unicast R2D transmission.
[0155] In some aspects, the signaling comprises a triggering signal to indicate the ambient IoT device is to transmit the confirmatory response.
[0156] In some aspects, the ambient IoT device is configured to transmit the confirmatory response: immediately after receiving the triggering signal; or a time duration after.
[0157] In some aspects, the at least one confirmatory response comprises a quantity of one or more confirmatory responses; and the quantity is determined via at least one of: a predefined number, an indication in the triggering signal, or via control information associated with the R2D transmission.
[0158] In some aspects, the at least one resource comprises a periodic resource.
[0159] In some aspects, the confirmatory response is transmitted subject to a minimum gap time after reception of the R2D transmission, wherein the minimum gap time is determined via: a predefined value, a dynamic indication, a common minimum gap time, or a device-specific minimum gap time.
[0160] In some aspects, the ambient IoT device is configured to transmit the confirmatory response: on a first valid resource after receiving one or more triggering signals, a first valid resource after decoding the R2D transmission, or based on control information scheduling the R2D transmission.
[0161] In some aspects, the at least one R2D transmission comprises a groupcast R2D transmission intended for a group of IoT devices.
[0162] In some aspects, the confirmatory response is used for negative acknowledgment (NACK) only.
[0163] In some aspects, the confirmatory response indicates at least one of a single NACK bit, a group ID, or a reader ID, or a group specified sequence based indication.
[0164] In some aspects, the at least one resource comprises, a single resource, a resource pool, or a combination of a single resource and a resource pool.
[0165] In some aspects, the at least one resource is configured or dynamically indicated.
[0166] In some aspects, the at least one resource is from a single resource pool configured for both ACK and NACK confirmatory responses or from separate resource pools configured for ACK and NACK confirmatory responses.
[0167] In some aspects, the separate resource pools are indicated per type of information provided in the confirmatory responses.
[0168] In some aspects, the ambient IoT device selects the at least one resource used for transmitting the confirmatory response via at least one of: random selection, based on a device ID, based on a resource ID, or based on a device type.
[0169] In some aspects, the confirmatory response is used for at least one of: a negative acknowledgment (NACK) with a multiple bit indication or positive acknowledgment (ACK) .
[0170] In some aspects, the confirmatory response indicates whether the ambient IoT device intends to stay in the group.
[0171] In one aspect, method 1400, or any aspect related to it, may be performed by an apparatus, such as communications device 1600 of FIG. 16, which includes various components operable, configured, or adapted to perform the method 1400. Communications device 1600 is described below in further detail.
[0172] Note that FIG. 14 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
[0173] FIG. 15 shows an example of a method 1500 of wireless communications at reader device. In some examples, the wireless node is a user equipment, such as a UE 104 of FIGS. 1 and 3. In some examples, the wireless node is a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0174] Method 1500 begins at step 1505 with transmitting, to an ambient Internet of things (IoT) device, signaling indicating at least one resource for confirmatory response transmission. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 16.
[0175] Method 1500 then proceeds to step 1510 with transmitting at least one reader to device (R2D) transmission to the ambient IoT device. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 16.
[0176] Method 1500 then proceeds to step 1515 with receiving, via the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 16.
[0177] In some aspects, the at least one R2D transmission comprises a unicast R2D transmission.
[0178] In some aspects, the signaling comprises a triggering signal to indicate the ambient IoT device is to transmit the confirmatory response.
[0179] In some aspects, the ambient IoT device is configured to transmit the confirmatory response: immediately after receiving the triggering signal; or a time duration after.
[0180] In some aspects, the at least one confirmatory response comprises a quantity of one or more confirmatory responses; and the quantity is determined via at least one of: a predefined number, an indication in the triggering signal, or via control information associated with the R2D transmission.
[0181] In some aspects, the at least one resource comprises a periodic resource.
[0182] In some aspects, the confirmatory response is transmitted subject to a minimum gap time after reception of the R2D transmission, wherein the minimum gap time is determined via: a predefined value, a dynamic indication, a common minimum gap time, or a device-specific minimum gap time.
[0183] In some aspects, the ambient IoT device is configured to transmit the confirmatory response: on a first valid resource after receiving one or more triggering signals, a first valid resource after decoding the R2D transmission, or based on control information scheduling the R2D transmission.
[0184] In some aspects, the at least one R2D transmission comprises a groupcast R2D transmission intended for a group of IoT devices.
[0185] In some aspects, the confirmatory response is used for negative acknowledgment (NACK) only.
[0186] In some aspects, the confirmatory response indicates at least one of a single NACK bit, a group ID, or a reader ID, or a group specified sequence based indication.
[0187] In some aspects, the at least one resource comprises, a single resource, a resource pool, or a combination of a single resource and a resource pool.
[0188] In some aspects, the at least one resource is configured or dynamically indicated.
[0189] In some aspects, the at least one resource is from a single resource pool configured for both ACK and NACK confirmatory responses or from separate resource pools configured for ACK and NACK confirmatory responses.
[0190] In some aspects, the separate resource pools are indicated per type of information provided in the confirmatory responses.
[0191] In some aspects, the ambient IoT device selects the at least one resource used for transmitting the confirmatory response via at least one of: random selection, based on a device ID, based on a resource ID, or based on a device type.
[0192] In some aspects, the confirmatory response is used for at least one of: a negative acknowledgment (NACK) with a multiple bit indication or positive acknowledgment (ACK) .
[0193] In some aspects, the confirmatory response indicates whether the ambient IoT device intends to stay in the group.
[0194] In one aspect, method 1500, or any aspect related to it, may be performed by an apparatus, such as communications device 1600 of FIG. 16, which includes various components operable, configured, or adapted to perform the method 1500. Communications device 1600 is described below in further detail.
[0195] Note that FIG. 15 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
[0196] Example Communications Device (s)
[0197] FIG. 16 depicts aspects of an example communications device 1600. In some aspects, communications device 1600 is a user equipment, such as UE 104 described above with respect to FIGS. 1 and 3. In some aspects, communications device 1600 is a network entity, such as BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0198] The communications device 1600 includes a processing system 1605 coupled to the transceiver 1645 (e.g., a transmitter and / or a receiver) . In some aspects (e.g., when communications device 1600 is a network entity) , processing system 1605 may be coupled to a network interface 1655 that is configured to obtain and send signals for the communications device 1600 via communication link (s) , such as a backhaul link, midhaul link, and / or fronthaul link as described herein, such as with respect to FIG. 2. The transceiver 1645 is configured to transmit and receive signals for the communications device 1600 via the antenna 1650, such as the various signals as described herein. The processing system 1605 may be configured to perform processing functions for the communications device 1600, including processing signals received and / or to be transmitted by the communications device 1600.
[0199] The processing system 1605 includes one or more processors 1610. In various aspects, the one or more processors 1610 may be representative of one or more of receive processor 358, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380, as described with respect to FIG. 3. In various aspects, one or more processors 1610 may be representative of one or more of receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to FIG. 3. The one or more processors 1610 are coupled to a computer-readable medium / memory 1625 via a bus 1640. In certain aspects, the computer-readable medium / memory 1625 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1610, cause the one or more processors 1610 to perform the method 1400 described with respect to FIG. 14, or any aspect related to it; and the method 1500 described with respect to FIG. 15, or any aspect related to it. Note that reference to a processor performing a function of communications device 1600 may include one or more processors 1610 performing that function of communications device 1600.
[0200] In the depicted example, computer-readable medium / memory 1625 stores code (e.g., executable instructions) , such as code for receiving 1630 and code for transmitting 1635. Processing of the code for receiving 1630 and code for transmitting 1635 may cause the communications device 1600 to perform the method 1400 described with respect to FIG. 14, or any aspect related to it; and the method 1500 described with respect to FIG. 15, or any aspect related to it.
[0201] The one or more processors 1610 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 1625, including circuitry for receiving 1615 and circuitry for transmitting 1620. Processing with circuitry for receiving 1615 and circuitry for transmitting 1620 may cause the communications device 1600 to perform the method 1400 described with respect to FIG. 14, or any aspect related to it; and the method 1500 described with respect to FIG. 15, or any aspect related to it.
[0202] Various components of the communications device 1600 may provide means for performing the method 1400 described with respect to FIG. 14, or any aspect related to it; and the method 1500 described with respect to FIG. 15, or any aspect related to it. For example, means for transmitting, sending or outputting for transmission may include transceivers 354 and / or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and / or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and / or the transceiver 1645 and the antenna 1650 of the communications device 1600 in FIG. 16. Means for receiving or obtaining may include transceivers 354 and / or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and / or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and / or the transceiver 1645 and the antenna 1650 of the communications device 1600 in FIG. 16.
[0203] Example Clauses
[0204] Implementation examples are described in the following numbered clauses:
[0205] Clause 1: A method for wireless communications at an ambient Internet of things (IoT) device, comprising: receiving, from a reader device, signaling indicating at least one resource for confirmatory response transmission; receiving at least one reader to device (R2D) transmission from the reader device; and transmitting, using the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.
[0206] Clause 2: The method of Clause 1, wherein: the at least one R2D transmission comprises a unicast R2D transmission.
[0207] Clause 3: The method of Clause 2, wherein the signaling comprises a triggering signal to indicate the ambient IoT device is to transmit the confirmatory response.
[0208] Clause 4: The method of Clause 3, wherein the ambient IoT device is configured to transmit the confirmatory response: immediately after receiving the triggering signal; or a time duration after receiving the at least one R2D transmission.
[0209] Clause 5: The method of Clause 3, wherein: the at least one confirmatory response aggregates acknowledgment information for a quantity of R2D transmissions; and the quantity is determined via at least one of: a predefined number, an indication in the triggering signal, or via control information associated with the at least one R2D transmission.
[0210] Clause 6: The method of Clause 2, wherein the at least one resource comprises a periodic resource.
[0211] Clause 7: The method of Clause 6, wherein the confirmatory response is transmitted subject to a minimum gap time after reception of the R2D transmission, wherein the minimum gap time is determined via: a predefined value, a dynamic indication, a common minimum gap time, or a device-specific minimum gap time.
[0212] Clause 8: The method of Clause 6, wherein the at least one resource comprises a first valid resource after receiving one or more triggering signals, a first valid resource after decoding the R2D transmission, or a resource determined based on control information scheduling the R2D transmission.
[0213] Clause 9: The method of any one of Clauses 1-8, wherein: the at least one R2D transmission comprises a groupcast R2D transmission intended for a group of IoT devices.
[0214] Clause 10: The method of Clause 9, wherein the confirmatory response is used for negative acknowledgment (NACK) only.
[0215] Clause 11: The method of Clause 10, wherein the confirmatory response indicates at least one of a single NACK bit, a group ID, or a reader ID, or a group specified sequence based indication.
[0216] Clause 12: The method of Clause 11, wherein the at least one resource comprises, a single resource, a resource pool, or a combination of a single resource and a resource pool.
[0217] Clause 13: The method of Clause 12, wherein the at least one resource is configured or dynamically indicated.
[0218] Clause 14: The method of Clause 9, wherein the confirmatory response is used to convey at least one of: a negative acknowledgment (NACK) or a positive acknowledgment (ACK) .
[0219] Clause 15: The method of Clause 14, wherein the at least one resource is from a single resource pool configured for both ACK and NACK confirmatory responses or from separate resource pools configured for ACK and NACK confirmatory responses.
[0220] Clause 16: The method of Clause 15, wherein the separate resource pools are indicated per type of information provided in the confirmatory responses.
[0221] Clause 17: The method of Clause 15, wherein the ambient IoT device selects the at least one resource used for transmitting the confirmatory response via at least one of:random selection, based on a device ID, based on a resource ID, or based on a device type.
[0222] Clause 18: The method of Clause 9, wherein the confirmatory response indicates whether the ambient IoT device intends to stay in the group.
[0223] Clause 19: A method for wireless communications at reader device, comprising: transmitting, to an ambient Internet of things (IoT) device, signaling indicating at least one resource for confirmatory response transmission; transmitting at least one reader to device (R2D) transmission to the ambient IoT device; and receiving, via the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.
[0224] Clause 20: The method of Clause 19, wherein: the at least one R2D transmission comprises a unicast R2D transmission.
[0225] Clause 21: The method of Clause 20, wherein the signaling comprises a triggering signal to indicate the ambient IoT device is to transmit the confirmatory response.
[0226] Clause 22: The method of Clause 21, wherein the ambient IoT device is configured to transmit the confirmatory response: immediately after receiving the triggering signal; or a time duration after.
[0227] Clause 23: The method of Clause 21, wherein: the at least one confirmatory response aggregates acknowledgment information for a quantity of R2D transmissions; and the quantity is determined via at least one of: a predefined number, an indication in the triggering signal, or via control information associated with the at least one R2D transmission.
[0228] Clause 24: The method of Clause 20, wherein the at least one resource comprises a periodic resource.
[0229] Clause 25: The method of Clause 24, wherein the confirmatory response is transmitted subject to a minimum gap time after reception of the R2D transmission, wherein the minimum gap time is determined via: a predefined value, a dynamic indication, a common minimum gap time, or a device-specific minimum gap time.
[0230] Clause 26: The method of Clause 24, wherein the at least one resource comprises a first valid resource after receiving one or more triggering signals, a first valid resource after decoding the R2D transmission, or a resource determined based on control information scheduling the R2D transmission.
[0231] Clause 27: The method of any one of Clauses 19-26, wherein: the at least one R2D transmission comprises a groupcast R2D transmission intended for a group of IoT devices.
[0232] Clause 28: The method of Clause 27, wherein the confirmatory response is used for negative acknowledgment (NACK) only.
[0233] Clause 29: The method of Clause 28, wherein the confirmatory response indicates at least one of a single NACK bit, a group ID, or a reader ID, or a group specified sequence based indication.
[0234] Clause 30: The method of Clause 29, wherein the at least one resource comprises, a single resource, a resource pool, or a combination of a single resource and a resource pool.
[0235] Clause 31: The method of Clause 30, wherein the at least one resource is configured or dynamically indicated.
[0236] Clause 32: The method of Clause 27, wherein the confirmatory response is used for at least one of: a negative acknowledgment (NACK) with a multiple bit indication or positive acknowledgment (ACK) .
[0237] Clause 33: The method of Clause 29, wherein the at least one resource is from a single resource pool configured for both ACK and NACK confirmatory responses or from separate resource pools configured for ACK and NACK confirmatory responses.
[0238] Clause 34: The method of Clause 33, wherein the separate resource pools are indicated per type of information provided in the confirmatory responses.
[0239] Clause 35: The method of Clause 33, wherein the ambient IoT device selects the at least one resource used for transmitting the confirmatory response via at least one of: random selection, based on a device ID, based on a resource ID, or based on a device type.
[0240] Clause 36: The method of Clause 27, wherein the confirmatory response indicates whether the ambient IoT device intends to stay in the group.
[0241] Clause 37: An apparatus, comprising: at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method in accordance with any combination of Clauses 1-36.
[0242] Clause 38: An apparatus, comprising means for performing a method in accordance with any combination of Clauses 1-36.
[0243] Clause 39: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of an apparatus, cause the apparatus to perform a method in accordance with any combination of Clauses 1-36.
[0244] Clause 40: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any combination of Clauses 1-36.
[0245] Additional Considerations
[0246] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting of the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
[0247] The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a graphics processing unit (GPU) , a neural processing unit (NPU) , a digital signal processor (DSP) , an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD) , 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 the alternative, the processor may be any commercially available 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, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC) , or any other such configuration.
[0248] As used herein, “a processor, ” “at least one processor” or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance of the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation. Similarly, “a memory, ” “at least one memory” or “one or more memories” generally refers to a single memory configured to store data and / or instructions, multiple memories configured to collectively store data and / or instructions.
[0249] In some cases, rather than actually transmitting a signal, an apparatus (e.g., a wireless node or device) may have an interface to output the signal for transmission. For example, a processor may output a signal, via a bus interface, to a radio frequency (RF) front end for transmission. Accordingly, a means for outputting may include such an interface as an alternative (or in addition) to a transmitter or transceiver. Similarly, rather than actually receiving a signal, an apparatus (e.g., a wireless node or device) may have an interface to obtain a signal from another device. For example, a processor may obtain (or receive) a signal, via a bus interface, from an RF front end for reception. Accordingly, a means for obtaining may include such an interface as an alternative (or in addition) to a receiver or transceiver.
[0250] While the present disclosure may describe certain operations as being performed by one type of wireless node, the same or similar operations may also be performed by another type of wireless node. For example, operations performed by a user equipment (UE) may also (or instead) be performed by a network entity (e.g., a base station or unit of a disaggregated base station) . Similarly, operations performed by a network entity may also (or instead) be performed by a UE.
[0251] Further, while the present disclosure may describe certain types of communications between different types of wireless nodes (e.g., between a network entity and a UE) , the same or similar types of communications may occur between same types of wireless nodes (e.g., between network entities or between UEs, in a peer-to-peer scenario) . Further, communications may occur in reverse order than described.
[0252] Means for receiving, and means for transmitting may comprise one or more processors, such as one or more of the processors described above with reference to FIG. 16.
[0253] As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
[0254] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
[0255] The methods disclosed herein comprise one or more actions for achieving the methods. The method actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component (s) and / or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0256] The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112 (f) unless the element is expressly recited using the phrase “means for” . All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.
Claims
1.An apparatus for wireless communication at an ambient Internet-of-Things (IoT) device, comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions and cause the apparatus to:receive, from a reader device, signaling indicating at least one resource for confirmatory response transmission;receive at least one reader to device (R2D) transmission from the reader device; andtransmit, using the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.2.The apparatus of claim 1, wherein the at least one R2D transmission comprises a unicast R2D transmission.3.The apparatus of claim 2, wherein the signaling comprises a triggering signal to indicate the ambient IoT device is to transmit the confirmatory response.4.The apparatus of claim 3, wherein the ambient IoT device is configured to transmit the confirmatory response:immediately after receiving the triggering signal; ora time duration after receiving the at least one R2D transmission.5.The apparatus of claim 3, wherein:the at least one confirmatory response aggregates acknowledgment information for a quantity of R2D transmissions; andthe quantity is determined via at least one of: a predefined number, an indication in the triggering signal, or via control information associated with the at least one R2D transmission.6.The apparatus of claim 2, wherein the at least one resource comprises a periodic resource.7.The apparatus of claim 6, wherein the confirmatory response is transmitted subject to a minimum gap time after reception of the R2D transmission, wherein the minimum gap time is determined via: a predefined value, a dynamic indication, a common minimum gap time, or a device-specific minimum gap time.8.The apparatus of claim 6, wherein the at least one resource comprises a first valid resource after receiving one or more triggering signals, a first valid resource after decoding the R2D transmission, or a resource determined based on control information scheduling the R2D transmission.9.The apparatus of claim 1, wherein the at least one R2D transmission comprises a groupcast R2D transmission intended for a group of IoT devices.10.The apparatus of claim 9, wherein the confirmatory response is used for negative acknowledgment (NACK) only.11.The apparatus of claim 10, wherein the confirmatory response indicates at least one of a single NACK bit, a group ID, or a reader ID, or a group specified sequence based indication.12.The apparatus of claim 11, wherein the at least one resource comprises, a single resource, a resource pool, or a combination of a single resource and a resource pool.13.The apparatus of claim 12, wherein the at least one resource is configured or dynamically indicated.14.The apparatus of claim 9, wherein the confirmatory response is used to convey at least one of: a negative acknowledgment (NACK) or a positive acknowledgment (ACK) .15.The apparatus of claim 14, wherein the at least one resource is from a single resource pool configured for both ACK and NACK confirmatory responses or from separate resource pools configured for ACK and NACK confirmatory responses.16.The apparatus of claim 15, wherein the separate resource pools are indicated per type of information provided in the confirmatory responses.17.The apparatus of claim 15, wherein the ambient IoT device selects the at least one resource used for transmitting the confirmatory response via at least one of: random selection, based on a device ID, based on a resource ID, or based on a device type.18.The apparatus of claim 9, wherein the confirmatory response indicates whether the ambient IoT device intends to stay in the group.19.An apparatus for wireless communication at a reader device, comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions and cause the apparatus to:transmit, to an ambient Internet of things (IoT) device, signaling indicating at least one resource for confirmatory response transmission;transmit at least one reader to device (R2D) transmission to the ambient IoT device; andreceive, via the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.20.The apparatus of claim 19, wherein the at least one R2D transmission comprises a unicast R2D transmission.21.The apparatus of claim 20, wherein the signaling comprises a triggering signal to indicate the ambient IoT device is to transmit the confirmatory response.22.The apparatus of claim 21, wherein the reader device is configured to receive the confirmatory response: immediately after transmitting the triggering signal; or a time duration after transmitting the at least one R2D transmission.23.The apparatus of claim 21, wherein:the at least one confirmatory response aggregates acknowledgment information for a quantity of R2D transmissions; andthe quantity is determined via at least one of: a predefined number, an indication in the triggering signal, or via control information associated with the at least one R2D transmission.24.The apparatus of claim 20, wherein the at least one resource comprises a periodic resource.25.The apparatus of claim 24, wherein the confirmatory response is transmitted subject to a minimum gap time after reception of the R2D transmission, wherein the minimum gap time is determined via: a predefined value, a dynamic indication, a common minimum gap time, or a device-specific minimum gap time.26.The apparatus of claim 24, wherein the at least one resource comprises a first valid resource after receiving one or more triggering signals, a first valid resource after decoding the R2D transmission, or a resource determined based on control information scheduling the R2D transmission.27.The apparatus of claim 19, wherein the at least one R2D transmission comprises a groupcast R2D transmission intended for a group of IoT devices.28.The apparatus of claim 27, wherein the confirmatory response is used for negative acknowledgment (NACK) only.29.A method for wireless communications at an ambient Internet of things (IoT) device, comprising:receiving, from a reader device, signaling indicating at least one resource for confirmatory response transmission;receiving at least one reader to device (R2D) transmission from the reader device; andtransmitting, using the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.30.A method for wireless communications at reader device, comprising:transmitting, to an ambient Internet of things (IoT) device, signaling indicating at least one resource for confirmatory response transmission;transmitting at least one reader to device (R2D) transmission to the ambient IoT device; andreceiving, via the at least one resource, at least one confirmatory response acknowledging the at least one R2D transmission.
Citation Information
Patent Citations
Feedback information transmission method, communication device and storage medium
CN118056368A
Transmission method and apparatus
WO2024140725A1