IOT (IoT)-BASED POSITIONING

Abstract

Aspects presented herein may enable a wireless device to communicate with a network entity for receiving a configuration associated with positioning of an RFID tag. In one aspect, a wireless device sends a set of requests to a network entity to estimate a range between the wireless device and an IoT device or to estimate a location of the IoT device. The wireless device transmits or receives an indication indicating a positioning method for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device. The wireless device receives at least one response from the network entity, the at least one response including a configuration for a set of resources for estimating the range between the wireless device and the IoT device or estimating the location of the IoT device based on the set of requests and the indicated location method.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems, and more particularly to wireless communication regarding positioning. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with respect to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Additionally, these improvements may also apply to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0004] A simplified summary of one or more aspects is presented below in order to provide a basic understanding of these aspects. This summary of the invention is not an extensive overview of all contemplated aspects. The summary of the invention neither identifies key or critical elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus sends a set of requests to a network entity for estimating a range between a wireless device and an Internet of Things (IoT) device or for estimating a location of the IoT device. The apparatus sends or receives an indication indicating a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, where the indication is sent to the network entity or received from the network entity. The apparatus receives at least one response from the network entity, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives a set of requests from a wireless device for estimating a range between the wireless device and an IoT device or for estimating a location of the IoT device. The apparatus sends or receives an indication indicating a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, where the indication is sent to the wireless device or received from the wireless device. The apparatus sends at least one response to the wireless device, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

[0007] To achieve the foregoing and related purposes, one or more aspects include the features described comprehensively below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0009] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0010] Figure 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe according to various aspects of the present disclosure.

[0011] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0012] Figure 2DIs a diagram illustrating an example of an uplink (UL) channel within a subframe according to various aspects of the present disclosure.

[0013] Figure 3 Is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0014] Figure 4 Is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0015] Figure 5 Is a diagram illustrating an example of a radio frequency identification (RFID) tag according to various aspects of the present disclosure.

[0016] Figure 6 Is a diagram illustrating an example of different types of Internet of Things (IoT) devices according to various aspects of the present disclosure.

[0017] Figure 7 Is a diagram illustrating an example of a passive IoT device performing backscattering / reflection of a modulated signal according to various aspects of the present disclosure.

[0018] Figure 8A Is a diagram illustrating an example of a network entity communicating directly with an RFID reader according to various aspects of the present disclosure.

[0019] Figure 8B Is a diagram illustrating an example of a network entity communicating with an RFID via a relay device according to various aspects of the present disclosure.

[0020] Figure 8C Is a diagram illustrating an example of a network entity communicating with an RFID via a relay device according to various aspects of the present disclosure.

[0021] Figure 9 Is a diagram illustrating an example of a network entity communicating with a set of IoT devices according to various aspects of the present disclosure.

[0022] Figure 10 Is a diagram illustrating an example of estimating the distance between an RFID reader and an RFID tag based on frequency domain (FD) phase difference of arrival (PDOA) (FD-PDOA) according to various aspects of the present disclosure.

[0023] Figure 11 Is a diagram illustrating an example of a network entity configuring a set of resources associated with PDOA positioning for an RFID reader according to various aspects of the present disclosure.

[0024] Figure 12 Is a diagram illustrating an example of a phase value distribution associated with FD-PDOA positioning of an RFID tag according to various aspects of the present disclosure.

[0025] Figure 13 is a diagram illustrating examples of the coherence bandwidth and coherence time according to various aspects of the present disclosure.

[0026] Figure 14 is a diagram illustrating an example of an RFID reader determining the location of an RFID tag according to various aspects of the present disclosure.

[0027] Figure 15A is a diagram illustrating an example of a fast-moving RFID reader according to various aspects of the present disclosure.

[0028] Figure 15B is a diagram illustrating an example of a slow-moving RFID reader according to various aspects of the present disclosure.

[0029] Figure 16 is a diagram illustrating an example of a positioning for IoT devices according to various aspects of the present disclosure.

[0030] Figure 17 is a flowchart of a wireless communication method.

[0031] Figure 18 is a diagram illustrating an example of a hardware implementation for an example device and / or network entity.

[0032] Figure 19 is a flowchart of a wireless communication method.

[0033] Figure 20 is a diagram illustrating an example of a hardware implementation for an example device and / or network entity. Detailed Description

[0034] Aspects presented herein may enable a network entity to configure a radio frequency identification (RFID) reader to estimate / determine the location or distance of an RFID tag based on phase difference of arrival (PDOA) positioning. For example, when an RFID reader (e.g., a UE) is configured to locate / determine the location of an RFID tag and the RFID reader is also capable of communicating with a network entity (e.g., a base station), the RFID reader may transmit a positioning request to the network entity. Based on the positioning request, the network entity may configure one or more parameters associated with PDOA positioning for the RFID reader, such as the frequency and / or time resources, bandwidth, and / or number of repetitions for PDOA positioning.

[0035] Aspects presented herein can improve the positioning efficiency and accuracy of RFID tags performed by an RFID reader. In one aspect, the RFID reader can indicate to a network entity, such as via a reader positioning request, at least one positioning method (e.g., positioning based on received signal strength indicator (RSSI), positioning based on PDOA, positioning based on time difference of arrival (TDOA), etc.) that it is configured to use. In response, the network entity can provide a suitable configuration (such as resource allocation) for the RFID reader based on the indicated positioning method (e.g., via a network positioning response). In another aspect, since different positioning methods can specify different positioning accuracies, the RFID reader can also report / indicate its positioning accuracy requirements to the network entity instead of explicitly indicating different positioning methods to the network entity (e.g., via a reader positioning request). In response, the network entity can provide a suitable configuration for the RFID reader based on the positioning accuracy requirements (e.g., via a network positioning response). In some examples, in addition to the RFID reader determining the positioning method, the network entity can also be configured to determine at least one positioning method for the RFID reader, such as via L1 / L2 / L3 signaling or a network positioning response.

[0036] The detailed description set forth below in connection with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. For a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0037] Certain aspects of a telecommunications system are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using either electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0038] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0039] Thus, in one or more example aspects, embodiments, and / or use cases, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded on a computer-readable medium as one or more instructions or code. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium capable of storing computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0040] While aspects, embodiments, and / or use cases are described herein by way of illustration of some examples, additional or different aspects, embodiments, and / or use cases may arise in many different arrangements and scenarios. The aspects, embodiments, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, embodiments, and / or use cases may be embodied via integrated chips and other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically targeted at a use case or application, the examples described may have broad applicability. Aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies herein. In some practical settings, devices incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The technologies described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0041] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions can be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0042] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0043] Base station operation or network design may consider the converged characteristics of base station functionality. For example, a split base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration as initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtualizing the functions of at least one unit, which may enable flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0044] Figure 1 FIG. 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a split base station architecture. The split base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via a respective midhaul link, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via a respective fronthaul link. The RU 140 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 140.

[0045] Each unit (i.e., CU 110, DU 130, RU 140, and the near RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0046] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RA configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0047] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of the Radio Link Control (RLC) layer, 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, etc.) at least partially according to a functional split (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with the control functions hosted by CU 110.

[0048] The lower layer functionality can be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 can correspond to logical nodes that host 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, etc.) or both, at least partially based on function splitting (such as lower layer function splitting). In such architectures, the RUs 140 can be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of the control and user plane communication with the RUs 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0049] The SMO framework 105 can be configured to support the deployment and orchestration of RANs for both non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 110, DU 130, RU 140, and the near RT RIC 125. In some embodiments, the SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some embodiments, the SMO framework 105 can communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 can also include the non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0050] The non-RT RIC 115 can be configured to include logic functions that can implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (such as via the A1 interface). The near-RT RIC 125 can be configured to include logic functions that can implement near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and the interface (such as via the E2 interface) connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

[0051] In some specific implementations, to generate the AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external rich information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or from network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ the AI / ML model to perform corrective actions through the SMO framework 105 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0052] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Thus, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides an access point for UE 104 to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. For each carrier allocated in carrier aggregation of up to a total of Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0053] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication 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), and a physical sidelink control channel (PSCCH). D2D communication may be via various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0054] The wireless communication system may further include a Wi-Fi AP 150 that communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in a 5 GHz unlicensed spectrum, etc. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0055] The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0056] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz to 24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0057] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used in this article, it may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" etc. is used in this article, it may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0058] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signal 182 to UE 104 in one or more transmission directions. UE 104 may receive the beamformed signal from base station 102 in one or more reception directions. UE 104 may also transmit beamformed signal 184 to base station 102 in one or more transmission directions. Base station 102 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 102 / UE 104 may perform beam training to determine the optimal reception direction and transmission direction for each of base station 102 / UE 104. The transmission direction and reception direction of base station 102 may be the same or may not be the same. The transmission direction and reception direction of UE 104 may be the same or may not be the same.

[0059] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission and reception point (TRP), network node, network entity, network equipment, or some other suitable term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including CU and DU) and an RU, or may be implemented as a disaggregated base station including one or more of CU, DU, and / or RU. A set of base stations including disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0060] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that processes signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, one or more location servers 168 may include one or more location / locationing servers, which may include one or more of the GMLC 165, LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. The signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a Satellite Positioning System (SPS) 170 (e.g., a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a Non-Terrestrial Network (NTN), or one or more of other satellite positioning / locationing systems), an LTE signal, a Wireless Local Area Network (WLAN) signal, a Bluetooth signal, a Terrestrial Beacon System (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR Enhanced Cell ID (NR E-CID) method, an NR signal (e.g., multi-round-trip time (multi-RTT), DL Angle of Departure (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0061] Examples of the UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, transportation vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functionality. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, transportation vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device cluster arrangement. One or more of these devices may access the network jointly and / or access the network individually.

[0062] Referring again to Figure 1 , in some aspects, the UE 104 may be configured to send a set of requests to a network entity for estimating the range between a wireless device and an IoT device or for estimating the location of the IoT device; send or receive an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, where the indication is sent to or received from the network entity; and receive at least one response from the network entity, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method (e.g., via the IoT device positioning component 198).

[0063] In some aspects, the base station 102 may be configured to: receive a set of requests from a wireless device for estimating the range between the wireless device and an IoT device or for estimating the location of the IoT device; send or receive an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, where the indication is sent to or received from the wireless device; and send at least one response to the wireless device, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method (e.g., via the IoT device positioning configuration component 199).

[0064] Figure 2AFIG. 200 is an illustration example of a first subframe within a 5G NR frame structure. Figure 2B FIG. 230 is an illustration example of a DL channel within a 5G NR subframe. Figure 2C FIG. 250 is an illustration example of a second subframe within a 5G NR frame structure. Figure 2D FIG. 280 is an illustration example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be frequency division duplexing (FDD) (where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL), or can be time division duplexing (TDD) (where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both DL and UL). In Figure 2A , Figure 2C the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly available between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3, 4 are shown as having slot formats 1, 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0, 1 are all DL, all UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by receiving a slot format indicator (SFI) (configured dynamically by DL control information (DCI) or semi-statically / statically by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0065] Figures 2A to 2DA frame structure is illustrated, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbols on the DL may be cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see

[0066] Table 1). The symbol length / duration may be scaled with 1 / SCS.

[0067]

[0068] Table 1: Parameter Sets, SCS, and CP

[0069] For normal CP (14 symbols / slot), the different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 time slots per subframe, respectively. For extended CP, parameter set 2 allows 4 time slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ time slots / subframe. The subcarrier spacing may be equal to 2 μ * 15 kHz, where μ is parameter set 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example is provided with normal CP having 14 symbols per time slot and parameter set μ = 2 having 4 time slots per subframe. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0070] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0071] As Figure 2A Illustrated, some of the REs in the RE carry reference (pilot) signals (RSs) for the UE. The RS can include a demodulation RS (DM-RS) (designated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS can also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0072] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six resource element groups (REGs), each REG including 12 consecutive REs in the OFDM symbols of an RB. The PDCCH within a BWP can be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring occasion on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) can be in symbol 2 of a particular subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) can be in symbol 4 of a particular subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and the SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) not transmitted via the PBCH, and paging messages.

[0073] As Figure 2CAs illustrated, some of the REs in the RE carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can send the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of the teeth of the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0074] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0075] Figure 3It is a block diagram of the communication between the base station 310 and the UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0076] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols are then split into parallel streams. Subsequently, each stream is mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is space precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 can be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Each spatial stream is then provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx modulates a radio frequency (RF) carrier using the corresponding spatial stream for transmission.

[0077] At the UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signals, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0078] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0079] Similar to the functionality described in connection with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0080] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate decoding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0081] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides this information to the RX processor 370.

[0082] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0083] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects in conjunction with Figure 1 IoT device positioning component 198.

[0084] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects in conjunction with Figure 1 IoT device positioning configuration component 199.

[0085] Figure 4 FIG. 400 is an illustration of an example of UE positioning based on reference signal measurements (which may also be referred to as “network-based positioning”) in accordance with various aspects of the present disclosure. UE 404 may transmit UL-SRS 412 at time T SRS_TX and receive a downlink positioning reference signal (PRS) (DL-PRS) 410 at time T PRS_RX . TRP 406 may receive UL-SRS 412 at time T SRS_RX and transmit DL-PRS 410 at time T PRS_TX . UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine the RTT 414 based on ||T SRS_RX –T PRS_TX |–|T SRS_TX –T PRS_RX ||. Thus, multi-RTT positioning may utilize UE Rx-Tx time difference measurements of downlink signals received from multiple TRPs 402, 406 and measured by UE 404 (i.e., |T SRS_TX –T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), as well as measured TRP Rx-Tx time difference measurements of uplink signals transmitted from UE 404 at multiple TRPs 402, 406 (i.e., |T SRS_RX –T PRS_TX|) and UL-SRS-RSRP. The UE 404 uses the assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and / or the DL-PRS-RSRP of the received signal), and the TRPs 402, 406 use the assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and / or the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the location of the UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0086] The PRS can be defined for network-based positioning (e.g., NR positioning) such that the UE can detect and measure more adjacent transmit and receive points (TRPs), where multiple configurations are supported to enable various deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). To support PRS beam operation, beam scanning can also be configured for the PRS. The UL positioning reference signal can be based on the sounding reference signal (SRS) with enhancements / modifications for positioning purposes. In some examples, the UL-PRS can be referred to as "SRS for positioning", and new information elements (IEs) can be configured for the SRS for positioning in RRC signaling.

[0087] The DL PRS-RSRP can be defined as the linear average of the power contributions (in [W]) of the resource elements of the antenna port carrying the DL PRS reference signal configured for RSRP measurement within the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for DL PRS-RSRP can be the antenna connector of the UE. For FR2, the DL PRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the UE uses receiver diversity, the reported DL PRS-RSRP value may not be lower than the corresponding DL PRS-RSRP of any individual receiver branch in the individual receiver branches. Similarly, the UL SRS-RSRP can be defined as the linear average of the power contributions (in [W]) of the resource elements carrying the sounding reference signal (SRS). The UL SRS-RSRP can be measured within the considered measurement frequency bandwidth, at the configured measurement occasion, by the configured resource elements. In some examples, for FR1, the reference point for UL SRS-RSRP can be the antenna connector of the base station (e.g., gNB). For FR2, the UL SRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the base station uses receiver diversity, the reported UL SRS-RSRP value may not be lower than the corresponding UL SRS-RSRP of any individual receiver branch in the individual receiver branches.

[0088] The PRS-path RSRP (PRS-RSRPP) can be defined as the power of the linear average of the channel response at the i-th path delay of the resource elements carrying the DL PRS signal configured for measurement, where the DL PRS-RSRPP of the first path delay is the power contribution corresponding to the path first detected in time. In some examples, the PRS path phase measurement can refer to the phase associated with the i-th path of the channel derived using the PRS resources.

[0089] DL-AoD positioning can utilize the measured DL-PRS-RSRP of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 measures the DL-PRS-RSRP of the received signals using the assistance data received from the positioning server, and the resulting measurement, together with the azimuth angle of departure (A-AoD), zenith angle of departure (Z-AoD), and other configuration information, is used to position the UE 404 relative to the adjacent TRPs 402, 406.

[0090] DL-TDOA positioning can utilize the downlink reference signal time difference (RSTD) (and / or DL-PRS-RSRP) of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL RSTD (and / or DL-PRS-RSRP) of the received signals, and the resulting measurements, together with other configuration information, are used to position the UE 404 relative to the neighboring TRPs 402, 406.

[0091] UL-TDOA positioning can utilize the uplink relative time of arrival (RToA) (and / or UL SRS-RSRP) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use the assistance data received from the positioning server to measure the UL-RToA (and / or UL SRS-RSRP) of the received signals, and the resulting measurements, together with other configuration information, are used to estimate the location of the UE 404.

[0092] UL-AoA positioning can utilize the measured azimuth of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use the assistance data received from the positioning server to measure the A-AoA and Z-AoA of the received signals, and the resulting measurements, together with other configuration information, are used to estimate the location of the UE 404. For the purposes of this disclosure, a positioning operation in which the UE provides measurements to a base station / location entity / server for use in calculating UE positioning may be described as "UE-assisted", "UE-assisted positioning", and / or "UE-assisted positioning calculation", while a positioning operation in which the UE measures and calculates its own positioning may be described as "UE-based", "UE-based positioning", and / or "UE-based positioning calculation".

[0093] Additional positioning methods can be used to estimate the location of the UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various techniques can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information.

[0094] Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish the types of PRS, downlink positioning reference signals may be referred to as "DL PRS", and uplink positioning reference signals (e.g., SRS, PTRS for positioning) may be referred to as "UL-PRS". In addition, for signals that can be transmitted in both the uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS".

[0095] In some scenarios, the positioning of an object can be performed using Internet of Things (IoT) devices, such as by attaching an IoT device to the object and measuring the signals backscattered / reflected from the IoT device. For example, one or more wireless devices (e.g., UE, base station, components of a base station, transmit-receive point (TRP), or a combination thereof) can send signals to the IoT device (e.g., the device to be tracked or the device attached to the object to be tracked), and one or more wireless devices can receive the signals reflected / backscattered from the IoT device (which may be hereinafter referred to as "backscattered signals") and measure the received backscattered signals. For example, one or more wireless devices can measure the round-trip time (RTT), time of arrival (ToA), angle of arrival (AoA) of the backscattered signals, and other positioning-related measurements described in combination (which may be hereinafter referred to as "positioning measurements"). Based on the positioning measurements for the backscattered signals, the positioning and / or relative positioning of the IoT device can be calculated, estimated, and / or determined. The relative positioning of the IoT device may refer to the positioning of the IoT device relative to another device or entity (such as a UE or a base station). For example, the relative positioning of the IoT device may be ten (10) meters away from the base station, located on the east side of the base station, etc. For the purposes of this disclosure, an IoT device may refer to a device that can be wirelessly connected to a network and has the ability to send data. For example, an IoT device can be a piece of hardware that is programmed for a specific application and can send data over the Internet or other networks, such as sensors, actuators, gadgets, appliances, or machines. Figure 4

[0096] ​In some examples, an IoT device may be referred to as a Radio Frequency Identification (RFID), RFID tag (or simply tag), RFID device, passive RFID, backscatter-based RFID, or backscatter-based IoT, etc. (collectively referred to as "RFID tag" or "passive IoT device" hereinafter). FRID may refer to a form of wireless communication that includes using electromagnetic or electrostatic coupling in the radio frequency part of the electromagnetic spectrum to uniquely identify objects, animals, or people, etc. A device capable of reading the information sent from the IoT device may be referred to as a backscatter receiver, backscatter reader, RFID reader, RFID reader UE, and / or reader UE, etc. (collectively referred to as "RFID reader" hereinafter). Additionally, a wireless device that sends signals to the IoT device (which may be a different entity from the RFID reader) may be referred to as an RF source, RF source UE, or carrier transmitter. Note that a wireless device / entity may be capable of both sending signals to the IoT device and receiving reflected signals (e.g., readings) from the IoT device, and the IoT device may be referred to as a full-duplex device. Thus, an RF source can also be an RFID reader, and vice versa.

[0097] RFID is a rapidly evolving technology that impacts many industries due to its economic potential in inventory / asset management (e.g., asset tracking, asset monitoring, etc.) in indoor and outdoor environments such as inside or outside a warehouse, IoT, sustainable sensor networks in factories and / or agriculture, and smart homes, etc. Additionally, some IoT devices may operate without an internal power source, and in some examples, these IoT devices may be referred to as zero-power (ZP)-IoT (ZP-IoT) devices. ZP-IoT devices are capable of relying on energy harvesting and passive communication (or low-power communication) technologies such as backscatter communication. Using such technologies, low-power and low-cost IoT devices can be achieved. For example, in some commercial communication systems, the Ultra-High Frequency Radio Frequency Identification (UHF RFID) system has matured and is widely used worldwide, and it is also based on backscatter communication. However, the UHF RFID system can be configured to operate in the Industrial, Scientific, and Medical (ISM) band, while other telecommunication systems such as the NR system can operate in a licensed band.

[0098] Figure 5FIG. 500 is a diagram illustrating an example RFID tag according to various aspects of the present disclosure, which may also be a zero-power IoT device. The RFID tag 502 (e.g., a passive / ZP-IoT device) may include a small transponder that emits an information-bearing signal upon receipt of a signal (e.g., from an RFID reader 504). The RFID tag 502 may operate without a battery at a low operating expense (OPEX), at a low maintenance cost, and / or with a long life cycle. As shown at 506, the RFID tag 502 may absorb / harvest energy in the air based on an energy signal transmitted from the RFID reader 504 (e.g., via a forward link (FL)) to power its transmit / receive circuitry. Then, as shown at 508, the RFID tag 502 may use the absorbed / harvested energy to send (e.g., reflect / backscatter) an information signal (e.g., a signal containing information, a 1-bit indication, a multi-bit indication, etc.) to the RFID reader 504 (e.g., via a backscatter link (BL)), where the transmitted information signal may generally be backscatter modulated (e.g., modulated based on the signal received from the RFID reader 504). There may also be RFID tags with batteries (which may be referred to as semi-passive or active RFID tags), which generally have a higher cost compared to battery-less RFID tags.

[0099] Figure 6 FIG. 600 is a diagram illustrating examples of different types of IoT devices (e.g., RFID tags) according to various aspects of the present disclosure. The IoT device may be configured as a passive IoT device or an active IoT device. For example, as shown at 604, a passive IoT device 602 (e.g., a ZP-IoT device) may not have a battery in its terminal, but its terminal may accumulate (e.g., absorb or harvest) energy from radio signaling (e.g., radio signaling transmitted from a base station, an RF source, a wireless device, a UE, etc.). In another example, as shown at 606, the passive IoT device 602 may include a supercapacitor, where the terminal of the passive IoT device 602 may accumulate energy from other energy sources such as the sun, wind, thermoelectricity, etc. as a supplement. In another example, as shown at 608, the passive IoT device 602 may be configured as a semi-passive device with a battery, which may enable the passive IoT device 602 to modulate / transmit a signal using power from the battery, and the passive IoT device 602 may be able to be almost always active but may not actively transmit. For a passive IoT device, a user may connect to it and receive information from it. On the other hand, an active IoT device 610 may send information as a timed stream, a threshold stream, and / or a constant stream (e.g., may be performed without first receiving a signal from an RF source). For example, an active IoT device or a semi-active IoT device may include amplification capabilities and / or active RF components, which may enable the IoT device to send better quality transmissions / information.

[0100] Figure 7 FIG. 700 is an illustration of an example of a passive IoT device (e.g., RFID tag) performing backscattering / reflection of a modulated signal in accordance with various aspects of the present disclosure. In one example, one of the primary information modulation methods used by a passive IoT device (e.g., RFID tag 704) can be amplitude shift keying (ASK), where the passive IoT device can be configured to turn on reflection when transmitting information bit "1" and turn off reflection when transmitting information bit "0".

[0101] For example, as shown at 708, a first device 702 (e.g., an RF source capable of transmitting RF waves, a first UE, or a network entity) can transmit a specific radio wave represented as x(n), which will be received by an RFID tag 704 (e.g., a passive IoT device, an RFID reader, etc.). As shown at 710, the information bits of the RFID tag 704 can be represented as s(n) ∈ {0,1}. Then, as shown at 712, the received signal y(n) at a second device (e.g., a second UE, an RFID reader, etc.) can be represented by y(n) = (h D1D2 (n)+σ f h D1T (n)h TD2 (n)s(n))x(n)+noise. Note that the first device 702 and the second device 706 can also be the same device (which can be referred to as a full-duplex device). In one example, when s(n) = 0, the RFID tag 704 can be configured to turn off reflection (e.g., the RFID tag 704 does not transmit any signal), such that the second device 706 can only receive the direct link signal from the first device 702 (e.g., y(n) = h D1D2 (n)x(n)+noise). However, when s(n) = 1, the RFID tag 704 can be configured to turn on reflection, such that the second device 706 can receive the superposition of both the direct link signal and the backscatter link signal (e.g., y(n) = (h D1D2 (n)+σ f h D1T (n)h TD2 (n)s(n))x(n)+noise, as shown at 712, where σ f can represent the reflection coefficient).

[0102] Figure 8AFIG. 800A is an illustration of an example where a network entity (e.g., a base station) according to various aspects of the present disclosure communicates directly with an RFID reader. In some examples, a network entity (such as a base station or a transmit receive point (TRP)) may be configured to directly (e.g., via DL) send an energy signal (e.g., data) to an RFID tag. Then, upon receiving the energy signal, the RFID tag may backscatter the energy signal and send the backscattered energy signal (e.g., backscattered data) to the network entity (e.g., via UL).

[0103] Figure 8B FIG. 800B is an illustration of an example where a network entity (e.g., a base station) according to various aspects of the present disclosure communicates (indirectly) with an RFID via a relay device. In some examples, a network entity (such as a base station or a TRP) may obtain information of an RFID tag via a relay device (e.g., a UE, an RFID reader, etc.). For example, the network entity may request the relay device to send an energy signal (e.g., data) to the RFID tag (e.g., via a forward link (FL)). Upon receiving the energy signal from the relay device, the RFID tag may backscatter the energy signal and send the backscattered energy signal (e.g., backscattered data) (e.g., via a backscatter link (BL)) to the relay device. Then, the relay device may relay / forward the received backscattered energy signal to the network entity.

[0104] Figure 8C FIG. 800C is an illustration of an example where a network entity (e.g., a base station) according to various aspects of the present disclosure communicates (indirectly) with an RFID via a relay device. In another example, a network entity (such as a base station or a TRP) may send an energy signal (e.g., data) to an RFID tag (e.g., via FL). Upon receiving the energy signal from the network entity, the RFID tag may backscatter the energy signal and send the backscattered energy signal (e.g., backscattered data) (e.g., via BL) to the relay device. Then, the relay device may relay / forward the received backscattered energy signal (e.g., via the Uu link) to the network entity.

[0105] Figure 9FIG. 900 is an illustration of an example of a network entity communicating with a set of IoT devices (e.g., receiving information from the set of IoT devices) in accordance with various aspects of the present disclosure. In some examples, the network entity may be a relay node, a RAN node, a non-RAN node, an IAB node, a base station, a component of a base station, etc. As wireless communication (e.g., 5G NR) continues to expand to support different types of wireless devices, such as enhanced mobile broadband (eMBB) devices, ultra-reliable low-latency communication (URLLC) devices, and / or machine type communication (MTC) devices, etc., wireless communication may also expand to support IoT devices such as passive IoT devices. Although in some scenarios (e.g., asset management, logistics, warehousing, and manufacturing, etc.), the network may not yet be able to efficiently support some popular RFID type sensors (e.g., passive IoT devices). A next-generation network may be specified to support or manage passive IoT devices, where the network entity (e.g., a base station, a component of a base station, an IAB node, etc.) may be configured / specified to provide energy to the passive IoT device and / or read / write information stored on the passive IoT device. For example, the passive IoT device may reflect / backscatter an information-bearing signal to the network entity, and the network entity may read the signal reflected / backscattered by the passive IoT device to decode the information sent by the passive IoT device. In another example, multiple network entities may send signals to an IoT device (e.g., IoT device 1) and receive the signals backscattered / reflected from the IoT device. Based on the round-trip time (RTT) or time of arrival (ToA) of the backscattered signal, each of the multiple network entities may calculate / estimate the distance / angle between the network entity and the IoT device. Thus, the location of the IoT device may be determined (e.g., based on a trilateration / triangulation mechanism).

[0106] As described in connection with Figure 4 , Figure 5 and Figure 9 , the location or relative location of an IoT device may be determined based on measuring the backscattered signal sent from the IoT device at one or more network entities (e.g., a base station, a UE, etc.). For example, the network entity (e.g., a base station, a component of a base station) may send a positioning reference signal (PRS) to the IoT device and measure the PRS backscattered / reflected from the IoT device. Similarly, the UE may send a PRS or a sidelink (SL) signal to the IoT device and measure the PRS / SL signal backscattered / reflected from the IoT device. Based on these measurements, the location of the IoT device may be determined.

[0107] In some scenarios, the arrival phase difference (PDOA) measurement may be suitable for the positioning of ZP-IoT devices. Under PDOA, the positioning of IoT devices can be estimated based on the phase difference between the transmitted signal and the backscattered signal. For example, an RFID reader can send signals of different frequencies to an RFID tag, and the RFID tag can backscatter these signals of different frequencies. Based on the backscattered signals, the RFID reader can compare the phase differences at those different frequencies, and the RFID reader can determine / estimate the distance between itself and the RFID tag based on this comparison.

[0108] Figure 10 FIG. 1000 is a diagram illustrating an example of estimating the distance between an RFID reader and an RFID tag based on frequency domain (FD)-PDOA according to various aspects of the present disclosure. As shown at 1006, an RFID reader 1002 can send RF signals of different frequencies (e.g., f1, f2, etc.) to an RFID tag 1004. Then, the RFID reader 1002 can measure the phases of the backscattered RF signals of different frequencies (e.g., phase angles in radians (rad)), and based on estimate the distance between the RFID reader 1002 and the RFID tag 1004, as shown at 1008 (e.g., showing the measured and recovered phase information of the received / backscattered signal).

[0109] In some examples, if the time period between consecutive signals sent from the RFID reader is too short, after the RFID reader sends another signal, the RFID reader may receive a backscattered signal from the RFID tag (e.g., after the RFID reader sends the first signal and the second signal, the RFID reader receives a signal backscattered based on the first signal). This may cause the RFID reader to be unable to determine whether the received backscattered signal is associated with the just-sent signal or the previously sent signal. This can be referred to as range ambiguity, where the RFID reader cannot distinguish the backscattered signals, and the RFID reader may obtain ambiguous (e.g., inaccurate or unreliable) range information. In some examples, when d > d max then, range ambiguity may occur, where Then, where k is unknown. For 30 kHz Δf, d max can be approximately 5000 meters (d max = 5000 m), and for 640 kHz Δf, d max can be approximately 240 meters (d max= 240 m), which may be sufficient to estimate the positioning / distance of the ZP-IoT device. Thus, for certain subcarrier spacings (SCSs) supported by a network (e.g., 5G-NR), the d associated with these SCSs max may be large enough and suitable for ZP-IoT positioning.

[0110] Aspects presented herein may enable a network entity to configure an RFID reader to estimate / determine the positioning or distance of an RFID tag based on PDOA positioning. For example, when an RFID reader (e.g., a UE) is configured to locate / determine the positioning of an RFID tag and the RFID reader is also capable of communicating with a network entity (e.g., a base station), the RFID reader may transmit a positioning request to the network entity. Based on the positioning request, the network entity may configure one or more parameters associated with PDOA positioning for the RFID reader, such as the frequency and / or time resources, bandwidth, and / or number of repetitions for PDOA positioning.

[0111] Figure 11 FIG. 1100 is a diagram illustrating an example of a network entity configuring a set of resources associated with PDOA positioning for an RFID reader in accordance with various aspects of the present disclosure. In one example, as shown at 1120, an RFID reader 1104 (e.g., a UE) may be configured / triggered to determine the positioning of an RFID tag 1106 (or the distance between the RFID reader 1104 and the RFID tag 1106) based on PDOA positioning, such as phase difference of arrival (PDOA) in the frequency domain (FD-PDOA) positioning.

[0112] Then, as shown at 1122, the RFID reader 1104 may send a reader positioning request 1108 to a network entity 1102 (e.g., a base station) to notify the network entity 1102 about performing PDOA positioning of the RFID tag 1106. In response, as shown at 1124, the network entity 1102 may send a network positioning response 1110 to the RFID reader 1104, where the network positioning response 1110 may include one or more parameters / configurations associated with PDOA positioning.

[0113] In one aspect of the present disclosure, the network positioning response 1110 may include resources in which the RFID reader 1104 may be used to send a signal to the RFID tag 1106, such as in combination with Figure 5 and Figure 7as described (e.g., the energy / data signal for backscattering of the RFID tag 1106). In one example, as shown at 1126, the resources can include a set of time-domain and frequency-domain resources that do not overlap in both the time domain (TD) and the frequency domain. In another example, as shown at 1128, the resources can include a set of time-domain and frequency-domain resources that do not overlap only in the frequency domain. Then, based on the configuration / resources granted in the network location response 1110, the RFID reader 1104 can use these configuration / resources to perform PDOA positioning / distance estimation of the RFID tag 1106.

[0114] Since the RFID reader 1104 is designated to compare different phases of the backscattered signals from the RFID tag 1106 under PDOA positioning, the signals transmitted from the RFID reader 1104 (or the signals backscattered by the RFID tag 1106) may not overlap in the frequency domain. In some cases, the signals transmitted from the RFID reader 1104 can also be configured to not overlap in the time domain. For example, some RFID readers may be able to transmit only one resource block (e.g., one energy signal) at a time (e.g., due to power limitations). Thus, the resources configured for these RFID readers may not overlap in the time domain.

[0115] However, in some examples, it may be beneficial to configure the RFID reader to transmit one resource block at a time (or resources that do not overlap in the time domain), because this can extend the transmission range / detection distance of the RFID reader. For example, if the RFID reader 1104 is configured to transmit one resource block at a time, the RFID reader 1104 can use all available transmission power to transmit that one resource block, which can result in a longer transmission distance / detection range. On the other hand, if the RFID reader 1104 is configured to transmit three resource blocks at a time, as shown at 1128, the RFID reader 1104 can be designated to allocate the available transmission power among these three resource blocks, which can result in a shorter transmission distance / detection range compared to transmitting one resource block at a time.

[0116] Figure 12FIG. 1200 is a diagram illustrating an example phase value distribution associated with FD-PDOA positioning of an RFID tag in accordance with various aspects of the present disclosure. In one example, an RFID tag (e.g., RFID tag 1106) may be set to move from a first position to a second position and away from an RFID reader (e.g., RFID reader 1104) in X steps. At each step, the RFID reader may use / transmit multiple transmit carrier frequencies (e.g., between frequencies 913 MHz and 920 MHz) to collect phase information from the RFID tag (e.g., record approximately 200 RFID tag phase values corresponding to each frequency). The curve at 1202 shows an example phase distribution when the carrier frequency varies from 913 MHz to 920 MHz at a point between the first and second positions. It can be observed that the phase values may change linearly with the carrier frequency.

[0117] Based on the diagram shown at 1202, it can be observed that the bandwidth used for positioning / localization of an RFID tag may affect the positioning accuracy of the RFID tag. For example, if a frequency interval of 1 MHz is used, performing PDOA positioning using a total bandwidth of 20 MHz (e.g., using a frequency range of 910 MHz to 930 MHz) may achieve higher accuracy than using a total bandwidth of 5 MHz (e.g., using a frequency range of 910 MHz to 915 MHz). Thus, in another aspect of the present disclosure, to improve or ensure positioning accuracy, a bandwidth (BW) threshold or a BW precision accuracy mapping may be defined / preconfigured at a network entity (and / or at the RFID reader). For example, as shown at 1204, when the positioning accuracy (or positioning precision) of the RFID tag is specified to be within one (1) meter, the RFID reader may be configured / specified to use at least five (5) MHz of bandwidth for positioning, while when the precision is specified to be between one (1) meter and ten (10) meters, the RFID reader may be configured / specified to use at least one (1) MHz of bandwidth for positioning.

[0118] Based on such a mapping, if the RFID reader reports / requests the positioning precision of an RFID tag positioning (e.g., using PDOA-based positioning, received signal strength indicator (RSSI)-based positioning, etc.) to a network entity (e.g., a base station), the network entity may determine how much BW to allocate to the RFID reader, which may be indicated to the RFID reader via a network positioning response. If the network entity is performing the positioning of the RFID tag, the network entity may also use such a mapping to determine the bandwidth for positioning. For example, returning to the reference Figure 11, if the RFID reader 1104 is to determine the positioning / distance of the RFID tag 1106 within an accuracy of less than one meter, the RFID reader 1104 may indicate its accuracy specification to the network entity 1102, such as via a reader positioning request 1108. In response (and based on the mapping / reconfiguration shown at 1204), the network entity 1102 may configure resources with a bandwidth of at least 5 MHz for the RFID reader 1104 and / or indicate that the RFID reader 1104 use a bandwidth of at least 5 MHz to perform the positioning of the RFID tag 1106, where the configuration / indication may be sent to the RFID reader 1104 via a network positioning response 1110. On the other hand, if the RFID reader 1104 is to determine the positioning / distance of the RFID tag 1106 within an accuracy between one meter and ten meters, the network entity 1102 may configure resources with a bandwidth of 2 MHz or 4 MHz for the RFID reader 1104 and / or indicate that the RFID reader 1104 use a bandwidth of 2 MHz or 4 MHz to perform the positioning of the RFID tag 1106, where the configuration / indication may be sent to the RFID reader 1104 via a network positioning response 1110.

[0119] Return reference Figure 12 , based on the illustration shown at 1202, it can also be observed that the number of repeated positionings for the positioning (positioning / localization) of the RFID tag may affect the positioning (positioning / localization) accuracy of the RFID tag. For example, if ten (10) specified positioning procedures are performed between the RFID reader and the RFID tag, the positioning (positioning / localization) accuracy of the RFID tag may be higher compared to performing only one positioning procedure. Thus, in another aspect of the present disclosure, to improve or ensure positioning accuracy, a repetition count threshold or a repetition count and accuracy accuracy mapping may be defined / preconfigured at the network entity (and / or at the RFID reader). For example, as shown at 1206, when the positioning accuracy (or positioning accuracy) of the RFID tag is specified to be within one (1) meter, the RFID reader may be configured to repeat the positioning at least ten (10) times, while when the accuracy is specified to be between one (1) meter and ten (10) meters, the RFID reader may be configured to perform the positioning once.

[0120] Based on such a mapping, if an RFID reader reports / requests the positioning accuracy (e.g., PDOA-based positioning, RSSI-based positioning, etc.) to a network entity (e.g., a base station), the network entity can determine how many repetition times are to be configured for the RFID reader, which can be indicated to the RFID reader via a network positioning response or configured for the RFID reader. If the network entity is performing the positioning of the RFID tag, the network entity can also use such a mapping to determine the number of repetition times for positioning. For example, referring back to Figure 11 , if the RFID reader 1104 wants to determine the positioning / distance of the RFID tag 1106 within an accuracy of less than one meter, the RFID reader 1104 can indicate its accuracy specification to the network entity 1102, such as via a reader positioning request 1108. In response (and based on the mapping / reconfiguration shown at 1206), the network entity 1102 can configure or instruct the RFID reader 1104 (e.g., via a network positioning response 1110) to perform the positioning (e.g., PDOA-based positioning, RSSI-based positioning, etc.) at least ten (10) times. On the other hand, if the RFID reader 1104 wants to determine the positioning / distance of the RFID tag 1106 within an accuracy between one meter and ten meters, the network entity 1102 can configure or instruct the RFID reader 1104 to perform the positioning only once, at least once, or no more than 10 times, etc.

[0121] As described in connection with Figure 12 , such an accuracy / bandwidth / repetition - times mapping (or table) can be defined / pre - configured at the network entity (e.g., a base station) and / or at the RFID reader (e.g., a UE). In one example, if such a mapping / table is configured at the network entity and the network entity is responsible for performing the positioning of the RFID tag, the network entity can determine the bandwidth for positioning and / or the number of times the positioning is to be repeated based on the mapping / table. However, if the RFID reader is responsible for performing the positioning, the network entity can configure the appropriate bandwidth and / or repetition times for the RFID reader based on the mapping / table.

[0122] On the other hand, if such a mapping / table is configured at the RFID reader, the RFID reader can determine the amount of bandwidth to request from the network entity (e.g., in the reader location request 1108) and / or the number of times to send the reader location request to the network entity. For example, the network entity 1102 can be configured to provide resources to the RFID reader 1104 to perform a location only once for each reader location request 1108 received from the RFID reader 1104. Thus, for the RFID reader 1104 to perform the location ten (10) times (e.g., to achieve an accuracy within one meter), the RFID reader 1104 can be specified to send ten reader location requests to the network entity 1102 and receive ten resource allocations / configurations (e.g., via ten network location responses) from the network entity 1102.

[0123] Figure 13 FIG. 1300 is a diagram illustrating examples of coherent bandwidth and coherent time in accordance with various aspects of the present disclosure. For FD-PDOA based positioning, another configuration factor to consider can be the coherent channel BW and coherent time, where the resources used for positioning (e.g., resources configured for the RFID reader) may not exceed the coherent channel BW and coherent time. As shown at 1302, the coherent channel BW can refer to a statistical measure of the frequency range over which the channel can be considered flat, or in other words, the approximate maximum bandwidth or frequency separation over which two frequencies of a signal may experience comparable or correlated amplitude fading. On the other hand, the coherent time can refer to the time duration over which the channel impulse response is considered not to change. Such channel variations may be more significant in wireless communication systems due to the Doppler effect.

[0124] Thus, in another aspect of the present disclosure, a network entity (e.g., network entity 1102, base station, etc.) can determine the bandwidth and time span of time and frequency resources for FD-PDOA positioning of an RFID reader (e.g., RFID reader 1104, UE, etc.) based on the moving speed (or Doppler) of the RFID reader (e.g., if the RFID reader is not stationary). For example, the resources configured for the RFID reader (e.g., via a network positioning response from the network entity) can be specified to be within the coherent channel BW and coherent time. Similarly, as shown at 1304, a mapping / table can be defined / pre-configured at the network entity and / or the RFID reader. For example, when the RFID reader moves at a speed greater than one meter per second (1 m / s) but less than three meters per second (3 m / s), the network entity can configure a set of time and frequency resources (e.g., via a network positioning response) with a bandwidth not exceeding 10 MHz and a time span not exceeding 250 milliseconds (ms). On the other hand, if the RFID reader moves at a speed greater than three meters per second (3 m / s), the network entity can configure a set of time and frequency resources (e.g., via a network positioning response) with a bandwidth not exceeding 3 MHz and a time span not exceeding 50 milliseconds (ms), etc.

[0125] When the RFID reader (e.g., UE) is configured / triggered to determine the distance between the RFID reader and the RFID tag (e.g., 100 meters away) or the positioning of the RFID tag (e.g., x, y, z positions, longitude coordinates, latitude coordinates, etc.), the RFID reader can request a network entity (e.g., base station, location server, LMF, etc.) to perform positioning (which can be referred to as UE-assisted positioning in some examples) or the RFID reader can perform positioning by itself (which can be referred to as UE-based positioning in some examples). If the network entity knows whether the RFID reader is going to determine the distance or positioning of the RFID tag and / or whether the RFID reader is going to perform positioning by itself (e.g., based on a reader positioning request received from the RFID reader), the network entity can provide a corresponding response / configuration to the RFID reader, such as via a network positioning response.

[0126] For example, returning to the reference Figure 11, the RFID reader 1104 may provide PDOA measurements for the RFID tag 1106 to the network entity 1102 and request the network entity 1102 to determine the location / distance of the RFID tag 1106 (e.g., via the reader location request 1108). In response, the network entity may calculate / estimate the location / distance of the RFID tag 1106 based on the PDOA measurements from the RFID reader (and also from other RFID readers if the location of the RFID tag 1106 involves multiple RFID readers), and the network entity may feedback the determined / estimated location / distance of the RFID tag 1106 to the RFID reader 1104 (e.g., via the reader location response 1110). Then, the location request from the RFID reader 1104 may be terminated. However, in some cases, if the RFID reader is configured to determine the location / distance of the RFID tag 1106 itself, additional signaling and configuration may be specified between the network entity 1102 and the RFID reader 1104. For example, as described in conjunction with Figure 11 , if the RFID reader 1104 is configured to determine the location of the RFID tag 1106, the RFID reader may request a set of time and frequency resources for performing the location (e.g., via the reader location request 1108). In response, the network entity 1102 may allocate a set of time and frequency resources for the RFID reader 1104 to perform the location (e.g., via the network location response 1110). In another example, as described in conjunction with Figure 12 , if the RFID reader 1104 is specified to determine the location of the RFID tag 1106 with a specific accuracy, the RFID reader 1104 may be configured to perform the location repeatedly multiple times, where the network entity 1102 may provide the target number of repetitions to the RFID reader 1104 (e.g., via the network location response 1110).

[0127] In some scenarios, different location accuracies may specify different location methods, and different location methods may specify different resources. For example, a location method based on received signal strength (RSS) or received signal strength indicator (RSSI) may specify a one-time resource in the time domain, while a location method based on FD-PDOA may specify certain bandwidth resources for the location, such as described in conjunction with Figure 11 .

[0128] Aspects presented herein can improve the positioning efficiency and accuracy of RFID tags performed by an RFID reader. In one aspect, the RFID reader can indicate to a network entity, such as via a reader positioning request, at least one positioning method (e.g., RSSI-based positioning, PDOA-based positioning, TDOA-based positioning, etc.) that it is configured to use. In response, the network entity can provide a suitable configuration (such as resource allocation) for the RFID reader based on the indicated positioning method (e.g., via a network positioning response). In another aspect, since different positioning methods can specify different positioning accuracies, the RFID reader can also report / indicate its positioning accuracy requirements to the network entity instead of explicitly indicating different positioning methods to the network entity (e.g., via a reader positioning request). In response, the network entity can provide a suitable configuration for the RFID reader based on the positioning accuracy requirements (e.g., via a network positioning response). In some examples, in addition to the RFID reader determining the positioning method, the network entity can also be configured to determine at least one positioning method for the RFID reader, such as via L1 / L2 / L3 signaling or a network positioning response.

[0129] In one aspect of the present disclosure, when an RFID reader (e.g., RFID reader 1104) is configured to only determine the distance between the RFID reader and an RFID tag (e.g., RFID tag 1106), the RFID reader can send only one reader positioning request to a network entity (e.g., network entity 1102) and receive one network positioning response from the network entity, the one network positioning response including one or more configurations (e.g., resource allocation, positioning parameters, etc.) associated with the determination of the distance. On the other hand, if the RFID reader is configured to determine the location of the RFID tag (e.g., its x, y, z location, longitude coordinates, and latitude coordinates, etc.), the RFID reader can be configured to send multiple reader positioning requests to the network entity, where the reader positioning requests may not overlap in the time domain. Thus, an association or relationship can be defined / configured between the reader positioning requests and the network positioning responses. For example, the set of reader positioning requests and the set of network positioning responses can be associated with each other based on timing (or a timing window), based on an identifier (ID) associated with the RFID tag, based on an ID associated with the reader positioning request (which may be referred to hereinafter as a "request ID"), and / or based on an ID associated with the network positioning response (which may be referred to hereinafter as a "response ID"), etc. Such an association can improve RFID tag positioning, such as when the RFID reader is configured to position a multi-pole RFID tag.

[0130] Figure 14FIG. 1400 is a diagram illustrating an example of an RFID reader determining the location of an RFID tag in accordance with various aspects of the present disclosure. In one example, as shown at 1402, the RFID reader 1104 may be configured to determine the location of the RFID tag 1106 (e.g., its x, y, z locations, longitude coordinates, latitude coordinates, etc.) based on measuring the distance between the RFID reader 1104 and the RFID tag 1106 at multiple positions (e.g., similar to performing trilateration via multiple RFID readers). Accordingly, the RFID reader 1104 may be designated to send multiple reader location requests to the network entity 1102.

[0131] For example, at 1404, the RFID reader 1104 may send a first reader location request to the network entity 1102, where the first reader location request may indicate that the RFID reader 1104 is to determine the distance between the RFID reader 1104 and the RFID tag 1106. In some examples, the reader location request may include one or more positioning methods that the RFID reader 1104 is capable of performing, such as ToA-based positioning, TDOA-based positioning, RSS-based positioning, PDOA-based positioning, and / or AoA-based positioning, etc. In response, at 1406, the network entity 1102 may provide a suitable configuration for the RFID reader 1104 to perform the specified positioning (e.g., distance estimation) via a first network location response, such as the specified positioning method, time-frequency resources for transmitting signals, password keys for communicating with the RFID tag 1106 (if the RFID tag 1106 is password protected / encrypted), and / or waveforms to be used, etc. Then, as shown at 1408, based on the configuration / first network location response, the RFID reader 1104 may perform a first distance estimation between the RFID reader 1104 and the RFID tag 1106 at a first time point (T1) or at a first position (position 1).

[0132] Thereafter, at 1410, the RFID reader 1104 may send a second reader location request to the network entity 1102, where the second reader location request may also indicate that the RFID reader 1104 is to determine the distance between the RFID reader 1104 and the RFID tag 1106 based on a specified location method. In response, at 1406, the network entity 1102 may provide appropriate configuration for the RFID reader 1104 via a second network location response to perform the specified location. Similarly, as shown at 1414, based on the configuration / second network location response, the RFID reader 1104 may perform a second distance estimation between the RFID reader 1104 and the RFID tag 1106 at a second time point (T2) or at a second location (Location 2). The RFID reader 1104 may continue and repeat this process until it has sufficient location measurements to determine the location of the RFID tag 1106 (e.g., until the Nth location).

[0133] In some cases, the periodicity of the RFID reader 1104 requesting location configuration from the network entity 1102 (or the periodicity of the reader sending the reader location request) may also affect location accuracy and / or resource utilization efficiency, such as when the RFID reader 1104 is moving at different speeds.

[0134] Figure 15A FIG. 1500A is a diagram illustrating an example of a fast-moving RFID reader in accordance with various aspects of the present disclosure. When the RFID reader 1104 is moving fast (e.g., 10 m / s) but the periodicity of the reader sending the reader location request is low (e.g., one reader location request every 10 seconds), the RFID reader 1104 may quickly move out of the detectable (e.g., transmit / receive (Tx / Rx)) range of the RFID tag. For example, after the RFID reader 1104 measures the distance between the RFID reader 1104 and the RFID tag 1106 at a first location (Location 1), the RFID reader 1104 at a second location (Location 2) may be 100 meters away from the first location (and may be outside the Tx / Rx range of the RFID tag 1106).

[0135] Figure 15BFIG. 1500B is an illustration example of a slow moving RFID reader according to various aspects of the present disclosure. In contrast, when the RFID reader 1104 moves slowly (e.g., 0.1 m / s) but the reader sends reader location requests periodically at a high rate (e.g., one reader location request every 0.1 seconds), the RFID reader 1104 may repeatedly detect the same results. For example, after the RFID reader 1104 measures the distance between the RFID reader 1104 and the RFID tag 1106 at a first location (Location 1), the RFID reader 1104 at a second location (Location 2) may be only 0.01 meters away from the first location. Thus, the distances measured by the RFID reader 1104 at the first and second locations may be the same, which may not be useful for the location of the RFID tag 1106 and may result in wasted additional power and resources.

[0136] In another aspect of the present disclosure, the mapping / table may be defined / preconfigured at a network entity (and / or at the RFID reader). If the mapping / table is defined / preconfigured at the network entity, the network entity may dynamically indicate / configure the mapping for the RFID reader (e.g., via L1 / L2 / L3 signaling, network location response 1110, etc.) based on information in the reader location request (e.g., reader location request 1108).

[0137] As Figure 16As shown in the illustration 1600, a mapping / association between the RFID reader speed and the request period can be defined / pre-configured at the network entity 1102. For example, as shown at 1602, the mapping / association can indicate that when the RFID reader moves between 0.1 meters per second (m / s) and 1 m / s, the RFID reader can send the reader location request 1108 periodically with a period greater than 10 seconds (e.g., the RFID reader is configured to send two consecutive reader location requests with an interval of at least 10 seconds). On the other hand, when the RFID reader moves between 1 m / s and 10 m / s, the RFID reader can send the reader location request 1108 periodically with a period greater than 1 second (e.g., the RFID reader can send two consecutive reader location requests with an interval of at least 1 second). Thus, when the network entity 1102 can determine the speed of the RFID reader 1104, such as based on its own detection or via a report from the RFID reader (e.g., via the reader location request 1108), the network entity 1102 can dynamically indicate the period for sending the reader location request to the RFID reader 1104. In another example, as shown at 1604, an RFID reader speed threshold (X m / s) can also be defined / pre-configured at the network entity 1102 and / or at the RFID reader 1104. If the speed of the RFID reader 1104 exceeds this speed threshold, the RFID reader can be prohibited from performing location or distance estimation.

[0138] In another example, a mapping / association between the distance change of the RFID reader and whether the RFID reader can continue to perform the location or distance estimation of the RFID tag can be defined / pre-configured at the network entity 1102 and / or at the RFID reader 1104. For example, as shown at 1606, the mapping / association can indicate that when the change in the distance of the RFID reader exceeds 10 meters (e.g., between two consecutive reader location requests, within a specified time duration, etc.), the RFID reader can send (or continue to send) another reader location request. On the other hand, when the change in the distance of the RFID reader does not exceed 10 meters (e.g., the change is between 0 meters and 10 meters), the RFID reader can be avoided from sending another reader location request. Thus, when the network entity 1102 can determine the distance change of the RFID reader 1104, such as based on its own detection or via a report from the RFID reader (e.g., via the reader location request 1108), the network entity 1102 can dynamically indicate to the RFID reader 1104 whether the RFID reader 1104 can send another reader location request. In other words, when the location change of the RFID reader 1104 is greater than the distance threshold, a new reader location request to the network entity 1102 can be triggered at the RFID reader 1104.

[0139] As combined withFigure 16 As described, although an RFID reader (e.g., RFID reader 1104) may be configured to determine whether it can transmit a reader location request and / or the periodicity for transmitting a reader location request (e.g., if a mapping / table is defined / pre-configured at the RFID reader), a network entity (e.g., network entity 1102) may also make such a determination for the RFID reader based on information provided by the RFID reader (e.g., via RFID reader reports, reader location requests, etc.). For example, as Figure 16 shown, RFID reader 1104 may include or report its speed (or Doppler) and / or its location change to network entity 1102, such as via reader location request 1108. In response, based on the mapping / table shown at 1602 and 1606, network entity 1102 may determine whether to respond to reader location request 1108 (e.g., RFID reader 1104 may be configured not to perform location / distance estimation without a network location response), or network entity 1102 may determine the periodicity of resources (granted to RFID reader 1104), such as via network location response 1110, etc.

[0140] Table 2 below shows examples of information that may be included in a reader location request and a network location response based on aspects presented herein.

[0141]

[0142] Table 2: Example Information Provided in Reader Location Request and Network Location Response

[0143] Figure 17 is a flowchart 1700 of a wireless communication method. In some scenarios, the method may be performed by a wireless device (e.g., UE 104, 404; RFID reader 504, 1002, 1104; device 1804). In one aspect, the method may enable a wireless device (e.g., RFID reader, UE, etc.) to estimate / determine the location or distance of an RFID tag based on phase difference of arrival (PDOA) positioning. In another aspect, the method may enable a wireless device to communicate with a network entity to receive a configuration associated with the location of an RFID tag.

[0144] At 1702, the wireless device may send a set of requests to the network entity for estimating the range between the wireless device and an IoT device or for estimating the location of the IoT device, such as in conjunction with Figure 11 , Figure 14 and Figure 16 described. For example, as Figure 14As shown at 1404 and 1410, the RFID reader 1104 may send a set of reader location requests to the network entity 1102 for estimating the distance between the RFID reader 1104 and the RFID tag 1106 and determining the location of the RFID tag 1106. The sending of the set of requests may be performed by, for example Figure 18 the IoT device location component 198, the cellular baseband processor 1824, and / or the transceiver 1822 of the device 1804 in

[0145] At 1704, a wireless device may send or receive an indication of a location method for estimating the range between the wireless device and an IoT device or for estimating the location of the IoT device, where the indication is sent to or received from a network entity, such as in connection with Figure 11 , Figure 14 and Figure 16 as described. For example, at 1404 or 1406 of Figure 14 , the RFID reader 1104 may send or receive an indication of a location method for estimating the range between the RFID reader 1104 and the RFID tag 1106 or for estimating the location of the RFID tag 1106 from the network entity 1102. The sending or receiving of the indication may be performed by, for example Figure 18 the IoT device location component 198, the cellular baseband processor 1824, and / or the transceiver 1822 of the device 1804 in

[0146] At 1706, the wireless device may receive at least one response from the network entity, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated location method, such as in connection with Figure 11 , Figure 14 and Figure 16 as described. For example, as shown at 1406 and 1412 of Figure 14 , the RFID reader 1104 may receive a set of network location responses from the network entity 1102, where the set of network location responses may include a configuration of a set of resources for estimating the range between the RFID reader 1104 and the RFID tag 1106 or for estimating the location of the RFID tag 1106. The sending of the at least one response may be performed by, for example Figure 18 the IoT device location component 198, the cellular baseband processor 1824, and / or the transceiver 1822 of the device 1804 in

[0147] In one example, the wireless device may use the indicated location method via the set of resources to estimate the range between the wireless device and the IoT device or to estimate the location of the IoT device.

[0148] In another example, the wireless device may send to the network entity the precision specified for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, and the wireless device may receive from the network entity an indication indicating a positioning method based on the specified precision.

[0149] In another example, a set of requests may correspond to one request for estimating the range between the wireless device and the IoT device, and the set of requests may correspond to more than one request for estimating the location of the IoT device, and the set of requests does not overlap in the time domain.

[0150] In another example, each request in the set of requests may be associated with at least one response based on a timing window, an ID associated with the IoT device, a request ID associated with each request in the set of requests, a response ID associated with at least one response, or a combination thereof.

[0151] In another example, the number of requests in the set of requests or the periodicity between the requests in the set of requests may be based on the moving speed of the wireless device. In such examples, the wireless device may determine the periodicity based on the moving speed of the wireless device, or the wireless device may receive the periodicity from the network entity based on the moving speed of the wireless device. In such examples, in the case where the moving speed of the wireless device exceeds a speed threshold, the wireless device may avoid estimating the range between the wireless device and the IoT device or estimating the location of the IoT device to the network entity.

[0152] In another example, in the case where the location of the wireless device has changed its location by more than a distance threshold, the wireless device may send to the network entity a second set of requests for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device.

[0153] In another example, the wireless device may send to the network entity a second indication of the moving speed or location change of the wireless device, where the configuration of the resource set may include a periodicity associated with the resource set, and the periodicity is based on the moving speed or location change.

[0154] In another example, the positioning method may include: positioning based on ToA, positioning based on TDOA, positioning based on RSS, positioning based on PDOA, or positioning based on AoA.

[0155] In another example, the positioning method may correspond to FD-PDOA positioning, and the resource sets may not overlap in the FD. In such examples, the wireless device may use the resource sets to estimate the range between the wireless device and the IoT device based on FD-PDOA positioning. In one example, to estimate the range between the wireless device and the IoT device based on FD-PDOA positioning, the wireless device may send a first set of signals to the IoT device, receive a second set of signals backscattered from the IoT device, and measure the PDOA of the second set of signals. In another example, the wireless device may estimate the positioning of the IoT device based on the estimated range, or send the estimated range to a network entity to assist the network entity in estimating the positioning of the IoT device. In another example, the resource sets may also not overlap in the time domain (TD). In another example, the configuration may further include the bandwidth or minimum bandwidth for the resource sets, and wherein the bandwidth or the minimum bandwidth may be based on the accuracy specified for estimating the range between the wireless device and the IoT device. In another example, the configuration may further include the number or minimum number of times the wireless device is to perform PDOA positioning, and the number or the minimum number may be based on the accuracy specified for estimating the range between the wireless device and the IoT device. In another example, the configuration may further include the minimum bandwidth and minimum time span for the resource sets, and the minimum bandwidth and the minimum time span may be based on the moving speed of the wireless device to maintain the coherent bandwidth and coherent time for PDOA positioning.

[0156] Figure 18FIG. 1800 is a diagram illustrating an example of a hardware implementation for apparatus 1804. Apparatus 1804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1804 may include a cellular baseband processor 1824 (also referred to as a modem) coupled to one or more transceivers 1822 (e.g., cellular RF transceivers). The cellular baseband processor 1824 may include on-chip memory 1824'. In some aspects, apparatus 1804 may further include one or more subscriber identity module (SIM) cards 1820 and an application processor 1806 coupled to a secure digital (SD) card 1808 and a screen 1810. The application processor 1806 may include on-chip memory 1806'. In some aspects, apparatus 1804 may further include a Bluetooth module 1812, a WLAN module 1814, an SPS module 1816 (e.g., GNSS module), one or more sensor modules 1818 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio aided detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), additional memory modules 1826, a power source 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include their own dedicated antennas and / or communicate using antenna 1880. The cellular baseband processor 1824 communicates with UE 104 and / or with an RU associated with network entity 1802 via transceiver 1822 through one or more antennas 1880. The cellular baseband processor 1824 and the application processor 1806 may each separately include computer-readable media / memory 1824', 1806'. The additional memory module 1826 may also be considered computer-readable media / memory. Each computer-readable media / memory 1824', 1806', 1826 may be non-transitory. The cellular baseband processor 1824 and the application processor 1806 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1824 / application processor 1806, causes the cellular baseband processor 1824 / application processor 1806 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1824 / application processor 1806 when executing the software.The cellular baseband processor 1824 / application processor 1806 can be components of the UE 350 and can include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1804 can be a processor chip (modem and / or application) and include only the cellular baseband processor 1824 and / or the application processor 1806, and in another configuration, the device 1804 can be the entire UE (e.g., see. Figure 3 of 350) and include additional modules of the device 1804.

[0157] As discussed above, the IoT device positioning component 198 is configured to send a set of requests to a network entity for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device. The IoT device positioning component 198 can also be configured to send or receive an indication indicating a positioning method for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device, where the indication is sent to or received from the network entity. The IoT device positioning component 198 can also be configured to receive at least one response from the network entity, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device based on the set of requests and the indicated positioning method. The IoT device positioning component 198 can be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The IoT device positioning component 198 can be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. As shown, the device 1804 can include a variety of components configured for various functions. In one configuration, the device 1804 (specifically, the cellular baseband processor 1824 and / or the application processor 1806) includes components for sending a set of requests to a network entity for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device. The device 1804 can also include components for sending or receiving an indication indicating a positioning method for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device, where the indication is sent to or received from the network entity. The device 1804 can also include components for receiving at least one response from the network entity, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device based on the set of requests and the indicated positioning method.

[0158] In one example, the apparatus 1804 may further include components for estimating the range between the wireless device and the IoT device or estimating the location of the IoT device using the indicated location method via a resource set.

[0159] In another example, the apparatus 1804 may further include components for sending to a network entity the accuracy specified for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, and components for receiving from the network entity an indication of the location method based on the specified accuracy.

[0160] In another example, the request set may correspond to one request for estimating the range between the wireless device and the IoT device, and the request set may correspond to more than one request for estimating the location of the IoT device, and the request set does not overlap in the time domain.

[0161] In another example, each request in the request set may be associated with at least one response based on a timing window, an ID associated with the IoT device, a request ID associated with each request in the request set, a response ID associated with at least one response, or a combination thereof.

[0162] In another example, the number of requests in the request set or the periodicity between requests in the request set may be based on the moving speed of the wireless device. In such examples, the apparatus 1804 may further include components for determining the periodicity based on the moving speed of the wireless device, or components for receiving the periodicity from the network entity based on the moving speed of the wireless device. In such examples, the apparatus 1804 may further include components for avoiding estimating the range between the wireless device and the IoT device or estimating the location of the IoT device from the network entity when the moving speed of the wireless device exceeds a speed threshold.

[0163] In another example, the apparatus 1804 may further include components for sending to the network entity a second request set for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device when the location of the wireless device has changed its location by more than a distance threshold.

[0164] In another example, the apparatus 1804 may further include components for sending to the network entity a second indication of the moving speed or location change of the wireless device, wherein the configuration of the resource set may include a periodicity associated with the resource set, and the periodicity is based on the moving speed or location change.

[0165] In another example, the location method may include: ToA-based location, TDOA-based location, RSS-based location, PDOA-based location, or AoA-based location.

[0166] In another example, the positioning method may correspond to FD-PDOA positioning, and the resource sets may not overlap in the FD. In such examples, apparatus 1804 may also include components for estimating the range between a wireless device and an IoT device based on FD-PDOA positioning using the resource sets.

[0167] In one example, to estimate the range between a wireless device and an IoT device based on FD-PDOA positioning, apparatus 1804 is configured to send a first set of signals to the IoT device, receive a second set of signals backscattered from the IoT device, and measure the PDOA of the second set of signals.

[0168] In another example, apparatus 1804 may also include components for estimating the location of the IoT device based on the estimated range, or for sending the estimated range to a network entity to assist the network entity in estimating the location of the IoT device.

[0169] In another example, the resource sets may also not overlap in the time domain.

[0170] In another example, the configuration may also include a bandwidth or a minimum bandwidth for the resource sets, and wherein the bandwidth or the minimum bandwidth may be based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0171] In another example, the configuration may also include the number of times or the minimum number of times the wireless device is to perform PDOA positioning, and the number or the minimum number may be based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0172] In another example, the configuration may also include a minimum bandwidth and a minimum time span for the resource sets, and the minimum bandwidth and the minimum time span may be based on the moving speed of the wireless device to maintain the coherent bandwidth and coherent time for PDOA positioning.

[0173] The components may be the IoT device positioning component 198 of apparatus 1804 configured to perform the functions recited by the components. As described above, apparatus 1804 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0174] Figure 19Flowchart 1900 of a wireless communication method. In some scenarios, this method may be performed by a network entity (e.g., base station 102; network entities 1102, 2002). In one aspect, this method enables the network entity to configure a wireless device (e.g., RFID reader, UE, etc.) to estimate / determine the location or distance of an RFID tag based on the phase difference of arrival (PDOA) positioning. In another aspect, this method enables the network entity to communicate with the wireless device and configure the wireless device with parameter configurations associated with the location of the RFID tag.

[0175] At 1902, the network entity may receive from the wireless device a set of requests for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, such as those described in conjunction with Figure 11 , Figure 14 and Figure 16 . For example, as shown at 1404 and 1410 of Figure 14 , the network entity 1102 may receive from the RFID reader 1104 a set of reader location requests for estimating the distance between the RFID reader 1104 and the RFID tag 1106 and determining the location of the RFID tag 1106. The reception of the set of requests may be performed by, for example, the IoT device location configuration component 199, the RU processor 2042, and / or the transceiver 2046 of the network entity 2002 in Figure 20 .

[0176] At 1904, the network entity may send or receive an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, where the indication is sent to or received from the wireless device, such as those described in conjunction with Figure 11 , Figure 14 and Figure 16 . For example, at 1404 or 1406 of Figure 14 , the network entity 1102 may send or receive from the RFID reader 1104 an indication of a positioning method for estimating the range between the RFID reader 1104 and the RFID tag 1106 or for estimating the location of the RFID tag 1106. The sending or receiving of the indication may be performed by, for example, the IoT device location configuration component 199, the RU processor 2042, and / or the transceiver 2046 of the network entity 2002 in Figure 20 .

[0177] At 1906, the network entity may send to the wireless device at least one response that includes a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method, such as those described in conjunction with Figure 11 ,Figure 14 and Figure 16 as described. For example, as shown at 1406 and 1412 of Figure 14 , network entity 1102 may send a set of network location responses to RFID reader 1104, where the set of network location responses may include a configuration for a set of resources for estimating the range between RFID reader 1104 and RFID tag 1106 or for estimating the location of RFID tag 1106. The sending of at least one response may be performed by, for example, Figure 20 the IoT device location configuration component 199, RU processor 2042, and / or transceiver 2046 of network entity 2002 in

[0178] In one example, a network entity may receive from a wireless device a specified accuracy for estimating the range between the wireless device and an IoT device or for estimating the location of the IoT device, and the network entity may send an indication of a location method to the wireless device based on the specified accuracy.

[0179] In another example, each request in a set of requests may be associated with at least one response based on a timing window, an ID associated with the IoT device, a request ID associated with each request in the set of requests, a response ID associated with at least one response, or a combination thereof.

[0180] In another example, the number of requests in a set of requests or the periodicity between requests in the set of requests may be based on the moving speed of the wireless device. In such examples, the network entity may determine the periodicity based on the moving speed of the wireless device, and the network entity may send the determined periodicity to the wireless device.

[0181] In another example, a network entity may receive from a wireless device a second indication of the moving speed of the wireless device or a change in location, where the configuration for the set of resources may include a periodicity associated with the set of resources that is based on the moving speed or change in location.

[0182] In another example, the location method may include: ToA-based location, TDOA-based location, RSS-based location, PDOA-based location, or AoA-based location.

[0183] In another example, the positioning method may correspond to FD-PDOA positioning, and where the resource sets do not overlap in the FD. In such examples, the network entity may receive an estimated range between the wireless device and the IoT device from the wireless device, and the network entity may estimate the positioning of the IoT device based on the estimated range. In such examples, the resource sets may also not overlap in the time domain. In such examples, the configuration may further include a bandwidth or a minimum bandwidth for the resource set, and where the bandwidth or the minimum bandwidth may be based on the accuracy specified for estimating the range between the wireless device and the IoT device. In such examples, the configuration may further include the number of times or the minimum number of times the wireless device is to perform FD-PDOA positioning, and the number or the minimum number may be based on the accuracy specified for estimating the range between the wireless device and the IoT device. In such examples, the configuration may further include a minimum bandwidth and a minimum time span for the resource set, and the minimum bandwidth and the minimum time span may be based on the moving speed of the wireless device to maintain the coherent bandwidth and coherent time for FD-PDOA positioning.

[0184] Figure 20FIG. 2000 is a diagram illustrating an example of a hardware implementation for network entity 2002. Network entity 2002 can be a BS, a component of a BS, or can implement BS functionality. Network entity 2002 can include at least one of CU 2010, DU 2030, or RU 2040. For example, depending on the layer functionality processed by the IoT device positioning configuration component 199, network entity 2002 can include CU 2010; both CU 2010 and DU 2030; each of CU 2010, DU 2030, and RU 2040; DU 2030; both DU 2030 and RU 2040; or RU 2040. CU 2010 can include CU processor 2012. CU processor 2012 can include on-chip memory 2012'. In some aspects, CU 2010 can also include additional memory module 2014 and communication interface 2018. CU 2010 communicates with DU 2030 via a midhaul link (such as the F1 interface). DU 2030 can include DU processor 2032. DU processor 2032 can include on-chip memory 2032'. In some aspects, DU 2030 can also include additional memory module 2034 and communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 can include RU processor 2042. RU processor 2042 can include on-chip memory 2042'. In some aspects, RU 2040 can also include additional memory module 2044, one or more transceivers 2046, antenna 2080, and communication interface 2048. RU 2040 communicates with UE 104. On-chip memories 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 can each be considered computer-readable media / memory. Each computer-readable media / memory can be non-transitory. Each of processors 2012, 2032, 2042 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by the processor when executing the software.

[0185] As discussed above, the IoT device positioning configuration component 199 is configured to receive from a wireless device a set of requests for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device. The IoT device positioning configuration component 199 may also be configured to send or receive an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device, where the indication is sent to or received from the wireless device. The IoT device positioning configuration component 199 may also be configured to send to the wireless device at least one response that includes a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device based on the set of requests and the indicated positioning method. The IoT device positioning configuration component 199 may be within one or more processors of one or more of the CU 2010, DU 2030, and RU 2040. The IoT device positioning configuration component 199 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of these operations. The network entity 2002 may include various components configured for various functions. As shown, the network entity 2002 may include various components configured for various functions. In one configuration, the network entity 2002 includes means for receiving from a wireless device a set of requests for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device. The network entity 2002 may also include means for sending or receiving an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device, where the indication is sent to or received from the wireless device. The network entity 2002 may also include means for sending to the wireless device at least one response that includes a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device based on the set of requests and the indicated positioning method.

[0186] In one example, the network entity 2002 may also include means for receiving from the wireless device the accuracy specified for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device, and means for sending to the wireless device an indication of the positioning method based on the specified accuracy.

[0187] In another example, each request in the set of requests may be associated with at least one response based on a timing window, an ID associated with the IoT device, a request ID associated with each request in the set of requests, a response ID associated with the at least one response, or a combination thereof.

[0188] In another example, the number of requests in the request set or the periodicity between requests in the request set may be based on the moving speed of the wireless device. In such examples, the network entity 2002 may further include components for determining the periodicity based on the moving speed of the wireless device, and components for sending the determined periodicity to the wireless device.

[0189] In another example, the network entity 2002 may further include components for receiving a second indication of the moving speed or positioning change of the wireless device from the wireless device, where the configuration for the resource set may include a periodicity associated with the resource set, and the periodicity is based on the moving speed or positioning change.

[0190] In another example, the positioning method may include: positioning based on ToA, positioning based on TDOA, positioning based on RSS, positioning based on PDOA, or positioning based on AoA.

[0191] In another example, the positioning method may correspond to FD-PDOA positioning, and the resource sets do not overlap in the FD. In such examples, the network entity 2002 may further include components for receiving an estimated range between the wireless device and the IoT device from the wireless device, and components for estimating the positioning of the IoT device based on the estimated range.

[0192] In such examples, the resource sets may also not overlap in the time domain.

[0193] In such examples, the configuration may further include the bandwidth or minimum bandwidth for the resource set, and the bandwidth or the minimum bandwidth may be based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0194] In such examples, the configuration may further include the number of times or the minimum number of times for the wireless device to perform FD-PDOA positioning, and the number of times or the minimum number of times may be based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0195] In such examples, the configuration may further include the minimum bandwidth and the minimum time span for the resource set, and the minimum bandwidth and the minimum time span may be based on the moving speed of the wireless device to maintain the coherent bandwidth and coherent time for FD-PDOA positioning.

[0196] The component can be the IoT device positioning configuration component 199 of the network entity 2002 configured to perform the functions described by the component. As described above, the network entity 2002 can include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the component can be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described by the component.

[0197] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely illustrative of example methods. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. Further, some blocks can be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0198] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims, and the singular forms of elements are not intended to mean "one and only one" but "one or more" unless specifically stated otherwise. Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases, such as "when...," do not mean an immediate action in response to or during the occurrence of an action, but simply imply that the action will occur if the condition is met, without requiring a specific or immediate time limitation for the occurrence of the action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or transmits data to a second device, the data may be received / transmitted directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," etc. do not substitute for the word "component." Thus, no claim element is to be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

[0199] As used herein, the phrase "based on" should not be construed to refer to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be construed as "at least based on A", unless stated otherwise specifically.

[0200] The following aspects are merely illustrative and can be combined with other aspects or teachings described herein without limitation.

[0201] Aspect 1 is a method for wireless communication at a wireless device, the method comprising: sending a set of requests to a network entity for estimating a range between the wireless device and an IoT device or for estimating a location of the IoT device; sending or receiving an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, wherein the indication is sent to the network entity or received from the network entity; and receiving at least one response from the network entity, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

[0202] Aspect 2 is the method according to aspect 1, the method further comprising: estimating the range between the wireless device and the IoT device or estimating the location of the IoT device using the indicated positioning method via the set of resources.

[0203] Aspect 3 is the method according to aspect 1 or 2, the method further comprising: sending to the network entity a specified accuracy for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device; and receiving from the network entity the indication of the positioning method based on the specified accuracy.

[0204] Aspect 4 is the method according to any one of aspects 1 to 3, wherein the set of requests corresponds to one request for estimating the range between the wireless device and the IoT device, and wherein the set of requests corresponds to more than one request for estimating the location of the IoT device, and the set of requests do not overlap in the time domain.

[0205] Aspect 5 is the method according to any one of aspects 1 to 4, wherein each request in the set of requests is associated with the at least one response based on a timing window, an ID associated with the IoT device, a request ID associated with each request in the set of requests, a response ID associated with the at least one response, or a combination thereof.

[0206] Aspect 6 is the method according to any one of Aspects 1 to 5, wherein the number of requests in the request set or the periodicity between the requests in the request set is based on the moving speed of the wireless device.

[0207] Aspect 7 is the method according to Aspect 6, the method further comprising: determining the periodicity based on the moving speed of the wireless device; or receiving the periodicity from the network entity based on the moving speed of the wireless device.

[0208] Aspect 8 is the method according to Aspect 6, the method further comprising: in a case where the moving speed of the wireless device exceeds a speed threshold, avoiding estimating the range between the wireless device and the IoT device or estimating the positioning of the IoT device to the network entity.

[0209] Aspect 9 is the method according to any one of Aspects 1 to 8, the method further comprising: in a case where the positioning of the wireless device has changed its positioning by more than a distance threshold, sending a second request set for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device to the network entity.

[0210] Aspect 10 is the method according to any one of Aspects 1 to 9, the method further comprising: sending a second indication of the moving speed or positioning change of the wireless device to the network entity, wherein the configuration for the resource set includes a periodicity associated with the resource set, the periodicity being based on the moving speed or the positioning change.

[0211] Aspect 11 is the method according to any one of Aspects 1 to 10, wherein the positioning method includes: positioning based on ToA, positioning based on TDOA, positioning based on RSS, positioning based on PDOA, or positioning based on AoA.

[0212] Aspect 12 is the method according to any one of Aspects 1 to 11, wherein the positioning method corresponds to FD-PDOA positioning, and wherein the resource sets do not overlap in FD, the method further comprising: using the resource sets to estimate the range between the wireless device and the IoT device based on the FD-PDOA positioning.

[0213] Aspect 13 is the method according to Aspect 12, wherein estimating the range between the wireless device and the IoT device based on the FD-PDOA positioning includes: sending a first set of signals to the IoT device; receiving a second set of signals backscattered from the IoT device; and measuring the PDOA of the second set of signals.

[0214] Aspect 14 is the method according to aspect 13, the method further comprising: estimating the positioning of the IoT device based on the estimated range; or sending the estimated range to the network entity to assist the network entity in estimating the positioning of the IoT device.

[0215] Aspect 15 is the method according to aspect 14, wherein the resource sets are further non-overlapping in the time domain.

[0216] Aspect 16 is the method according to aspect 15, wherein the configuration further includes the bandwidth or minimum bandwidth for the resource sets, and wherein the bandwidth or the minimum bandwidth is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0217] Aspect 17 is the method according to aspect 16, wherein the configuration further includes the number or minimum number of times the wireless device is to perform the PDOA positioning, and wherein the number or the minimum number of times is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0218] Aspect 18 is the method according to aspect 17, wherein the configuration further includes the minimum bandwidth and minimum time span for the resource sets, and wherein the minimum bandwidth and the minimum time span are based on the moving speed of the wireless device to maintain the coherent bandwidth and coherent time for the PDOA positioning.

[0219] Aspect 19 is an apparatus for wireless communication at a wireless device, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to implement any one of aspects 1 to 18 at least in part based on information stored in the memory.

[0220] Aspect 20 is the apparatus according to aspect 19, the apparatus further comprising: at least one of a transceiver or an antenna coupled to the at least one processor.

[0221] Aspect 21 is an apparatus for wireless communication, the apparatus comprising components for implementing any one of aspects 1 to 18.

[0222] Aspect 22 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 18.

[0223] Aspect 23 is a method for wireless communication at a network entity, the method comprising: receiving, from a wireless device, a set of requests for estimating a range between the wireless device and an IoT device or for estimating a location of the IoT device; sending or receiving an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device, wherein the indication is sent to or received from the wireless device; and sending to the wireless device at least one response, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

[0224] Aspect 24 is the method according to aspect 23, the method further comprising: receiving, from the wireless device, a specified accuracy for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device; and sending the indication of the positioning method to the wireless device based on the specified accuracy.

[0225] Aspect 25 is the method according to aspect 23 or aspect 24, wherein each request in the set of requests is associated with the at least one response based on a timing window, an ID associated with the IoT device, a request ID associated with each request in the set of requests, a response ID associated with the at least one response, or a combination thereof.

[0226] Aspect 26 is the method according to any one of aspects 23 to 25, wherein a number of requests in the set of requests or a periodicity between requests in the set of requests is based on a moving speed of the wireless device, the method further comprising: determining the periodicity based on the moving speed of the wireless device; and sending the determined periodicity to the wireless device.

[0227] Aspect 27 is the method according to any one of aspects 23 to 26, the method further comprising: receiving, from the wireless device, a second indication of a moving speed or a location change of the wireless device, wherein the configuration of the set of resources includes a periodicity associated with the set of resources, the periodicity being based on the moving speed or the location change.

[0228] Aspect 28 is the method according to any one of aspects 23 to 27, wherein the positioning method includes: positioning based on ToA, positioning based on TDOA, positioning based on RSS, positioning based on PDOA, or positioning based on AoA.

[0229] Aspect 29 is the method according to any one of aspects 23 to 28, wherein the positioning method corresponds to FD-PDOA positioning, and wherein the resource sets do not overlap in FD.

[0230] Aspect 30 is the method according to aspect 29, the method further comprising: receiving from the wireless device an estimated range between the wireless device and the IoT device; and estimating the positioning of the IoT device based on the estimated range.

[0231] Aspect 31 is the method according to aspect 29, wherein the resource sets further do not overlap in the time domain.

[0232] Aspect 32 is the method according to aspect 29, wherein the configuration further comprises a bandwidth or a minimum bandwidth for the resource sets, and wherein the bandwidth or the minimum bandwidth is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0233] Aspect 33 is the method according to aspect 29, wherein the configuration further comprises the number of times or the minimum number of times for the wireless device to perform the FD-PDOA positioning, and wherein the number of times or the minimum number of times is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

[0234] Aspect 34 is the method according to aspect 29, wherein the configuration further comprises a minimum bandwidth and a minimum time span for the resource sets, and wherein the minimum bandwidth and the minimum time span are based on the moving speed of the wireless device to maintain the coherent bandwidth and coherent time for the FD-PDOA positioning.

[0235] Aspect 35 is a device for wireless communication at a network entity, the device comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of aspects 23 to 34 at least in part based on information stored in the memory.

[0236] Aspect 36 is the device according to aspect 35, the device further comprising: at least one of a transceiver or an antenna coupled to the at least one processor.

[0237] Aspect 37 is a device for wireless communication, the device comprising components for implementing any one of aspects 23 to 34.

[0238] Aspect 38 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 23 to 34.

Claims

1. An apparatus for wireless communication at a wireless device, the apparatus comprising: a memory; and at least one processor coupled to the memory and configured, at least in part based on information stored in the memory, to: send a set of requests to a network entity for estimating a range between the wireless device and an Internet of Things (IoT) device or for estimating a location of the IoT device; send to or receive from the network entity an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device; and receive from the network entity at least one response, the at least one response including a configuration of a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

2. The apparatus according to claim 1, wherein the at least one processor is further configured to: estimate the range between the wireless device and the IoT device or estimate the location of the IoT device using the indicated positioning method via the set of resources.

3. The apparatus according to claim 1, wherein the at least one processor is further configured to: send to the network entity a specified accuracy for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device; and receive from the network entity the indication of the positioning method based on the specified accuracy.

4. The apparatus according to claim 1, wherein the set of requests corresponds to one request for estimating the range between the wireless device and the IoT device, and wherein the set of requests corresponds to more than one request for estimating the location of the IoT device, the set of requests not overlapping in time domain.

5. The apparatus according to claim 1, wherein each request in the set of requests is associated with the at least one response based on a timing window, an identifier (ID) associated with the IoT device, a request ID associated with each request in the set of requests, a response ID associated with the at least one response, or a combination thereof.

6. The apparatus according to claim 1, wherein a number of requests in the set of requests or a periodicity between requests in the set of requests is based on a moving speed of the wireless device.

7. The apparatus according to claim 6, wherein the at least one processor is further configured to: determine the periodicity based on the moving speed of the wireless device or receive the periodicity from the network entity based on the moving speed of the wireless device; and in a case where the moving speed of the wireless device exceeds a speed threshold, avoid estimating the range between the wireless device and the IoT device or estimating the location of the IoT device to the network entity.

8. The apparatus according to claim 1, wherein the at least one processor is further configured to: in a case where the positioning of the wireless device has changed its positioning by more than a distance threshold, send a second set of requests to the network entity for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device.

9. The apparatus according to claim 1, wherein the at least one processor is further configured to: send a second indication of the moving speed or positioning change of the wireless device to the network entity, wherein the configuration for the resource set includes a periodicity associated with the resource set, and the periodicity is based on the moving speed or the positioning change.

10. The apparatus according to claim 1, wherein the positioning method includes: positioning based on time of arrival (ToA), positioning based on time difference of arrival (TDOA), positioning based on received signal strength (RSS), positioning based on phase difference of arrival (PDOA), or positioning based on angle of arrival (AoA).

11. The apparatus according to claim 1, wherein the positioning method corresponds to frequency domain (FD) phase difference of arrival (PDOA) (FD-PDOA) positioning, and wherein the resource sets do not overlap in the FD, and the at least one processor is configured to: use the resource sets to estimate the range between the wireless device and the IoT device based on the FD-PDOA positioning.

12. The apparatus according to claim 11, wherein in order to estimate the range between the wireless device and the IoT device based on the FD-PDOA positioning, the at least one processor is configured to: send a first set of signals to the IoT device; receive a second set of signals backscattered from the IoT device; and measure the PDOA of the second set of signals.

13. The apparatus according to claim 11, wherein the at least one processor is further configured to: estimate the positioning of the IoT device based on the estimated range; or send the estimated range to the network entity to assist the network entity in estimating the positioning of the IoT device.

14. The apparatus according to claim 11, wherein the resource sets further do not overlap in the time domain (TD).

15. The apparatus according to claim 11, wherein the configuration further includes a bandwidth or a minimum bandwidth for the resource set, and wherein the bandwidth or the minimum bandwidth is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

16. The apparatus according to claim 11, wherein the configuration further includes the number of times or the minimum number of times for the wireless device to perform the FD-PDOA positioning, and wherein the number of times or the minimum number of times is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

17. The apparatus according to claim 11, wherein the configuration further includes a minimum bandwidth and a minimum time span for the resource set, and wherein the minimum bandwidth and the minimum time span are based on the moving speed of the wireless device to maintain a coherent bandwidth and a coherent time for the FD-PDOA positioning.

18. A method for wireless communication at a wireless device, the method comprising: sending a set of requests to a network entity for estimating a range between the wireless device and an Internet of Things (IoT) device or for estimating a location of the IoT device; sending to or receiving from the network entity an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device; and receiving from the network entity at least one response, the at least one response including a configuration of a resource set for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

19. A device for wireless communication at a network entity, the device comprising: a memory; and at least one processor coupled to the memory and configured at least in part based on information stored in the memory to: receive from a wireless device a set of requests for estimating a range between the wireless device and an Internet of Things (IoT) device or for estimating a location of the IoT device; send to or receive from the wireless device an indication of a positioning method for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device; and send to the wireless device at least one response, the at least one response including a configuration of a resource set for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

20. The apparatus according to claim 19, wherein the at least one processor is further configured to: receive from the wireless device a specified accuracy for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device; and send the indication of the positioning method to the wireless device based on the specified accuracy.

21. The apparatus according to claim 19, wherein each request in the set of requests is associated with the at least one response based on a timing window, an identifier (ID) associated with the IoT device, a request ID associated with each request in the set of requests, a response ID associated with the at least one response, or a combination thereof.

22. The apparatus according to claim 19, wherein the number of requests in the request set or the periodicity between requests in the request set is based on the moving speed of the wireless device, and wherein the at least one processor is further configured to: determine the periodicity based on the moving speed of the wireless device; and send the determined periodicity to the wireless device.

23. The apparatus according to claim 19, wherein the at least one processor is further configured to: receive from the wireless device a second indication of the moving speed or positioning change of the wireless device, wherein the configuration for the resource set includes a periodicity associated with the resource set, the periodicity being based on the moving speed or the positioning change.

24. The apparatus according to claim 19, wherein the positioning method includes: positioning based on time of arrival (ToA), positioning based on time difference of arrival (TDOA), positioning based on received signal strength (RSS), positioning based on phase difference of arrival (PDOA), or positioning based on angle of arrival (AoA).

25. The apparatus according to claim 19, wherein the positioning method corresponds to frequency domain (FD) phase difference of arrival (PDOA) (FD-PDOA) positioning, and wherein the resource set does not overlap in the FD.

26. The apparatus according to claim 25, wherein the at least one processor is further configured to: receive from the wireless device an estimated range between the wireless device and the IoT device; and estimate the positioning of the IoT device based on the estimated range.

27. The apparatus according to claim 25, wherein the configuration further includes a bandwidth or a minimum bandwidth for the resource set, and wherein the bandwidth or the minimum bandwidth is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

28. The apparatus according to claim 25, wherein the configuration further includes the number of times or the minimum number of times for the wireless device to perform the FD-PDOA positioning, and wherein the number of times or the minimum number of times is based on the accuracy specified for estimating the range between the wireless device and the IoT device.

29. The apparatus according to claim 25, wherein the configuration further includes a minimum bandwidth and a minimum time span for the resource set, and wherein the minimum bandwidth and the minimum time span are based on the moving speed of the wireless device to maintain a coherent bandwidth and a coherent time for the FD-PDOA positioning.

30. A method for wireless communication at a network entity, the method comprising: receiving from a wireless device a set of requests for estimating a range between the wireless device and an Internet of Things (IoT) device or for estimating the positioning of the IoT device; sending to or receiving from the wireless device an indication indicating a positioning method for estimating the range between the wireless device and the IoT device or for estimating the positioning of the IoT device; and Send at least one response to the wireless device, the at least one response including a configuration for a set of resources for estimating the range between the wireless device and the IoT device or for estimating the location of the IoT device based on the set of requests and the indicated positioning method.

Images