Positioning using radio frequency identification (RFID) tags

Abstract

Aspects presented herein may enable a location of a UE to be determined based on a plurality of passive IoT devices having known locations. In one aspect, a UE receives information from a plurality of IoT devices, where the information includes an ID of a corresponding IoT device of the plurality of IoT devices and a location change indication for the corresponding IoT device, where the location change indication indicates whether a location of the corresponding IoT device has changed, where each of the plurality of IoT devices is associated with a known location. The UE obtains a location of one or more of the UE or at least one other IoT device based on the information received from the plurality of IoT devices including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Greek application serial number 20220100837, filed on October 11, 2022, entitled “POSITIONING USING RADIOFREQUENCY IDENTIFICATION (RFID) TAGS”, the entire text of which is expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications related to positioning. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR 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 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important 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 a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives information from a plurality of Internet of Things (IoT) devices, wherein the information includes an identification (ID) of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed, wherein each of the plurality of IoT devices is associated with a known location. The apparatus obtains the location of one or more of the UE or at least one other IoT device based on the information received from the plurality of IoT devices including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives at least one signal from at least one of a user equipment (UE) or a network entity. The apparatus uses the at least one signal to send information for at least one of the UE or the network entity, wherein the information includes an identification (ID) of the IoT device and a location change indication for the IoT device, wherein the location change indication indicates whether the location of the IoT device has changed, wherein the IoT device is associated with a known location.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives a first indication from a UE to calculate the location of the UE, wherein the first indication is associated with information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed from an initial location, wherein each of the plurality of IoT devices is associated with a known location. The apparatus calculates the location of the UE or the at least one other IoT device based on the information including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device.

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

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

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

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

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

[0015] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

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

[0017] Figure 4 is a diagram illustrating an example of UE positioning based on reference signal measurement.

[0018] Figure 5 is a diagram illustrating examples of different types of Internet of Things (IoT) devices according to aspects of the present disclosure.

[0019] Figure 6 is a diagram illustrating an example passive IoT device according to aspects of the present disclosure.

[0020] Figure 7 is a diagram illustrating an example of a passive IoT device that performs backscattering / reflection of a signal through modulation according to aspects of the present disclosure.

[0021] Fig. 8A is a diagram illustrating example power relationships between a radio frequency (RF) source, a radio frequency identification (RFID) tag, and an RFID reader device in accordance with aspects of the present disclosure.

[0022] Figure 8B is a diagram illustrating an example of single-station operation according to aspects of the present disclosure.

[0023] Fig. 9 is a diagram illustrating an example communication procedure between an RFID reader and an RFID tag according to aspects of the present disclosure.

[0024] Fig.10 is a diagram 1000 illustrating example communications between a UE and a set of RFID tags during a UE positioning session in accordance with aspects of the present disclosure.

[0025] Fig.11 is a communication flow illustrating example signaling between a server, an RFID reader, and an RFID tag according to aspects of the present disclosure.

[0026] Fig.12 is a communication flow illustrating example signaling between a server, an RFID reader, and an RFID tag according to aspects of the present disclosure.

[0027] Fig.13 is a communication flow illustrating example signaling between a server, an RFID reader, and an RFID tag according to aspects of the present disclosure.

[0028] Fig.14 is a flow chart of a method of wireless communication.

[0029] Fig.15 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0030] Fig.16 is a flow chart of a method of wireless communication.

[0031] Fig.17 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0032] Fig.18 is a flow chart of a method of wireless communication.

[0033] Fig.19 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0034] Various aspects presented herein may enable the determination of the location of a UE based on multiple passive IoT devices with known locations. For example, in one aspect, if the UE is surrounded by multiple passive IoT devices (e.g., RFID tags) with known locations, the UE may be able to determine its location or its location relative to one or more passive IoT devices (or one or more known location devices) based on performing positioning measurements (e.g., time of arrival (ToA), angle of arrival (AoA), round trip time (RTT), and / or other location-related measurements, etc.) for signals sent from the passive IoT devices (e.g., backscatter signals, configured reference signals, etc.). On the other hand, each of the passive IoT devices (or the ID of the passive IoT device) may be associated with a specific location / position in a database or positioning server. Therefore, if the UE has access to the database / positioning server, the UE may obtain the location / position of the passive IoT device from the database / positioning server (e.g., based on the ID of the passive IoT device). On the other hand, in order to improve positioning accuracy, the UE can also be configured to determine whether a passive IoT device has changed its position / location, and the UE can use a passive IoT device that has not changed its position / location for UE positioning, and can refrain from using a passive IoT device that has changed its position / location for UE positioning.

[0035] The various aspects presented herein also provide various features that facilitate accurate positioning of UEs based on passive IoT devices. For example, in one aspect, signaling related to passive IoT devices with motion detectors, passive IoT devices without motion detectors, and passive IoT devices with the ability to determine their new locations and / or indicate their new locations is also provided to improve the positioning of the UE. For example, an RFID reader configured to determine its positioning (e.g., with assistance from an RF source or network entity / node for transmitting a continuous wave (CW) or signal that will be backscattered by the passive IoT device) or an RF source (e.g., with assistance from an RFID reader or network entity / node, or if it is an FD device, it is performing both acquisition and reading) can transmit a signal to surrounding passive IoT devices. In response, the passive IoT device can respond to the RFID reader or RF source regarding its motion detection capabilities, whether its positioning has changed, and / or its new location, etc. The RFID reader or RF source can then discard readings from passive IoT devices that have changed their positioning (note that the RFID reader may not know which passive IoT devices are around it). In another aspect, the passive IoT device may also send its measurements to the RFID reader, such as by including the motion detection metrics as a digital payload in the backscatter signal, or embedding / modulating them in the backscatter signal. In response, the RFID reader or another entity (e.g., a network entity / node) may determine whether the passive IoT device has changed location based on the motion detection metrics provided by the passive IoT device (discussed below).

[0036] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0037] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0038] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which 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, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0039] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may 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 that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0040] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described 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 include 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 various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[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, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element 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 decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0042] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack 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 in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a 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 take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0044] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated 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 corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0045] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, 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 a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send 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 specific implementations, 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 unit may communicate bidirectionally with the CU-CP unit 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 a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part 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 control functions hosted by CU 110.

[0048] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may 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 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0050] The non-RT RIC 115 may be configured to include logic functions that enable 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 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0051] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function 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 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0052] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which 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 uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as 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 through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. 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 carrier may be referred to as a secondary cell (SCell).

[0053] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The 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). The D2D communication may be through a variety of 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 also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

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

[0056] 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.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0057] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

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

[0059] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The 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 a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed 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. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. 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, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, 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, NR signals (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 UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, 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, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0062] Refer again Figure 1 In some aspects, the UE 104 may be configured to: receive information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed, wherein each of the plurality of IoT devices is associated with a known location; and obtain the location of one or more of the UE or at least one other IoT device based on the information received from the plurality of IoT devices including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device (e.g., via the RFID reading component 198).

[0063] In some aspects, the base station 102 may be configured to: receive a first indication from a UE to calculate a location of the UE, wherein the first indication is associated with information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed from an initial location, wherein each of the plurality of IoT devices is associated with a known location; and calculate the location of the UE or the at least one other IoT device based on the information including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device (e.g., via the UE positioning component 199).

[0064] In certain aspects, the RFID tag 1106 (e.g., an IoT device) may be configured to: receive at least one signal from at least one of a UE or a network entity; and use the at least one signal to send information for the UE or at least one of the network entity, wherein the information includes an ID of the IoT device and a location change indication for the IoT device, wherein the location change indication indicates whether the location of the IoT device has changed, wherein the IoT device is associated with a known location (e.g., via the backscatter component 197).

[0065] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0066] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various 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 (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, 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 a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0067]

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

[0069] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 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] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending 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] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one 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 may 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. A 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 RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may 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 opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a 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 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 not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0073] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first 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 may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0074] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and 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 may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0075] Figure 3375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting 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 transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with 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 through HARQ, priority handling, and logical channel prioritization.

[0076] The transmit (TX) processor 316 and 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) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0077] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a 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 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to 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 codes 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 ACK and / or NACK protocols to support HARQ operations.

[0079] Similar to the functionality described in conjunction 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 delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0080] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 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 conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0082] The controller / processor 375 may be associated with a memory 376 that stores program codes 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 ACK and / or NACK protocols to support HARQ operations.

[0083] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The RFID reading component 198 combines various aspects.

[0084] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The UE positioning component 199 combines various aspects.

[0085] Figure 4 4 is a diagram illustrating an example of UE positioning based on reference signal measurements (which may also be referred to as “network-based positioning”) according to various aspects of the present disclosure. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX A DL positioning reference signal (PRS) (DL-PRS) 410 is received. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. 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 UL-SRS 412 based on ||T SRS_RX –T PRS_TX |–|T SRS_TX –T PRS_RX || determines RTT 414. Thus, multi-RTT positioning may utilize UE Rx-Tx time difference measurements (i.e., |T SRS_TX –T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (ie, |T SRS_RX –T PRS_TX|) and UL-SRS-RSRP. The UE 404 measures the UE Rx-Tx time difference measurement (and / or the DL-PRS-RSRP of the received signal) using the assistance data received from the positioning server, and the TRP 402, 406 measures the gNB Rx-Tx time difference measurement (and / or the UL-SRS-RSRP of the received signal) using the assistance data received from the positioning server. These measurements may be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the position 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] PRS may be defined for network-based positioning (e.g., NR positioning) to enable UEs to detect and measure more neighboring transmit and receive points (TRPs), with multiple configurations supported to enable various deployments (e.g., indoor, outdoor, below 6, mmW, etc.). To support PRS beam operation, beam scanning may also be configured for PRS. The UL positioning reference signal may be based on a sounding reference signal (SRS) with enhancements / adjustments for positioning purposes. In some examples, the UL-PRS may be referred to as "SRS for positioning," and a new information element (IE) may be configured for SRS for positioning in RRC signaling.

[0087] The DL PRS-RSRP may be defined as the linear average of the power contributions (in [W]) of the resource elements of the antenna ports 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 the DL PRS-RSRP may be the antenna connector of the UE. For FR2, the DL PRS-RSRP may be measured based on the combined signals 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 may 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 may be measured over the configured resource elements in the considered measurement frequency bandwidth, in the configured measurement occasions. In some examples, for FR1, the reference point for the UL SRS-RSRP may be the antenna connector of the base station (e.g., gNB). For FR2, the UL SRS-RSRP may be measured based on the combined signals 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 of the individual receiver branches.

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

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

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

[0091] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and / or UL-SRS-RSRP) at multiple TRPs 402, 406 of uplink signals sent from the UE 404. The TRPs 402, 406 measure the UL-RTOA (and / or UL-SRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404.

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

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

[0094] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used 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, the downlink positioning reference signal may be referred to as "DL PRS", and the uplink positioning reference signal (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS". In addition, for signals that can be sent in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prepended with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" may be distinguished from "DL-DMRS".

[0095] In some scenarios, the location or relative location / distance of a wireless device may be determined based on measuring signals backscattered / reflected from a set of Internet of Things (IoT) devices. For example, the wireless device (or another wireless device) may send a signal to the set of IoT devices, and the wireless device may receive a signal reflected / backscattered from the set of IoT devices (which may be referred to as a "backscattered signal" hereinafter) and measure the received backscattered signal. For example, the wireless device may measure the round trip time (RTT), time of arrival (ToA), angle of arrival (AoA), and the like of the backscattered signal. Figure 4Other positioning-related measurements described (which may be collectively referred to as "positioning measurements" below). Based on positioning measurements for backscatter signals, the position and / or distance of the first wireless device relative to one or more IoT devices can be calculated, estimated and / or determined (e.g., by the first wireless device itself or another entity). The relative positioning of a wireless device may refer to the positioning of the wireless device relative to another device or entity such as an IoT device (e.g., the wireless device is 10 meters away from the IoT device, the wireless device is east of the IoT device, etc.). In some examples, the wireless device may be referred to as a backscatter receiver, a backscatter reader, an RFID reader, an RFID reader UE, and / or a reader UE. IoT devices may be referred to as passive IoT devices, radio frequency identification (RFID) tags (or simply tags), backscatter-based IoT, or backscatter-based RFID. RFID may refer to a form of wireless communication that combines the use of electromagnetic or electrostatic coupling in the radio frequency portion of the electromagnetic spectrum to uniquely identify objects, animals, or people, etc. In addition, a wireless device that sends a signal to an IoT device may be referred to as an RF source, an RF source UE, or a carrier transmitter. Note that a wireless device may be able to both send signals to a passive IoT device and receive reflected signals (e.g., readings) from the passive IoT device, which may be referred to as a full-duplex device (discussed below). Thus, an RF source may also be an RFID reader, and vice versa. For purposes of this disclosure, an IoT device may refer to a device that is capable of wirelessly connecting to a network and has the ability to send data.

[0096] Figure 5500 is a diagram illustrating examples of different types of IoT devices (e.g., RFID tags) according to various aspects of the present disclosure. IoT devices can be configured as passive devices or active devices. For example, as shown at 504, a passive IoT device 502 can be a device that does not have a battery in its terminal, but its terminal can accumulate (e.g., absorb or collect) energy from radio signaling (e.g., from a base station, RF source, wireless device, UE, etc.). In another example, as shown at 506, the passive IoT device 502 may include a supercapacitor, wherein the terminal of the passive IoT device 502 can also accumulate energy from other energy sources (such as solar energy, wind, thermal power, etc.) as a supplement. In another example, as shown at 508, the passive IoT device 502 can be configured as semi-passive with a battery, which can enable the passive IoT device 502 to use power from the battery to modulate a signal, and the passive IoT device 502 can be able to be activated almost all the time but may not actively transmit. For a passive IoT device, a user can connect to it and receive information from it. On the other hand, an active IoT device 510 may be a device that transmits information as a timed stream, a threshold stream, and / or a constant stream. For example, an active IoT device or a semi-active IoT device may include amplification capabilities and / or active RF components that may enable the IoT device to send better quality transmissions / information.

[0097] Figure 6 600 is a diagram illustrating an example passive IoT device according to aspects of the present disclosure. A passive IoT device 602 (e.g., an RFID tag) may include a small transponder that transmits an information-bearing signal upon receiving a signal (e.g., from an RFID reader 604). The passive IoT device 602 may operate without a battery, with low operating expenses (OPEX), with low maintenance costs, and / or with a long life cycle. As shown at 606, the passive IoT device 602 may absorb / harvest energy in the air based on an energy signal transmitted from the RFID reader 604 to power its transmit / receive circuits. Subsequently, as shown at 608, the passive IoT device 602 may use the absorbed / harvested energy to transmit (e.g., reflect / backscatter) an information signal (e.g., a signal containing information, a 1-bit indication, a multi-bit indication, etc.), wherein the transmitted information signal may typically be backscatter modulated (e.g., modulated based on a signal received from the RFID reader 604). In some examples, the passive IoT device 602 may have a coverage of 20-30 meters in an indoor environment and 100-200 meters in an outdoor environment. The power consumption of the passive IoT device 602 may be within 0.1 milliwatts (mW), with a positioning accuracy between 3 and 5 meters and a data rate of 10-100 kilobytes per second (kpbs). The passive IoT device 602 may also be configured to use both licensed and unlicensed bands.

[0098] Figure 7 700 is a diagram illustrating an example of a passive IoT device (e.g., RFID tag) performing backscattering / reflection of a signal by modulation in accordance with 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) may be amplitude shift keying (ASK), where the passive IoT device may be configured to turn on reflection when sending an information bit "1" and turn off reflection when sending an information bit "0".

[0099] 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) may transmit a specific radio wave denoted 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 may be represented as s(n)∈{0,1}. Then, as shown at 712, the received signal y(n) at the second device (e.g., a second UE, an RF reader, etc.) may be represented by y(n)=(h D1D2 (n)+σ f h D1T (n)h TD2 (n)s(n))x(n)+noise. It should be noted that the first device 702 and the second device 706 can also be the same device (which can be called a full-duplex device). In one example, when s(n)=0, the RFID tag 704 can be configured to turn off reflection (for example, the RFID tag 704 does not send any signal), so that the second device 706 can only receive the direct link signal from the first device 702 (for example, y(n)=h D1D2 However, when s(n)=1, the RFID tag 704 can be configured to turn on reflection so 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, such as shown at 712, where σ f can represent the reflection coefficient).

[0100] Fig. 8A 800A is a diagram illustrating an example power relationship between an RF source, an RFID tag, and an RFID reader device according to aspects of the present disclosure. In some examples, the reading of information from an RFID tag (such as in conjunction with Figure 7The RFID reader 800A may be based on a dual-station operation, where the device that sends the RF source to the RFID tag may be different from the device that reads the information sent from the RFID tag (e.g., the RF source and the RFID reader are different entities). For example, as shown in diagram 800A, a first device 802 (e.g., an RF source) may send a signal to an RFID tag 804, where the signal may be transmitted at a transmission (Tx) power P scatt-tag(dB) The link / path in which the signal is sent from the first device 802 to the RFID tag 804 may be referred to as the forward link. The power of the signal received by the RFID tag 804 may be referred to as the absorbed power and is represented by P absorb-tag(dB) express.

[0101] After the RFID tag 804 receives the signal from the first device 802, the RFID tag 804 may absorb (or harvest) power energy from the signal, modulate the signal, and then send the modulated signal to the second device 806 (e.g., an RFID reader), such as in conjunction with Figure 7 The link / path in which the modulated power signal is sent from the RFID tag 804 to the second device 806 may be referred to as a backscatter link, and the power of the modulated signal sent from the RFID tag 804 may be referred to as the backscatter power and is denoted by P tag-scatt(dB) express.

[0102] In one example, if the RFID tag 804 is able to modulate the signal received from the first device 802 without any energy loss (e.g., in an idealized case), the power absorbed by the RFID tag 804 and used for transmission may be equal to the power of the signal transmitted by the first device 802 (e.g., P scatt-tag(dB) =P absorb-tag(dB) =P tag-scatt(dB) ). However, in most scenarios (e.g., in real situations), the RFID tag 804 may receive and modulate the signal from the first device 802 with some energy loss. For example, there may be energy loss associated with the efficiency of the signal modulation at the RFID tag 804 (e.g., higher power loss when the modulation efficiency is low), which may be caused by M loss(dB) Thus, the power of the signal transmitted from the RFID tag 804 may be equal to the power absorbed by the RFID tag 804 minus the energy loss (e.g., P scatt-tag(dB) =P absorb-tag(dB) -M loss(dB) After the signal is modulated by the RFID tag 804 and sent to the second device 806, the power of the modulated signal received at the second device 806 (e.g., P RX-reader(dB)) may vary based on one or more conditions, such as the antenna transmission gain (G) at the RFID tag 804. TX-tag(dB) ), the antenna receiving gain G at the second device 806 RX-reader(dB) , and / or the distance of the backscatter link (i.e., the distance between the RFID tag 804 and the second device 806), etc. For example, the power of the modulated signal received at the second device 806 (e.g., P RX-reader(dB) ) can be calculated based on:

[0103] P RX-reader(dB) =P scatt-tag(dB) +G TX-tag(dB) +G RX-reader(dB) -20log 10 f (GHz) -20log 10 r backscatter(m) -32.44dB,

[0104] where f (GHz) It may be the frequency at which the signal is transmitted from the first device 802. For the second device 806 for receiving the modulated signal from the RFID tag 804, it is desirable that the power of the modulated signal received at the second device 806 exceeds its sensitivity (e.g., P RX-reader(dB) >sensitivity, which may indicate the minimum power of a signal that can be detected / received by the second device 806).

[0105] In some scenarios, the reading of information from RFID tags can also be based on single-station operation, where the device that transmits the RF source to the RFID tag can also be used to read the information sent from the RFID tag (e.g., the RF source transmitter and the backscatter receiver are co-located), such as Figure 8B In some examples, such a device may also be referred to as a full-duplex (FD) device, an FD reader, or an FD UE. The power relationship between an FD device and an RFID tag under single-station operation may be similar to that of a combined Fig. 8A The power relationship between the RF source, backscatter receiver and RFID tag for bistatic operation is described.

[0106] For purposes of this disclosure, in some scenarios, the RF source may be a UE configured to determine its location, and the RFID reader may be one of the following: a network node / entity (e.g., a relay node, a RAN node, a non-RAN node, an IAB node, a base station, a component of a base station, etc.), the UE itself (e.g., if the UE is a full-duplex device capable of providing both RF acquisition and RFID reading, such as Figure 8B ), or another UE assisting the RF source UE (e.g., only as shown in the first device in Fig. 8ARFID reader UE shown in the second device 806).

[0107] In another scenario, the RFID reader may be a UE configured to determine its location, and the RF source (e.g., an entity providing RF signals to assist the RFID reader) may be one of the following: a network node / entity (e.g., a relay node, a RAN node, a non-RAN node, an IAB node, a base station, a component of a base station, etc.), the UE itself (e.g., if the UE is a full-duplex device capable of providing both RF acquisition and RFID reading, such as Figure 8B ), or another UE assisting the RFID reader (e.g., only as shown in the first device in Fig. 8A RF source UE shown in the first device 802).

[0108] In another scenario, Fig. 8A The first device 802 and the second device 806 shown or Figure 8B As shown, only the first device (e.g., a full-duplex device) may be configured to locate one or more RFID tags, where the first device and / or the second device may be one of: a UE, or a network node / entity (e.g., a relay node, a RAN node, a non-RAN node, an IAB node, a base station, a component of a base station, etc.).

[0109] Fig. 9 900 is a diagram illustrating an example communication protocol between an RFID reader and an RFID tag according to aspects of the present disclosure. As shown at 902, an RFID reader (which may be an FD device capable of providing an RF source and reading RFID) may send a signal (e.g., continuous wave (CW)) to an RFID tag, and the RFID tag may absorb / harvest power from the signal, such as in conjunction with Figure 7 and Fig. 8A In some scenarios, an RFID tag may have a turn-on voltage, where it may take a period of time for the RFID tag to absorb power and have enough power to send information (eg, a modulated signal) or communicate with an RFID reader.

[0110] As shown at 904, after the RFID tag absorbs sufficient power and is turned on, the RFID reader may send a command or query to the RFID tag (or the RFID tag may become capable of receiving a command / query from the RFID reader). The RFID tag may continue to absorb power from the signal sent by the RFID reader (e.g., from the CW). Then, as shown at 906, in response to the command / query, the RFID tag may send the RFID reader the information requested by the RFID reader (e.g., via a multi-bit indication), such as in conjunction with Figure 7This process may continue and repeat until the RFID tag stops receiving signals from the RFID reader (eg, the RFID tag is no longer able to absorb power).

[0111] Various aspects presented herein may enable the determination of the location of a UE based on multiple passive IoT devices with known locations. For example, in one aspect, if the UE is surrounded by multiple passive IoT devices (e.g., RFID tags) with known locations, the UE may be able to determine its location or its location relative to one or more passive IoT devices (or one or more known location devices) based on performing positioning measurements (e.g., ToA, AoA, RTT, and / or other location-related measurements, etc.) on signals sent from the passive IoT devices (e.g., backscatter signals, configured reference signals, etc.). On the other hand, each of the passive IoT devices (or the ID of the passive IoT device) may be associated with a specific location / position in a database or positioning server. Therefore, if the UE has access to the database / positioning server, the UE may obtain the location / position of the passive IoT device from the database / positioning server (e.g., based on the ID of the passive IoT device). On the other hand, in order to improve positioning accuracy, the UE can also be configured to determine whether a passive IoT device has changed its position / location, and the UE can use a passive IoT device that has not changed its position / location for UE positioning, and can refrain from using a passive IoT device that has changed its position / location for UE positioning.

[0112] The various aspects presented herein also provide various features that facilitate accurate positioning of UEs based on passive IoT devices. For example, in one aspect, signaling related to passive IoT devices with motion detectors, passive IoT devices without motion detectors, and passive IoT devices with the ability to determine their new positions and / or indicate their new positions is also provided to improve the positioning of the UE. For example, an RFID reader configured to determine its positioning (e.g., with assistance from an RF source or network entity / node for transmitting a CW or signal that will be backscattered by a passive IoT device) or an RF source (e.g., with assistance from an RFID reader or network entity / node, or if it is an FD device, it is performing both tracing and reading) can transmit a signal to surrounding passive IoT devices. In response, the passive IoT device can respond to the RFID reader or RF source regarding its motion detection capabilities, whether its positioning has changed, and / or its new position, etc. The RFID reader or RF source can then discard readings from passive IoT devices whose positioning has changed (note that the RFID reader may not know which passive IoT devices are surrounding it). In another aspect, the passive IoT device may also send its measurements to the RFID reader, such as by including the motion detection metrics as a digital payload in the backscatter signal, or embedding / modulating them in the backscatter signal. In response, the RFID reader or another entity (e.g., a network entity / node) may determine whether the passive IoT device has changed location based on the motion detection metrics provided by the passive IoT device (discussed below).

[0113] Fig.10 1000 is a diagram illustrating example communications between a UE and a set of RFID tags during a UE positioning session in accordance with aspects of the present disclosure. In one aspect of the present disclosure, an RFID tag (e.g., a passive IoT device) may include motion detection capabilities (e.g., having at least one motion detection sensor), wherein the RFID tag may determine whether its positioning has changed based on motion detection or may be capable of generating / providing motion detection metrics via at least one motion detection sensor.

[0114] For example, a UE 1002, which may be an RF reader or FD device, may communicate with a set of RFID tags (e.g., read information sent from the set of RFID tags), wherein the set of RFID tags may include a first RFID tag 1004, a second RFID tag 1006, a third RFID tag 1008, a fourth RFID tag 1010, and up to an Nth RFID tag 1012. The UE 1002 may communicate with the set of RFID tags for a UE positioning session, wherein the UE is configured to measure backscatter signals received from the set of RFID tags to determine its own position. The first RFID tag 1004, the second RFID tag 1006, the third RFID tag 1008, and the Nth RFID tag 1012 may have motion detection capabilities. In addition, the second RFID tag 1006 may also include the ability to determine its new location and report its new location. On the other hand, the fourth RFID tag 1010 may not have motion detection capabilities (e.g., not having a motion detection sensor). Each RFID in the set of RFIDs may be associated with a corresponding identifier (ID), which may also be referred to as a tag ID. For example, the first RFID tag 1004 may be associated with a first tag ID, the second RFID tag 1006 may be associated with a second tag ID, and the third RFID tag 1008 may be associated with a third tag ID, etc. The tag ID of the RFID tag may be configured to be unique and different from other RFID tags. In addition, RFID tags with motion sensors, RFID tags with motion sensors and the ability to determine and report new locations, and / or RFID tags without motion sensors may be classified by different RFID tag categories and assigned their corresponding RFID tag categories. Therefore, the UE 1002 may select which RFID tags to use for UE positioning or prioritize them based on the corresponding RFID tag categories of the RFID tags.

[0115] In one example, when the RFID tag detects motion or if the RFID tag determines that it has moved, the RFID tag may indicate to the reader UE that its location has changed (e.g., this may be verified based on the last location information). For example, as shown at 1014 and 1016, based on its motion detection sensors and / or measurements obtained via its motion detection sensors, the second RFID tag 1006 and the third RFID tag 1008 may determine that its location has changed, and they may send an indication indicating its location change (e.g., a location change indication indicating a change in the location / position of the RFID tag, such as from the last read) to the UE 1002 (e.g., via a backscatter signal). Similarly, if the RFID does not detect any motion or if the RFID determines that it has not moved, the RFID tag may indicate to the reader UE that its location has not changed (e.g., this may also be verified based on the last location information). For example, as shown at 1018 and 1020, based on its motion detection sensor and / or the measurement obtained via its motion detection sensor, the second RFID tag 1006 and the third RFID tag 1008 can determine that its location has not changed, and they can send an indication indicating that there is no location change to the UE 1002 (e.g., via a backscatter signal). In addition, in order to be able to determine the relative location of the UE 1002 relative to the set of RFID tags, each RFID tag can include its corresponding tag ID in the indication, so that the UE 1002 can determine the location of the RFID tag based on its corresponding tag ID (e.g., obtained from a database or positioning server). In another example, the RFID tag can also indicate a timestamp associated with its last read (or last sent). For example, the RFID tag can indicate in the indication the last time it determined whether it has moved. Based on the timestamp, the UE 1002 can determine whether to use the reading from the RFID tag (e.g., if the timestamp exceeds a certain timing threshold, the UE 1002 can discard the reading of the RFID tag).

[0116] In another example, an RFID tag may determine if there is motion or movement based on kinetic energy harvesting, where a battery-free sensor on the RFID tag may be configured to detect motion when the RFID tag is being moved. For example, a "motion detected" state variable may be defined for the RFID tag to indicate a change in its location, which may be used for future reporting, or for transmitting an indication / notification directly to an RFID reader or network entity.

[0117] In one example, the ability of an RFID tag to detect a change in location and / or determine and report its new location may be shared with the UE 1002 as part of a response (e.g., via a capabilityInformation message) to a query from the UE 1002 or from a network entity / node (e.g., via a capabilityEnquery message). In another example, the capabilities of the RFID tag may be shared with the UE 1002 during an initial access procedure or discovery procedure by an RF source, RFID reader, and / or network entity (e.g., a base station). In some examples, the capability indication may be as simple as simply indicating the RFID tag class (and a specification or predefined configuration may specify what capabilities each RFID tag class has).

[0118] In another example, if the RFID tag does not have the ability to detect whether its location has changed (e.g., it does not have a motion detection sensor), the RFID tag may also send an indication indicating that it does not have such an ability, or the RFID tag may skip responding to the reader UE (e.g., the RFID tag may not reflect a signal). For example, as shown at 1022, since the fourth RFID tag 1010 does not have a motion detection capability, the fourth RFID tag 1010 may be configured to send an indication to the UE 1002 indicating that it does not have the ability to detect motion or a change in location, or be configured not to reflect a signal to the UE 1002.

[0119] Based on the indications received from the set of RFID tags as to whether their positions have changed, the reader UE may discard the RFID tags whose positions have changed (or skip readings from the RFID tags) and if they do not know their new positions (e.g., do not include positions or do not have them or if they cannot know their own positions), and then the reader UE may use the remaining RFID tags for UE positioning. For example, after the UE 1002 receives an indication from the third RFID tag 1008 that its position has changed and there is no new positioning information for the third RFID tag 1008, the UE 1002 may exclude / deprioritize the third RFID tag 1008 from the UE positioning session (e.g., by excluding its readings and measurements).

[0120] In another example, if the RFID tag is able to detect its current location, in some communication modes, the RFID tag may indicate that there is motion, and then the RFID tag may include new positioning information / indicate the new positioning information to the reader UE. Then, the reader UE can directly use the new positioning information (in the input from other RFID tags) to determine its location (for example, this can occur after accessing the location of some other RFID tags from the database). For example, as shown in 1014, the second RFID tag 1006 may include both the ability to detect motion and the ability to determine and report its current location. Therefore, the second RFID tag 1006 may also indicate its new location to the UE 1002 (for example, via a backscatter signal). Similarly, the ability signaling with the ability to determine its location can also be configured as part of the RFID tag category. For example, an RFID tag with the ability to determine its new location after moving can be classified in a different RFID tag category from an RFID tag that does not have the ability to determine its new location after moving (for example, the second RFID tag 1006 is in a different RFID tag category from the first RFID tag 1004).

[0121] In another example, if for privacy reasons, where the reader UE (e.g., UE 1002) cannot directly access the location of the RFID tag, the reader UE can be configured to collect all IDs associated with the RFID tag and its new positioning readings / information (if available) from the RFID tag. Subsequently, the reader UE 1002 can send the collected IDs (and new positioning readings / information (if available)) together with its own location readings / measurements (e.g., UE positioning related measurements, such as RTT, AoA, AoD of backscattered signals from RFID tags) to a server (e.g., location server, LMF, etc.) or controller. In response, the server or controller can determine the current location of the UE and indicate the current location of the UE to the UE.

[0122] Fig.11 1 is a communication flow 1100 illustrating example signaling between a server, an RFID reader, and an RFID tag according to aspects of the present disclosure. The numbers associated with the communication flow 1100 do not specify a particular time order and are used only as a reference to the communication flow 1100.

[0123] In one example, an RFID reader 1104 (e.g., a UE, a network entity, an FD device, etc.) may communicate with a set of RFID tags (a set of passive IoT devices), which may include a first RFID tag 1106 and up to an Nth RFID tag, and the RFID reader 1104 may also communicate with a server 1102 (e.g., a network entity such as a base station, a location server, or an LMF, etc.) for a UE positioning session (e.g., for determining a location of the UE or a location of the UE relative to at least one RFID tag), such as in conjunction with Fig.10 In some examples, such as in combination with Fig. 8A and Figure 8B As depicted, server 1102 may be an RF source, and / or server 1102 and RFID reader 1104 may be the same entity (eg, an FD device capable of accessing a database that provides the location of an RFID tag based on its tag ID).

[0124] At 1108, the first RFID tag 1106 (and other RFID tags in the set of RFID tags) may send an indication (which may also be referred to as a tag report) to the RFID reader 1104 indicating at least one of: a motion detection indication capability, a location change indication, a new location determination capability, location information, updated location information, and / or a metric associated with motion detection (which may also be referred to as a motion detection metric), such as in conjunction with a Fig.10 The indication may be sent in a backscatter signal with an embedded positioning aid payload, such as in conjunction with Figure 7 and Fig. 9 In addition, the indication may also include a specific (location) ID (e.g., a unique tag ID) associated with each RFID tag. For example, the first RFID tag 1106 may include a unique ID corresponding to the first RFID tag 1106 in the indication / tag report.

[0125] As combined Fig.10 As described, in some scenarios, instead of transmitting an indication of whether the location of the RFID tag has changed, the RFID tag may send a motion detection metric obtained via at least one motion detection sensor to the RFID reader. In response, the RFID reader or server may determine whether the location of the RFID tag has changed based on the motion detection metric provided by the RFID tag.

[0126] In one aspect, a motion detection metric that may be included in a backscatter signal from a set of RFID tags may be received by the RFID reader 1104 across a determined time domain window. The motion detection metric may include an amplitude change metric, a received signal strength (RSS) change metric, a phase change metric, a quantized channel Doppler response (e.g., multiple Doppler shifts with relative power for each Doppler shift), or a combination thereof. The motion detection metric may be included in the backscatter signal as a digital payload, or may be embedded / modulated in the backscatter signal. In one example, after the RFID reader 1104 receives the motion detection metric from the set of RFID tags, the RFID reader 1104 may evaluate the motion of the set of RFID tags (e.g., determine whether the positioning of the RFID has changed based on the corresponding motion detection metric of the RFID). In another example, the RFID reader 1104 may send / forward the motion detection metric received from the set of RFID tags to the server 1102, and the server 1102 may evaluate the motion of the set of RFID tags. In other examples, based on the motion detection metric / measurement, the RFID tag may determine by itself whether there is motion, such as based on measuring a reference signal from a transmitter. For example, an RFID tag may determine whether its position relative to a transmitter has changed based on periodically measuring a reference signal sent from the transmitter (e.g., the RFID tag's position may change if the received power, direction, and / or angle of the reference signal has changed).

[0127] At 1110, after the RFID reader 1104 receives the indication from the set of RFID tags, the RFID reader 1104 may select / prioritize multiple RFID tags from the set of RFID tags for use in the UE positioning session, such as based on their capabilities (e.g., obtained from their indications / tag reports), such as in combination with Fig.10 For example, the RFID reader 1104 may select the first RFID tag 1106 if the first RFID tag 1106 indicates that it has not moved or if the first RFID tag 1106 indicates its new location after a location change.

[0128] At 1112, after determining a plurality of RFID tags to be used for the UE positioning session, the RFID reader 1104 may perform positioning measurements for the selected RFID tags, such as measuring RTT, ToA, and / or AoA of backscattered signals from the plurality of RFID tags.

[0129] At 1114, for network-based positioning (e.g., the server 1102 determines the location of the RFID reader 1104), the RFID reader 1104 may be configured to send the IDs of the plurality of RFID tags, the detected payload / backscatter signals embedded with information received from the plurality of RFID tags, and / or positioning measurements thereof to the server 1102. Then, at 1116, based on the IDs of the RFID tags, the information in the payload / backscatter signals, and / or the positioning measurements from the RFID reader 1104, the server 1102 may calculate / determine the positioning of the RFID reader 1104 (or the relative positioning of the RFID reader 1104 with respect to one or more RFID tags), and the server 1102 may indicate to the RFID reader 1104 the positioning / relative positioning of the RFID reader 1104.

[0130] On the other hand, for UE-based positioning (e.g., the RFID reader 1104 determines its own position), at 1114, the RFID reader 1104 may simply send the IDs collected from the plurality of RFID tags (which may include the first RFID tag 1106) to the server 1102. Then, at 1116, in response to the IDs of the plurality of RFID tags, the server 1102 may indicate the positions of the plurality of RFID tags to the RFID reader 1104. Based on the positions of the plurality of RFID tags, information in the payload / backscatter signals received from the plurality of RFID tags, and / or positioning measurements performed by the RFID reader 1104, the RFID reader 1104 may calculate / determine its position or its position relative to one or more RFID tags.

[0131] In one example, the server 1102 may be configured to store the location of the RFID reader 1104 or the RFID tag in a database. Subsequently, the stored location of the RFID reader 1104 or the RFID tag may be used to determine a second location of the RFID reader 1104 or at least one other IoT device at a subsequent time (e.g., after a certain period of time or after the RFID reader 1104 moves).

[0132] In another example, the RFID reader 1104 and the server 1102 may be the same entity. For example, the RFID reader 1104 may be an FD device and may be able to access the locations of multiple RFID tags. Thus, the RFID reader 1104 may determine the locations of multiple RFID tags without communicating with a separate entity. In addition, if the RFID reader 1104 is an FD device, the RFID reader 1104 may also provide incident power or CW to the RFID tag set.

[0133] Fig.121 is a communication flow 1200 illustrating example signaling between a server, an RFID reader, and an RFID tag according to aspects of the present disclosure. The numbers associated with the communication flow 1200 do not specify a particular time order and are used only as a reference to the communication flow 1200.

[0134] In another configuration, as indicated at 1218, the network entity may transmit a request to the set of RFID tags to initiate a binding. Fig.11 The described procedures, such as indicating at least one of the following to an RFID reader (e.g., a UE to be positioned) via an indication or tag report: motion detection indication capability, positioning change indication, new position determination capability, positioning information, updated positioning information, and / or metrics associated with motion detection, etc. The request from the network entity may be embedded in an event signal (e.g., a CW from the server 1102) or in an explicit bit / signal. For example, a specific sequence may be included in the incident signal. In some examples, the request may also include timing information (e.g., a start time for providing an indication) and / or a duration for providing an indication / tag report. Therefore, the RFID tag may send its indication / tag report based on the timing information and / or duration from the server 1102.

[0135] In another example, the request may also include a zone ID, an ID associated with one or more RFID tags (which may be referred to as a tag ID), and / or a location ID. In response, an RFID tag associated with the zone ID, the tag ID indicated by the server 1102, and / or the location ID may send an indication to the RFID reader 1104. On the other hand, an RFID tag not associated with the zone ID, the tag ID indicated by the server 1102, and / or the location ID may skip or ignore sending an indication to the RFID reader 1104. Similarly, the network entity (e.g., server 1102) and the RFID reader 1104 may be the same entity (e.g., UE, FD device, etc.).

[0136] Then, at 1208, the RFID tag specified by the request from the server 1102 (which may include the first RFID tag 1106) may send an indication or tag report to the RFID reader 1104 indicating at least one of: a motion detection indication capability, a location change indication, a new location determination capability, location information, updated location information, and / or a metric associated with motion detection, such as in conjunction with the RFID reader 1104. Fig.10 and Fig.11 As described.

[0137] At 1210, after the RFID reader 1104 receives the indication from the set of RFID tags, the RFID reader 1104 may select / prioritize multiple RFID tags from the set of RFID tags to use for the UE positioning session, such as based on their capabilities (e.g., obtained from their indications), such as in conjunction with Fig.10 and Fig.11 as described.

[0138] At 1212, after determining a plurality of RFID tags to be used for the UE positioning session, the RFID reader 1104 may perform positioning measurements for the selected RFID tags, such as measuring the RTT, ToA, and / or AoA of their backscatter signals.

[0139] At 1214, for network-based positioning, the RFID reader 1104 may be configured to send the IDs of the plurality of RFID tags, the detected payload / backscatter signals embedded with information received from the plurality of RFID tags, and / or positioning measurements thereof to the server 1102. Then, at 1216, based on the IDs of the RFID tags, the information in the payload / backscatter signals, and / or the positioning measurements from the RFID reader 1104, the server 1102 may calculate / determine the positioning of the RFID reader 1104 (or the relative positioning of the RFID reader 1104 with respect to one or more RFID tags), and the server 1102 may indicate to the RFID reader 1104 the positioning / relative positioning of the RFID reader 1104.

[0140] On the other hand, for UE-based positioning, at 1214, the RFID reader 1104 may simply send the IDs collected from the plurality of RFID tags (which may include the first RFID tag 1106) to the server 1102. Then, at 1216, in response to the IDs of the plurality of RFID tags, the server 1102 may indicate the locations of the plurality of RFID tags to the RFID reader 1104. Based on the locations of the plurality of RFID tags, information in the payload / backscatter signals received from the plurality of RFID tags, and / or positioning measurements performed by the RFID reader 1104, the RFID reader 1104 may calculate / determine its location or its location relative to one or more RFID tags.

[0141] Fig.13 1 is a communication flow 1300 illustrating example signaling between a server, an RFID reader, and an RFID tag according to aspects of the present disclosure. The numbers associated with the communication flow 1300 do not specify a particular time order and are used only as a reference to the communication flow 1300.

[0142] In another configuration, in addition to the network entity transmitting a request to the RFID tag set to initiate the binding Fig.11 Described procedures (such as in Fig.13 1318 shows and combines Fig.12 In addition to the above (described at 1218), the network entity may also send a location request (or information message) to the RFID reader to notify the RFID reader of the backscattered signals that can be read by the RFID reader, such as shown at 1302. The location request or information message may also include time, frequency, and / or sequence information associated with the indications sent from each RFID reader.

[0143] Then, at 1308, the RFID tag specified by the request from the server 1102 (which may include the first RFID tag 1106) may send an indication or tag report to the RFID reader 1104 indicating at least one of: motion detection indication capability, location change indication, new location determination capability, location information, updated location information, and / or metrics associated with motion detection, such as in conjunction with the RFID reader 1104. Figures 10 to 12 as described.

[0144] At 1310, based on the location request from the server and / or the indication from the set of RFID tags, the RFID reader 1104 may select / prioritize a plurality of RFID tags from the set of RFID tags for use in the UE positioning session, such as based on their capabilities (e.g., obtained from their indications), such as in conjunction with Figures 10 to 12 as described.

[0145] At 1312, after determining a plurality of RFID tags to be used for the UE positioning session, the RFID reader 1104 may perform positioning measurements for the selected RFID tags, such as measuring the RTT, ToA, and / or AoA of their backscatter signals.

[0146] At 1314, for network-based positioning, the RFID reader 1104 may be configured to send the IDs of the plurality of RFID tags, the detected payload / backscatter signals embedded with information received from the plurality of RFID tags, and / or positioning measurements thereof to the server 1102. Then, at 1316, based on the IDs of the RFID tags, the information in the payload / backscatter signals, and / or the positioning measurements from the RFID reader 1104, the server 1102 may calculate / determine the positioning of the RFID reader 1104 (or the relative positioning of the RFID reader 1104 with respect to one or more RFID tags), and the server 1102 may indicate to the RFID reader 1104 the positioning / relative positioning of the RFID reader 1104.

[0147] On the other hand, for UE-based positioning, at 1314, the RFID reader 1104 may send only the IDs collected from the plurality of RFID tags (which may include the first RFID tag 1106) to the server 1102. Then, at 1316, in response to the IDs of the plurality of RFID tags, the server 1102 may indicate the locations of the plurality of RFID tags to the RFID reader 1104. Based on the locations of the plurality of RFID tags, information in the payload / backscatter signals received from the plurality of RFID tags, and / or positioning measurements performed by the RFID reader 1104, the RFID reader 1104 may calculate / determine its location or its location relative to one or more RFID tags.

[0148] In another aspect of the present disclosure, other types of IoT devices may also be used for UE positioning, such as semi-passive IoT (e.g., RFID tags that have batteries and can be activated almost all of the time but may not actively transmit) and / or semi-active IoT (e.g., RFID tags with amplification capabilities and / or active RF components that can improve the quality of reading / writing). Therefore, different types of IoT devices may be associated with different antenna configurations (or have different numbers of antennas), and / or have different processing / measurement capabilities (e.g., positioning information processing capabilities may be associated with positioning accuracy). Therefore, an RFID reader may be configured to distinguish one RFID tag type from another RFID tag type, so that the RFID reader may select / prioritize an RFID tag for UE positioning based on the type of the RFID tag or based on the hardware specifications of the RFID tag.

[0149] In one example, a positioning measurement rank that can be used as an indication of measurement accuracy can be assigned to the IoT device based on the type of IoT device. In one example, the positioning measurement rank can refer to the rank assigned to these different types of wireless devices based at least in part on the capabilities, types or categories of different types of wireless devices related to positioning measurements. For example, a first positioning measurement rank can be assigned to a passive IoT device, a second positioning measurement rank can be assigned to a semi-passive IoT device, and a third positioning measurement rank can be assigned to a semi-active IoT device, etc. In another example, the positioning measurement rank can be assigned to an IoT device based on the ability of the receiver of the IoT device to process positioning information / reference signals. For example, a higher positioning measurement rank can be assigned to an IoT device with a better ability to process positioning information and / or reference signals (e.g., receiving and measuring reference signals), and a lower positioning measurement rank can be assigned to an IoT device that cannot process positioning information and / or reference signals at a specific threshold (e.g., within a specific time period and / or with a specific accuracy). In another example, a positioning measurement rank can be assigned to an IoT device based on the current energy state of the IoT device and / or the energy state during processing positioning information and / or reference signals. For example, IoT devices with better energy status (e.g., fast charging, with battery, etc.) may be given a higher positioning measurement rank, while IoT devices with poor energy status (e.g., slow charging, no battery, etc.) may be given a lower positioning measurement rank.

[0150] The location measurement rank associated with each IoT device (e.g., RFID tag) may be determined, for example, via a backscatter signal from the RFID tag (e.g., via a combination of Figures 11 to 13 The RFID reader may be indicated to the RFID reader based on the indication / tag report described in 1108, 1208, and 1308 of the RFID reader 1108 or a backscatter signal from a network entity (e.g., via an RFID tag / tag ID report or based on an indication of an RFID tag category associated with the type of RFID tag and / or the receiver's ability to process positioning information / reference signals, etc.). Based on the positioning measurement rank associated with each IoT device, an RFID reader (e.g., RFID reader 1104) or a network entity (e.g., server 1102) may select / prioritize a set of RFID tags for performing positioning of the UE based on the corresponding positioning measurement ranks of the RFID tags.

[0151] In another aspect of the present disclosure, different ranks of IoT devices may be configured to send different types of indications or tag reports based on the positioning measurement rank associated with each IoT device. In other words, the type of indication or tag report from the RFID tag may depend on the positioning measurement rank of the RFID tag. For example, an IoT device with a better positioning measurement rank may be designated to send more information in an indication / report or more frequently, while an IoT device with a lower positioning measurement rank may be designated to send less information in an indication / report or less frequently than an IoT device with a higher positioning measurement rank.

[0152] In another aspect of the present disclosure, an RFID reader (e.g., RFID reader 1104) may be configured to collect information from different RFID tags. For example, an RFID reader may request a set of RFID tags to send its capability report to the RFID reader. Based on the capability reports received from the set of RFID tags, the RFID reader may discard some of them (e.g., those that the RFID reader determines are not suitable for UE positioning) before forwarding the tag IDs and / or collected information of the RFID tags to a network entity or positioning server (e.g., server 1102). For example, the capability report may include a positioning measurement rank or RFID tag category associated with each RFID tag. Therefore, the RFID reader may select or remove an RFID tag from a UE positioning session based on the corresponding positioning measurement rank or RFID tag category of the RFID tag.

[0153] In another aspect of the present disclosure, a network entity (e.g., server 1102, LMF, location server, or base station) may configure an RFID reader (e.g., UE) with a positioning measurement rank (and also prioritization) for each RFID tag or each tag ID. For example, the base station may indicate the positioning measurement rank of each RFID and its priority to the RFID reader. Then, based on the positioning measurement rank and its priority associated with the RFID tag set, the RFID reader may perform prioritization for the RFID tag set. For example, the RFID reader may be configured to select the top five RFID tags with the highest priority and / or positioning measurement rank from the RFID tag set for the UE positioning session, and discard other RFID tags that are not selected for the UE positioning session. In another example, if the network entity or RFID reader is able to determine which RFID tags are closer to the RFID reader (e.g., based on the latest positioning information of the RFID tags available at the server), the network entity may also configure the RFID reader to apply prioritization for the RFID tag set based on the distance of the RFID tag to the RFID reader. For example, the RFID reader may be configured to select the ten RFID tags closest to the RFID reader from the RFID tag set for the UE positioning session, and discard other RFID tags that are not selected.

[0154] In one example, the RFID reader may be able to calculate how far away the RFID tag is from the RFID reader based on capability reports / indications from the RFID tag and / or based on RSRP / AoA measurements of the RFID tag (e.g., measurements of backscattered signals from the RFID tag). The RFID reader may then obtain a rough location of the RFID and identify which frequency, time, and / or power level is most appropriate for a UE positioning session or may occur for a UE positioning session, and the RFID reader may accordingly perform a prioritized search for a set of RFID tags (e.g., searching for RFID tags that are appropriate for the identified frequency, time, and / or power level).

[0155] After the RFID reader receives responses (e.g., indications or reports) from multiple RFID tags, the RFID reader may perform additional or narrower searches to determine which of the responding RFID tags are close to the RFID reader. The additional or narrower searches may enable the RFID reader to more accurately determine the location of the RFID tag to be used to locate the RFID reader itself and / or the most appropriate RFID tag. In addition, knowing the distance between the RFID tag and the RFID reader may also help the RFID reader read information from the RFID tag, transmit information to the RFID tag, and / or configure the RFID tag.

[0156] As combined Figures 11 to 13 As described, in some scenarios, instead of a network entity (e.g., a location server, a base station, etc.) triggering a set of RFID tags to assist a UE positioning session (e.g., sending a tag report / indication), an RFID reader (e.g., a UE) may also be configured to trigger a set of RFID tags, such as by sending a signal (e.g., a CW) with a specified sequence or cryptographic key to the set of RFID tags. For example, a network entity (e.g., a server 1102) may use RRC signaling, MAC-CE, or a secure channel to signal an RFID reader (e.g., an RFID reader 1104) a cryptographic key for triggering RFID tags on a specific zone ID or for triggering RFID tags that are close to the RFID reader (e.g., based on a history of positioning information).

[0157] In one example, the cryptographic key may be configured to be RFID tag specific (e.g., each RFID tag is associated with a cryptographic key), and the cryptographic key may be provided by a network entity or pre-configured at an RFID reader. The cryptographic key may be an RFID tag access password (e.g., for accessing an RFID tag), a kill password (e.g., for disabling an RFID tag), or a combination password (e.g., having multiple purposes). In another example, the cryptographic key may also be based on a hardware ID associated with an RFID (e.g., may be a permanent unique ID of an RFID tag).

[0158] After the RFID tag receives signaling with the corresponding cryptographic key from the RFID reader, the RFID tag may respond in a pre-configured manner until it is reconfigured by the network entity or the RFID reader. For example, the RFID tag may send an indication / tag report to the RFID reader based on the correct cryptographic key, refrain from sending any indication / tag report to the RFID reader based on an incorrect cryptographic key, or apply an updated configuration from the RFID reader based on the cryptographic key associated with the reconfiguration of the RFID tag, etc.

[0159] In another example, if the RFID tag is in a coverage gap, the cryptographic key can also assist in locating the RFID reader. For example, since the RFID tags at a particular location or area can be associated with the same cryptographic key, the RFID reader can activate the RFID tags at different locations or areas based on the corresponding cryptographic key.

[0160] In another example, resources (e.g., frequency resources) to be used by the RFID tag to send indication / tag reports may be pre-configured for the RFID tag, and the RFID reader (e.g., requesting UE) may configure the RFID tag with timing (e.g., start time) and / or duration for sending indication / tag reports.

[0161] In another aspect of the present disclosure, the RFID tag may be configured to announce its ID (e.g., tag ID), wherein the ID may be associated with or connected to a password in a database set. The ID may be permanent and may be used by a network entity or a trusted device (e.g., a trusted RFID reader) to locate the corresponding cryptographic key associated with the RFID tag through a database set. For example, an authentication device may use the corresponding ID of the RFID tag to locate the cryptographic key associated with the RFID tag in the database set. Then, the RFID reader may transmit some commands / queries (or write tags) to the RFID tag to start the process of reading information from the RFID tag using the cryptographic key. In some examples, in order to avoid always keeping a shared ID, the RFID tag and the latest RFID reader (e.g., a base station or UE) may agree to a new RNTI or temporary ID, wherein the new RNTI or temporary ID may be configured to expire when there is a change in the location of the RFID tag or when a timer associated with the RFID tag expires. Then, a new or updated ID may be requested for the RFID tag. In addition, a new RNTI or temporary ID may also be used to scramble data to or from the RFID tag. If the RFID tag is semi-active, the RFID tag may also be configured to transmit an ID expiration indication to the RFID reader, such as via a location change indication or a tag report.

[0162] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 404, 1002; RFID reader 604, 1104; second device 706, 806; apparatus 1504). The method may enable a UE (e.g., an RFID reader) to determine its location based on a set of IoT devices with known locations.

[0163] At 1402, the UE may receive information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device in the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether a location of the corresponding IoT device has changed, wherein each of the plurality of IoT devices is associated with a known location, such as in conjunction with Figures 10 to 13 For example, in Fig.11 At 1108, the RFID reader 1104 may receive information from the RFID tag set, wherein the information includes an ID of a corresponding RFID tag in the RFID tag set and a location change indication for the corresponding RFID tag. The information may be received by, for example Fig.15 The RFID reading component 198, cellular baseband processor 1524 and / or transceiver 1522 of the device 1504 are executed.

[0164] At 1404, the UE may obtain the location of one or more of the UE or at least one other IoT device based on information received from a plurality of IoT devices including an ID of the corresponding IoT device and a location change indication for the corresponding IoT device, such as in conjunction with Figures 10 to 13 For example, in Fig.11 At 1116, the RFID reader 1104 may obtain its location or the location of the RFID tag selected for the UE location session from the server 1102. The location of one or more of the UE or at least one other IoT device may be obtained by, for example Fig.15 The RFID reading component 198, cellular baseband processor 1524 and / or transceiver 1522 of the device 1504 are executed.

[0165] In one example, the UE may send the information to a network entity, wherein obtaining the position of the UE may include receiving the position of the UE from the network entity.

[0166] In another example, obtaining the location of one or more of the UE or the at least one other IoT device may include: calculating a first relative location of the UE relative to each of the multiple IoT devices, or calculating a second relative location of the at least one other IoT device relative to the UE. In such an example, if the location of the IoT device has changed, the UE may refrain from including the IoT device in the multiple IoT devices in the calculation. In such an example, the UE may receive the location change indication from the IoT device in the multiple IoT devices via the information, and the UE may receive the updated location of the IoT device.

[0167] In another example, the UE may receive a location request from a network entity indicating that the plurality of IoT devices may be used to obtain the location of one or more of the UE or the at least one other IoT device, and the UE may monitor the information sent from the plurality of IoT devices based on the location request. In such examples, the location request includes at least one of: time resources, frequency resources, or sequences associated with the plurality of IoT devices.

[0168] In another example, the positioning change indication corresponds to at least one motion detection metric associated with the corresponding IoT device, and the UE may determine whether the positioning of the corresponding IoT device has changed based on the at least one motion detection metric.

[0169] In another example, the UE may send at least one signal to the plurality of IoT devices before receiving the information from the plurality of IoT devices, wherein the information is received in a format derived based on the at least one signal.

[0170] In another example, each of the multiple IoT devices is associated with a positioning measurement rank, and the UE may prioritize the information received from a first IoT device associated with a first positioning measurement rank among the multiple IoT devices, or the UE may deprioritize or exclude the information received from a second IoT device associated with a second positioning measurement rank among the multiple IoT devices, wherein the first positioning measurement rank is higher than the second positioning measurement rank. In such examples, the positioning measurement rank is based on at least one of: IoT device type, IoT device capability, current energy state of the corresponding IoT device, or energy state of the corresponding IoT device during processing. In such examples, the UE may send the positioning measurement rank associated with the multiple IoT devices to a network entity, or receive the positioning measurement rank associated with the multiple IoT devices from the network entity. In such examples, the UE may determine the positioning measurement rank associated with the multiple IoT devices based on one or more measurements associated with the multiple IoT devices.

[0171] In another example, the UE may receive at least one cryptographic key associated with the plurality of IoT devices, and the UE may trigger the plurality of IoT devices to send the information based on the at least one cryptographic key.

[0172] Fig.151500 is a diagram illustrating an example of a hardware implementation for an apparatus 1504. The apparatus 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., a cellular RF transceiver). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the apparatus 1504 may also include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or communicate using an antenna 1580. The cellular baseband processor 1524 communicates with the UE 104 and / or with the RU associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software causes the cellular baseband processor 1524 / application processor 1506 to perform the various functions described above when executed by the cellular baseband processor 1524 / application processor 1506. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software.The cellular baseband processor 1524 / application processor 1506 may be a component of the UE 350 and may 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 1504 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1524 and / or the application processor 1506, and in another configuration, the device 1504 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1504.

[0173] As discussed above, the RFID reading component 198 is configured to receive information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device in the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed, wherein each of the plurality of IoT devices is associated with a known location. The RFID reading component 198 may also be configured to obtain the location of one or more of the UE or at least one other IoT device based on the information received from the plurality of IoT devices including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device. The RFID reading component 198 may be within the cellular baseband processor 1524, the application processor 1506, or both the cellular baseband processor 1524 and the application processor 1506. The RFID reading component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform 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 1504 may include multiple components configured for various functions. In one configuration, the device 1504 (and specifically the cellular baseband processor 1524 and / or the application processor 1506) includes a component for receiving information from multiple IoT devices, wherein the information includes an ID of a corresponding IoT device in the multiple IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed, wherein each of the multiple IoT devices is associated with a known location. The device 1504 may also include a component for obtaining the location of one or more of the UE or at least one other IoT device based on the information received from the multiple IoT devices including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device.

[0174] In one configuration, the apparatus 1504 may further include means for sending the information to a network entity, wherein obtaining the position of the UE may include receiving the position of the UE from the network entity.

[0175] In another configuration, the means for obtaining the location of one or more of the UE or the at least one other IoT device may include configuring the device 1504 to calculate a first relative location of the UE relative to each of the multiple IoT devices, or to calculate a second relative location of the at least one other IoT device relative to the UE. In such a configuration, the device 1504 may also include a means for refraining from including the IoT device in the multiple IoT devices in the calculation if the location of the IoT device has changed. In such a configuration, the device 1504 may also include a means for receiving an indication of the location change from an IoT device in the multiple IoT devices via the information, and a means for receiving an updated location of the IoT device.

[0176] In another configuration, the apparatus 1504 may also include a component for receiving a location request from a network entity indicating that the plurality of IoT devices may be used to obtain the location of one or more of the UE or the at least one other IoT device, and a component for monitoring the information sent from the plurality of IoT devices based on the location request. In such a configuration, the location request includes at least one of: time resources, frequency resources, or sequences associated with the plurality of IoT devices.

[0177] In another configuration, the location change indication corresponds to at least one motion detection metric associated with the corresponding IoT device, and the apparatus 1504 may further include a component for determining whether the location of the corresponding IoT device has changed based on the at least one motion detection metric.

[0178] In another configuration, the apparatus 1504 may further include means for sending at least one signal to the plurality of IoT devices before receiving the information from the plurality of IoT devices, wherein the information is received in a format derived based on the at least one signal.

[0179] In another configuration, each of the multiple IoT devices is associated with a positioning measurement rank, and the device 1504 may also include a component for prioritizing the information received from a first IoT device associated with a first positioning measurement rank among the multiple IoT devices, or a component for deprioritizing or excluding the information received from a second IoT device associated with a second positioning measurement rank among the multiple IoT devices, wherein the first positioning measurement rank is higher than the second positioning measurement rank. In such a configuration, the positioning measurement rank is based on at least one of the following: IoT device type, IoT device capability, current energy state of the corresponding IoT device, or energy state of the corresponding IoT device during processing. In such a configuration, the device 1504 may also include a component for sending the positioning measurement rank associated with the multiple IoT devices to a network entity, or a component for receiving the positioning measurement rank associated with the multiple IoT devices from the network entity. In such a configuration, the device 1504 may also include a component for determining the positioning measurement rank associated with the multiple IoT devices based on one or more measurements associated with the multiple IoT devices.

[0180] In another configuration, the apparatus 1504 may also include means for receiving at least one cryptographic key associated with the plurality of IoT devices, and means for triggering the plurality of IoT devices to send the information based on the at least one cryptographic key.

[0181] The means may be the RFID reading component 198 of the apparatus 1504 configured to perform the functions recited by the means. As described above, the apparatus 1504 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0182] Fig.16 1600 is a flow chart of a method of wireless communication. The method may be performed by an IoT device (e.g., passive IoT device 502, 602; active IoT device 510; RFID tag 704, 804, 1004, 1006, 1008, 1010, 1012, 1106; apparatus 1704). The method may enable the IoT device to indicate to an RFID reader whether its location has changed and / or indicate its new / updated location if its location has changed.

[0183] At 1602, IoT may receive at least one signal from at least one of a UE or a network entity, such as in conjunction with Figure 6 , Figure 7 , Fig. 8A and Figure 8BFor example, Fig. 8A As shown, RFID tag 804 may receive a signal from first device 802, which may be a UE or a network entity. The reception of at least one signal may be performed by, for example Fig.17 The method may be performed by the backscatter component 197, the cellular baseband processor 1724 and / or the transceiver 1722 of the device 1704.

[0184] At 1604, the IoT may use at least one signal to send information to at least one of the UE or the network entity, wherein the information includes an ID of the IoT device and a location change indication for the IoT device, wherein the location change indication indicates whether the location of the IoT device has changed, wherein the IoT device is associated with a known location, such as in conjunction with Figures 10 to 13 For example, Fig.11 As shown in 1108, the first RFID tag 1106 may send an indication to the RFID reader 1104, wherein the indication may include its tag ID and whether its location has changed. The transmission of information may be performed by, for example Fig.17 The method may be performed by the backscatter component 197, the cellular baseband processor 1724 and / or the transceiver 1722 of the device 1704.

[0185] In one example, the IoT device may determine whether the location of the IoT device has changed based on at least one motion sensor or based on a comparison of the current location of the IoT device with the last read location of the IoT device. In such examples, if the location of the IoT device has changed, the IoT device may send an updated location of the IoT device.

[0186] In another example, the IoT device may receive a request to send the information from at least one of the UE or the network entity, wherein the request includes at least one parameter associated with the information, and the IoT device may send the information based on the request. In such examples, the request includes at least one of: a time resource for sending the information, a frequency resource for sending the information, a sequence for sending the information, timing information for sending the information, a duration for sending the information, or a zone ID, a tag ID, or a location ID to be included in the information.

[0187] In another example, the location change indication corresponds to at least one motion detection metric, and the IoT device may determine the at least one motion detection metric via at least one motion sensor.

[0188] In another example, the information also includes a positioning measurement rank associated with the IoT device.

[0189] In another example, the IoT device may receive a cryptographic key associated with the IoT device from at least one of the UE or the network entity in the at least one signal, and the IoT device may send the information in response to the cryptographic key being authentic.

[0190] In another example, the information is sent in a format derived based on the at least one signal.

[0191] Fig.171700 is a diagram illustrating an example of a hardware implementation for an apparatus 1704. The apparatus 1704 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1704 may include a cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers 1722 (e.g., a cellular RF transceiver). The cellular baseband processor 1724 may include on-chip memory 1724'. In some aspects, the apparatus 1704 may also include one or more subscriber identity module (SIM) cards 1720 and an application processor 1706 coupled to a secure digital (SD) card 1708 and a screen 1710. The application processor 1706 may include on-chip memory 1706'. In some aspects, the device 1704 may also include a Bluetooth module 1712, a WLAN module 1714, an SPS module 1716 (e.g., a GNSS module), one or more sensor modules 1718 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1726, a power source 1730, and / or a camera 1732. The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include their own dedicated antennas and / or utilize an antenna 1780 for communication. The cellular baseband processor 1724 communicates with the UE 104 and / or with the RU associated with the network entity 1702 through the transceiver 1722 via one or more antennas 1780. The cellular baseband processor 1724 and the application processor 1706 may each include a computer-readable medium / memory 1724', 1706', respectively. The additional memory module 1726 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1724', 1706', 1726 may be non-transitory. The cellular baseband processor 1724 and the application processor 1706 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1724 / application processor 1706 to perform the various functions described above when executed by the cellular baseband processor 1724 / application processor 1706. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1724 / application processor 1706 when executing the software.The cellular baseband processor 1724 / application processor 1706 may be a component of the UE 350 and may 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 1704 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1724 and / or the application processor 1706, and in another configuration, the device 1704 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1704.

[0192] As discussed above, the backscatter component 197 is configured to receive at least one signal from at least one of the UE or the network entity. The backscatter component 197 may also be configured to use the at least one signal to send information for at least one of the UE or the network entity, wherein the information includes an ID of the IoT device and a location change indication for the IoT device, wherein the location change indication indicates whether the location of the IoT device has changed, wherein the IoT device is associated with a known location. The backscatter component 197 may be within the cellular baseband processor 1724, the application processor 1706, or both the cellular baseband processor 1724 and the application processor 1706. The backscatter component 197 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. As shown, the device 1704 may include a variety of components configured for various functions. In one configuration, the apparatus 1704 (and specifically the cellular baseband processor 1724 and / or the application processor 1706) includes means for receiving at least one signal from at least one of a UE or a network entity. The apparatus 1704 may also include means for sending information for at least one of the UE or the network entity using the at least one signal, wherein the information includes an ID of the IoT device and a location change indication for the IoT device, wherein the location change indication indicates whether the location of the IoT device has changed, wherein the IoT device is associated with a known location.

[0193] In one configuration, the device 1704 may also include a component for determining whether the location of the IoT device has changed based on at least one motion sensor or based on a comparison of the current location of the IoT device with the last read location of the IoT device. In such a configuration, the device 1704 may also include a component for sending an updated location of the IoT device if the location of the IoT device has changed.

[0194] In another configuration, the apparatus 1704 may also include a component for receiving a request to send the information from at least one of the UE or the network entity, wherein the request includes at least one parameter associated with the information, and the IoT device may send the information based on the request. In such a configuration, the request includes at least one of the following: time resources for sending the information, frequency resources for sending the information, a sequence for sending the information, timing information for sending the information, a duration for sending the information, or a zone ID, tag ID, or location ID to be included in the information.

[0195] In another configuration, the positioning change indication corresponds to at least one motion detection metric, and the apparatus 1704 may further include means for determining the at least one motion detection metric via at least one motion sensor.

[0196] In another configuration, the information also includes a positioning measurement rank associated with the IoT device.

[0197] In another configuration, the apparatus 1704 may further include means for receiving a cryptographic key associated with the IoT device from at least one of the UE or the network entity in the at least one signal, and means for sending the information in response to the cryptographic key being authentic.

[0198] In another configuration, the information is sent in a format derived based on the at least one signal.

[0199] The means may be the backscatter component 197 of the apparatus 1704 configured to perform the functions recited by the means. As described above, the apparatus 1704 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0200] Fig.18 1800 is a flow chart of a method of wireless communication. The method may be performed by a base station (eg, base station 102; server 1102; network entity 1902). The method may enable a base station to determine the location of a UE or a set of IoT devices.

[0201] At 1802, the base station may receive a first indication from the UE to calculate the location of the UE, wherein the first indication is associated with information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device in the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed from an initial location, wherein each of the plurality of IoT devices is associated with a known location, such as in conjunction with Figures 11 to 13 For example, Fig.11 As shown in 1114, the server 1102 may receive IDs of multiple RFID tags, information in payload / backscatter signals, and / or positioning measurements from the RFID reader 1104. Based on the IDs of the RFID tags, information in payload / backscatter signals, and / or positioning measurements from the RFID reader 1104, the server 1102 may calculate / determine the positioning of the RFID reader 1104 (or the relative positioning of the RFID reader 1104 with respect to one or more RFID tags). The receipt of the first indication may be performed by, for example Fig.19 The UE positioning component 199 and / or the transceiver 1946 of the network entity 1902 is executed.

[0202] At 1804, the base station may calculate the location of the UE or at least one other IoT device based on information including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device, such as in combination with Figures 11 to 13 For example, as described in conjunction with Fig.11 As discussed, based on the ID of the RFID tag, information in the payload / backscatter signal, and / or positioning measurements from the RFID reader 1104, the server 1102 may calculate / determine the positioning of the RFID reader 1104 (or the relative positioning of the RFID reader 1104 with respect to one or more RFID tags). The calculation of the positioning of the UE or at least one other IoT device may be performed by, for example Fig.19 The UE positioning component 199 and / or the transceiver 1946 of the network entity 1902 is executed.

[0203] In one example, the base station may send at least one signal to the plurality of IoT devices.

[0204] In another example, the base station may receive a request from the UE to perform a position calculation for the UE, and the base station may send a second indication of the position of the UE to the UE based on the request.

[0205] In another example, the base station may send a positioning measurement rank associated with each of the multiple IoT devices for the UE or the corresponding IoT device.

[0206] In another example, the base station may send a location request for the UE indicating that the multiple IoT devices can be used to calculate the location of the UE, or send a second request for the multiple IoT devices to send the information, wherein the location request or the second request includes at least one parameter associated with the information. In such examples, the base station may determine the multiple IoT devices that can be used to calculate the location of the UE based on crowdsourced information or past UE reports.

[0207] In another example, the base station may send at least one cryptographic key associated with the plurality of IoT devices to the UE.

[0208] In another example, the base station may store the positioning of the UE or the at least one other IoT device in a database, wherein the stored positioning of the UE or the at least one other IoT device is used to determine a second positioning of the UE or the at least one other IoT device at a subsequent time.

[0209] Fig.19 1900 is a diagram illustrating an example of a hardware implementation for a network entity 1902. The network entity 1902 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1902 may include at least one of a CU 1910, a DU 1930, or a RU 1940. For example, depending on the layer functionality handled by the UE positioning component 199, the network entity 1902 may include a CU 1910; both a CU 1910 and a DU 1930; each of the CU 1910, the DU 1930, and the RU 1940; the DU 1930; both a DU 1930 and a RU 1940; or a RU 1940. The CU 1910 may include a CU processor 1912. The CU processor 1912 may include an on-chip memory 1912'. In some aspects, the CU 1910 may also include an additional memory module 1914 and a communication interface 1918. CU1910 communicates with DU 1930 via a midhaul link, such as an F1 interface. DU 1930 may include a DU processor 1932. DU processor 1932 may include on-chip memory 1932'. In some aspects, DU 1930 may also include an additional memory module 1934 and a communication interface 1938. DU 1930 communicates with RU 1940 via a fronthaul link. RU 1940 may include a RU processor 1942. RU processor 1942 may include on-chip memory 1942'. In some aspects, RU 1940 may also include an additional memory module 1944, one or more transceivers 1946, an antenna 1980, and a communication interface 1948. RU 1940 communicates with UE 104. On-chip memory 1912', 1932', 1942' and additional memory modules 1914, 1934, 1944 can each be considered as a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1912, 1932, 1942 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0210] As discussed above, the UE positioning component 199 is configured to receive a first indication from the UE to calculate the positioning of the UE, wherein the first indication is associated with information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device in the plurality of IoT devices and a positioning change indication for the corresponding IoT device, wherein the positioning change indication indicates whether the positioning of the corresponding IoT device has changed from an initial positioning, wherein each of the plurality of IoT devices is associated with a known location. The UE positioning component 199 may also be configured to calculate the positioning of the UE or the at least one other IoT device based on the information including the ID of the corresponding IoT device and the positioning change indication for the corresponding IoT device. The UE positioning component 199 may be within one or more processors of one or more of the CU 1910, the DU 1930, and the RU 1940. The UE positioning component 199 may be one or more hardware components that are 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 so as to be implemented by one or more processors, or some combination of the above. The network entity 1902 may include a variety of components configured for various functions. In one configuration, the network entity 1902 includes a component for receiving a first indication from a UE to calculate a location of the UE, wherein the first indication is associated with information from a plurality of IoT devices, wherein the information includes an ID of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether the location of the corresponding IoT device has changed from an initial location, wherein each of the plurality of IoT devices is associated with a known location. The network entity 1902 may also include a component for calculating the location of the UE or the at least one other IoT device based on the information including the ID of the corresponding IoT device and the location change indication for the corresponding IoT device.

[0211] In one configuration, the network entity 1902 may also include means for sending at least one signal directed to the plurality of IoT devices.

[0212] In another configuration, the network entity 1902 may further include means for receiving a request from the UE to perform a position calculation for the UE, and means for sending a second indication of the position of the UE to the UE based on the request.

[0213] In another configuration, the network entity 1902 may also include means for sending, for the UE or the corresponding IoT device, a positioning measurement rank associated with each of the plurality of IoT devices.

[0214] In another configuration, the network entity 1902 may also include a component for sending a location request for the UE indicating that the multiple IoT devices can be used to calculate the location of the UE, or sending a second request for sending the information for the multiple IoT devices, wherein the location request or the second request includes at least one parameter associated with the information. In such a configuration, the network entity 1902 may also include a component for determining the multiple IoT devices that can be used to calculate the location of the UE based on crowdsourced information or past UE reports.

[0215] In another configuration, the base station may send at least one cryptographic key associated with the plurality of IoT devices to the UE.

[0216] In another configuration, the network entity 1902 may also include a component for storing the positioning of the UE or the at least one other IoT device in a database, wherein the stored positioning of the UE or the at least one other IoT device is used to determine a second positioning of the UE or the at least one other IoT device at a subsequent time.

[0217] The means may be a UE positioning component 199 of the network entity 1902 configured to perform the functions recited by the means. As described above, the network entity 1902 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

[0218] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0219] 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, 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 "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. 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 "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, wherein the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent 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 the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0220] As used herein, the phrase "based on" should not be interpreted as referring 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 interpreted as "based at least on A" unless specifically stated differently.

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

[0222] Aspect 1 is a method for performing wireless communication at a first UE, the method comprising: receiving information from multiple IoT devices, wherein the information includes an ID of a corresponding IoT device among the multiple IoT devices and a positioning change indication for the corresponding IoT device, wherein the positioning change indication indicates whether the positioning of the corresponding IoT device has changed, wherein each of the multiple IoT devices is associated with a known location; and obtaining the positioning of one or more of the UE or at least one other IoT device based on the information received from the multiple IoT devices including the ID of the corresponding IoT device and the positioning change indication for the corresponding IoT device.

[0223] Aspect 2 is a method according to aspect 1, the method further comprising: sending the information to a network entity; wherein obtaining the positioning of the UE comprises: receiving the positioning of the multiple IoT devices from the network entity.

[0224] Aspect 3 is a method according to Aspect 1 or 2, wherein obtaining the positioning of one or more of the UE or the at least one other IoT device includes: calculating a first relative positioning of the UE relative to each of the multiple IoT devices, or calculating a second relative positioning of the at least one other IoT device relative to the UE.

[0225] Aspect 4 is a method according to aspect 3, the method further comprising: if the location of the IoT device has changed, stopping the IoT device from being included in the calculation.

[0226] Aspect 5 is a method according to aspect 3, the method further comprising: receiving the location change indication from an IoT device among the multiple IoT devices via the information; and receiving an updated location of the IoT device.

[0227] Aspect 6 is a method according to any one of Aspects 1 to 5, the method further comprising: receiving a location request from a network entity indicating that the multiple IoT devices can be used to obtain the positioning of one or more of the UE or the at least one other IoT device; and monitoring the information sent from the multiple IoT devices based on the location request.

[0228] Aspect 7 is a method according to aspect 6, wherein the location request includes at least one of the following: time resources, frequency resources, or sequences associated with the plurality of IoT devices.

[0229] Aspect 8 is a method according to any one of Aspects 1 to 7, wherein the positioning change indication corresponds to at least one motion detection metric associated with the corresponding IoT device, and the method further includes: determining whether the positioning of the corresponding IoT device has changed based on the at least one motion detection metric.

[0230] Aspect 9 is a method according to any one of Aspects 1 to 8, the method further comprising: sending at least one signal to the multiple IoT devices before receiving the information from the multiple IoT devices, wherein the information is received in a format derived based on the at least one signal.

[0231] Aspect 10 is a method according to any one of Aspects 1 to 9, wherein each of the multiple IoT devices is associated with a positioning measurement rank, and the method further includes: prioritizing the information received from a first IoT device associated with a first positioning measurement rank among the multiple IoT devices; or deprioritizing or excluding the information received from a second IoT device associated with a second positioning measurement rank among the multiple IoT devices, wherein the first positioning measurement rank is higher than the second positioning measurement rank.

[0232] Aspect 11 is a method according to aspect 10, wherein the positioning measurement rank is based on at least one of the following: IoT device type, IoT device capability, current energy state of the corresponding IoT device, or energy state of the corresponding IoT device during processing.

[0233] Aspect 12 is a method according to aspect 10, the method further comprising: sending the positioning measurement rank associated with the multiple IoT devices to a network entity, or receiving the positioning measurement rank associated with the multiple IoT devices from the network entity.

[0234] Aspect 13 is a method according to aspect 10, the method further comprising: determining the positioning measurement rank associated with the multiple IoT devices based on one or more measurements associated with the multiple IoT devices.

[0235] Aspect 14 is a method according to aspect 12, the method further comprising: receiving at least one cryptographic key associated with the plurality of IoT devices; and triggering the plurality of IoT devices to send the information based on the at least one cryptographic key.

[0236] Aspect 15 is an apparatus for performing wireless communication at a UE, the apparatus 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 1 to 14 based at least in part on information stored in the memory.

[0237] Aspect 16 is the apparatus of aspect 15, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0238] Aspect 17 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 14.

[0239] Aspect 18 is a computer-readable medium (eg, 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 14 .

[0240] Aspect 19 is a method for performing wireless communication at an IoT device, the method comprising: receiving at least one signal from at least one of a UE or a network entity; and using the at least one signal to send information for the UE or at least one of the network entities, wherein the information comprises an ID of the IoT device and a positioning change indication for the IoT device, wherein the positioning change indication indicates whether the positioning of the IoT device has changed, wherein the IoT device is associated with a known location.

[0241] Aspect 20 is a method according to Aspect 19, the method further comprising: determining whether the positioning of the IoT device has changed based on at least one motion sensor or based on a comparison of a current position of the IoT device with a last read position of the IoT device.

[0242] Aspect 21 is a method according to Aspect 20, the method further comprising: if the location of the IoT device has changed, sending the updated location of the IoT device.

[0243] Aspect 22 is a method according to any one of Aspects 19 to 21, the method further comprising: receiving a request to send the information from at least one of the UE or the network entity, wherein the request includes at least one parameter associated with the information; and sending the information based on the request.

[0244] Aspect 23 is a method according to any one of Aspect 22, wherein the request includes at least one of the following: time resources for sending the information, frequency resources for sending the information, a sequence for sending the information, timing information for sending the information, a duration for sending the information, or an area ID, tag ID or location ID to be included in the information.

[0245] Aspect 24 is a method according to any one of aspects 19 to 23, wherein the positioning change indication corresponds to at least one motion detection metric, and the method further includes: determining the at least one motion detection metric via at least one motion sensor.

[0246] Aspect 25 is a method according to any one of aspects 19 to 24, wherein the information also includes a positioning measurement rank associated with the IoT device.

[0247] Aspect 26 is a method according to any one of Aspects 19 to 25, the method further comprising: receiving a cryptographic key associated with the IoT device from at least one of the UE or the network entity in the at least one signal; and sending the information in response to the cryptographic key being authentic.

[0248] Aspect 27 is a method according to any one of aspects 19 to 26, wherein the information is sent in a format derived based on the at least one signal.

[0249] Aspect 28 is an apparatus for wireless communication at an IoT device, the apparatus 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 19 to 27 based at least in part on information stored in the memory.

[0250] Aspect 29 is the apparatus of aspect 28, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0251] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 19 to 27.

[0252] Aspect 31 is a computer-readable medium (eg, 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 19 to 27.

[0253] Aspect 32 is a method for performing wireless communications at a network entity, the method comprising: receiving a first indication from a UE to calculate the positioning of the UE, wherein the first indication is associated with information from multiple IoT devices, wherein the information includes an ID of a corresponding IoT device among the multiple IoT devices and a positioning change indication for the corresponding IoT device, wherein the positioning change indication indicates whether the positioning of the corresponding IoT device has changed from an initial positioning, wherein each of the multiple IoT devices is associated with a known location; and calculating the positioning of the UE or at least one other IoT device based on the information including the ID of the corresponding IoT device and the positioning change indication for the corresponding IoT device.

[0254] Aspect 33 is a method according to aspect 32, the method further comprising: sending at least one signal for the plurality of IoT devices.

[0255] Aspect 34 is a method according to aspect 32 or aspect 33, the method further comprising: receiving a request from the UE to perform position calculation for the UE; and sending a second indication of the positioning of the UE to the UE based on the request.

[0256] Aspect 35 is a method according to any one of aspects 32 to 34, the method further comprising: sending a positioning measurement rank associated with each of the plurality of IoT devices for the UE or the corresponding IoT device.

[0257] Aspect 36 is a method according to any one of aspects 32 to 35, the method further comprising: sending a location request for the UE indicating that the plurality of IoT devices can be used to calculate the location of the UE, or sending a second request for the plurality of IoT devices to send the information, wherein the location request or the second request includes at least one parameter associated with the information;

[0258] Aspect 37 is a method according to aspect 36, the method further comprising: determining the plurality of IoT devices that can be used to calculate the positioning of the UE based on crowdsourced information or past UE reports.

[0259] Aspect 38 is a method according to any one of aspects 32 to 37, the method further comprising: sending at least one cryptographic key associated with the plurality of IoT devices to the UE.

[0260] Aspect 39 is a method according to any one of Aspects 32 to 38, the method further comprising: storing the positioning of the UE or the at least one other IoT device in a database, wherein the stored positioning of the UE or the at least one other IoT device is used to determine a second positioning of the UE or the at least one other IoT device at a subsequent time.

[0261] Aspect 40 is an apparatus for wireless communication at a network entity, the apparatus 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 32 to 39 based at least in part on information stored in the memory.

[0262] Aspect 41 is the apparatus of aspect 40, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0263] Aspect 42 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 32 to 39.

[0264] Aspect 43 is a computer-readable medium (eg, 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 32 to 39.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on first information stored in the memory, the at least one processor configured to: receiving information from a plurality of Internet of Things (IoT) devices, wherein the information includes an identification (ID) of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether a location of the corresponding IoT device has changed, wherein each of the plurality of IoT devices is associated with a known location; and The positioning of one or more of the UE or at least one other IoT device is obtained based on the information received from the plurality of IoT devices including the ID of the corresponding IoT device and the positioning change indication for the corresponding IoT device.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: sending the information to a network entity; In order to obtain the positioning of the UE, the at least one processor is configured to receive the positioning of the plurality of IoT devices from the network entity.

3. The apparatus of claim 1 , wherein to obtain the positioning of one or more of the UE or the at least one other IoT device, the at least one processor is configured to: Calculate a first relative position of the UE relative to each of the plurality of IoT devices, or A second relative positioning of the at least one other IoT device relative to the UE is calculated.

4. The apparatus of claim 3, wherein the at least one processor is further configured to: If the location of the IoT device has changed, refraining from including an IoT device among the plurality of IoT devices in the calculation.

5. The apparatus of claim 3, wherein the at least one processor is further configured to: receiving the location change indication from an IoT device among the plurality of IoT devices via the information; and Receive an updated location of the IoT device.

6. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a location request from a network entity indicating that the plurality of IoT devices are available to obtain the location of one or more of the UE or the at least one other IoT device; and The information sent from the plurality of IoT devices is monitored based on the location request. 7 . The apparatus of claim 6 , wherein the location request comprises at least one of: a time resource, a frequency resource, or a sequence associated with the plurality of IoT devices.

8. The apparatus of claim 1 , wherein the location change indication corresponds to at least one motion detection metric associated with the corresponding IoT device, and the at least one processor is further configured to: A determination is made based on the at least one motion detection metric whether the location of the corresponding IoT device has changed.

9. The apparatus of claim 1 , wherein the at least one processor is further configured to: At least one signal is sent to the plurality of IoT devices before receiving the information from the plurality of IoT devices, wherein in order to receive the information from the plurality of IoT devices, the at least one processor is configured to receive the information in a format derived based on the at least one signal.

10. The apparatus of claim 1, wherein each of the plurality of IoT devices is associated with a positioning measurement rank, and the at least one processor is further configured to: Prioritizing the information received from a first IoT device associated with a first positioning measurement rank among the plurality of IoT devices; or The information received from a second IoT device associated with a second positioning measurement rank among the plurality of IoT devices is deprioritized or excluded, wherein the first positioning measurement rank is higher than the second positioning measurement rank.

11. The apparatus of claim 10, wherein the positioning measurement rank is based on at least one of: IoT device types, IoT device capabilities, The current energy state of the corresponding IoT device, or The energy state of the corresponding IoT device during processing.

12. The apparatus of claim 10, wherein the at least one processor is further configured to: sending the positioning measurement ranks associated with the plurality of IoT devices to a network entity, or The positioning measurement rank associated with the plurality of IoT devices is received from the network entity.

13. The apparatus of claim 10, wherein the at least one processor is further configured to: The positioning measurement rank associated with the plurality of IoT devices is determined based on one or more measurements associated with the plurality of IoT devices.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving at least one cryptographic key associated with the plurality of IoT devices; and The plurality of IoT devices are triggered to send the information based on the at least one cryptographic key.

15. A method of wireless communication at a user equipment (UE), the method comprising: receiving information from a plurality of Internet of Things (IoT) devices, wherein the information includes an identification (ID) of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether a location of the corresponding IoT device has changed, wherein each of the plurality of IoT devices is associated with a known location; and The positioning of one or more of the UE or at least one other IoT device is obtained based on the information received from the plurality of IoT devices including the ID of the corresponding IoT device and the positioning change indication for the corresponding IoT device.

16. An apparatus for wireless communication at an Internet of Things (IoT) device, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on first information stored in the memory, the at least one processor configured to: receiving at least one signal from at least one of a user equipment (UE) or a network entity; and The at least one signal is used to send information to at least one of the UE or the network entity, wherein the information includes an identification (ID) of the IoT device and a location change indication for the IoT device, wherein the location change indication indicates whether the location of the IoT device has changed, wherein the IoT device is associated with a known location.

17. The apparatus of claim 16, wherein the at least one processor is further configured to: Determining whether the location of the IoT device has changed is based on at least one motion sensor or based on a comparison of a current location of the IoT device with a last read location of the IoT device.

18. The apparatus of claim 17, wherein the at least one processor is further configured to: If the location of the IoT device has changed, then sending the updated location of the IoT device.

19. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving, from at least one of the UE or the network entity, a request to send the information, wherein the request includes at least one parameter associated with the information; and The information is sent based on the request.

20. The apparatus of claim 19, wherein the request comprises at least one of: The time resources used to send said information, frequency resources used to send said information, The sequence used to send said information, timing information for sending said information, the duration used to send said information, or The zone ID, tag ID or location ID will be included in the information.

21. The apparatus of claim 16, wherein the location change indication corresponds to at least one motion detection metric, and the at least one processor is further configured to: The at least one motion detection metric is determined via at least one motion sensor.

22. The apparatus of claim 16, wherein the information further comprises a positioning measurement rank associated with the IoT device.

23. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving, in the at least one signal, a cryptographic key associated with the IoT device from at least one of the UE or the network entity; and The information is sent in response to the cryptographic key being authentic.

24. The apparatus of claim 16, wherein to send the information for at least one of the UE or the network entity using the at least one signal, the at least one processor is configured to send the information in a format derived based on the at least one signal.

25. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on first information stored in the memory, the at least one processor configured to: receiving a first indication from a user equipment (UE) to calculate a position of the UE, wherein the first indication is associated with information from a plurality of Internet of Things (IoT) devices, wherein the information includes an identification (ID) of a corresponding IoT device among the plurality of IoT devices and a location change indication for the corresponding IoT device, wherein the location change indication indicates whether a location of the corresponding IoT device has changed from an initial location, wherein each of the plurality of IoT devices is associated with a known location; and The positioning of the UE or the at least one other IoT device is calculated based on the information including the ID of the corresponding IoT device and the positioning change indication for the corresponding IoT device.

26. The apparatus of claim 25, wherein the at least one processor is further configured to: At least one signal directed to the plurality of IoT devices is sent.

27. The apparatus of claim 25, wherein the at least one processor is further configured to: receiving, from the UE, a request to perform a position calculation for the UE; and A second indication of the positioning of the UE is sent to the UE based on the request.

28. The apparatus of claim 25, wherein the at least one processor is further configured to: A positioning measurement rank associated with each of the plurality of IoT devices is sent for the UE or the corresponding IoT device.

29. The apparatus of claim 25, wherein the at least one processor is further configured to: Sending a location request for the UE indicating that the plurality of IoT devices can be used to calculate the location of the UE, or sending a second request for the plurality of IoT devices to send the information, wherein the location request or the second request includes at least one parameter associated with the information; and The plurality of IoT devices that can be used to calculate the positioning of the UE are determined based on crowd-sourced information or past UE reports.

30. The apparatus of claim 25, wherein the at least one processor is further configured to: At least one cryptographic key associated with the plurality of IoT devices is sent to the UE.

Images