Map-assisted node selection for localization and radio frequency sensing

Abstract

In an aspect, a first network node may obtain first map information associated with at least one of a positioning session or an RF sensing session. The first network node may select at least one of a first set of TRPs or at least one second network node for at least one of the positioning session or the RF sensing session based on the map information. The first network node may configure at least one of the first set of TRPs or the at least one second network node for at least one of the positioning session or the RF sensing session.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 18 / 169,778, filed on February 15, 2023, entitled “MAP-AIDED NODE SELECTION FOR POSITIONING AND RADIO FREQUENCY SENSING,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to positioning systems, and more particularly to positioning systems related to map information. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. 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 continued mobile broadband evolution promulgated by the 3rd 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. 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] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a first network node are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to: obtain first map information associated with at least one of a positioning session or a radio frequency (RF) sensing session; select a first set of transmit receive points (TRPs) or at least one of at least one second network node for at least one of the positioning session or the RF sensing session based on the first map information; and configure the first set of TRPs or at least one of the at least one second network node for at least one of the positioning session or the RF sensing session.

[0008] In another aspect of the present disclosure, a method, computer-readable medium, and apparatus at a first network node are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to: obtain map information associated with at least one of a positioning session or a radio frequency (RF) sensing session for a UE; and send an indication of a first set of TRPs or at least one of the at least one network node for at least one of the positioning session or the RF sensing session based on the map information.

[0009] To achieve the foregoing and related ends, one or more aspects may 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 illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0017] Figure 5 is a diagram illustrating an environment in which an uplink or downlink positioning or RF sensing session is performed according to various aspects of the present disclosure.

[0018] Figure 6 is a diagram illustrating an environment in which a sidelink-based positioning or a sidelink RF sensing session is performed according to various aspects of the present disclosure.

[0019] Figure 7A Depicted is a call flow diagram illustrating a method of wireless communication in accordance with various aspects of the present disclosure.

[0020] Figure 7B Depicted is a call flow diagram illustrating a method of wireless communication in accordance with various aspects of the present disclosure.

[0021] Figure 8 is a flow chart illustrating a method of wireless communication at a wireless entity according to various aspects of the present disclosure.

[0022] Figure 9 is a flow chart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure.

[0023] Figure 10 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0024] Figure 11 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0025] Figure 12 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0026] Figure 13 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0027] Figure 14is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0028] Various aspects relate generally to positioning systems. Some aspects relate more specifically to positioning or RF sensing utilizing map information. In some examples, a coordinator node may obtain map information about the environment of a target entity for which a positioning or sensing session is to be performed. Based at least on the map information, the coordinator node may select and / or configure a set of transmit receive points (TRPs) or anchor nodes to be used or not to be used for the positioning or sensing session. For example, the coordinator node may activate or deactivate the transmission or reception of reference signals (e.g., positioning reference signals (PRS)) from the set of TRPs or anchor nodes based on the configuration. The coordinator node may select and / or configure a set of TRPs for uplink or downlink based positioning or sensing, and may select and / or configure anchor nodes for sidelink based positioning or sensing. In some aspects, a target UE may provide an indication of a set of TRPs or anchor nodes to be used for its positioning or sensing session based on its map information.

[0029] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. By utilizing map information associated with the specific environment in which the target entity is located, the coordinator node may determine TRPs or anchor nodes that do not have a direct line of sight to the target entity due to obstacles in the environment indicated by the map information. The coordinator node may disable the transmission or reception of reference signals from such TRPs or anchor nodes. By disabling the transmission or reception of reference signals from such TRPs or anchor nodes, such TRPs or anchor nodes (and target entities configured to detect such reference signals) may save computing resources (e.g., processing cycles, memory, power, etc.). The coordinator node may also enable the transmission or reception of reference signals from TRPs or anchor nodes that have a direct line of sight to the target entity. By enabling the transmission or reception of reference signals from such TRPs or anchor nodes, the positioning of the target entity may be determined more accurately.

[0030] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, these concepts may 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.

[0031] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses 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 can 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.

[0032] 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. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gating logic, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout this 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 an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

[0033] Thus, in one or more example aspects, specific implementations and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of 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.

[0034] Although various aspects, specific implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, specific implementations and / or use cases may be produced in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases may be produced via integrated chip 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, devices that enable artificial intelligence (AI), 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 within the scope of chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregation, distribution or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment in conjunction 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 both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0035] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways using various components or parts. 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) that perform base station functionality can be implemented in a converged 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 a converged base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

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

[0037] 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 (a 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)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality 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.

[0038] Figure 1 FIG1 is a diagram 100 illustrating an example of a wireless communication system and 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, which 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 the 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.

[0039] 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 transmit 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 transmit 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 transmit signals to one or more of the other units via a wireless transmission medium.

[0040] In some aspects, the 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 the CU 110. The 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, the 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-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0041] The 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, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0042] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (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 a functional split (such as a lower layer functional split). 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 implementations, both real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0043] The SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as 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 the 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 implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can 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 .

[0044] The non-RT RIC 115 may be configured to include logic that enables 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 in communication with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., 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.

[0045] In some implementations, to generate AI / ML models 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 non-network data sources or from network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in 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).

[0046] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, DU 130, and RU 140 (each component is indicated by a dotted line to indicate that each component may or may not be included in the base station 102). 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 that includes 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 called a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmissions from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmissions from RU 140 to UE 104. The communication link may utilize multiple-input, multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. Base station 102 / UE 104 may utilize spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) for each carrier allocated in a carrier aggregation for transmission in each direction for a total of up to Yx MHz (x component carriers). 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).

[0047] Some UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be accomplished through various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0048] 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 the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0049] 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 referred to (interchangeably) 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 it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0051] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like 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" or the like 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.

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

[0053] 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 TRP, a network node, a network entity, a network equipment, or some other suitable terminology. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0054] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 168 are exemplified as including a gateway mobile location center (GMLC) 165, a location management function (LMF) 166, and a sensing management function (SnMF) 167. 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 following: the GMLC 165, the LMF 166, the SnMF 167, a Positioning Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), etc. The GMLC 165, the LMF 166, and the SnMF 167 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The SnMF 167 coordinates the RF sensing session of the target entity, for example, by configuring a node (e.g., a TRP or UE) for the RF sensing session. The SnMF 167 may also receive measurements and / or additional information from the node and determine a sensing result (e.g., the location of the target entity) based on the measurements and / or additional information. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity calculation based on these measurements. The signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104.The measured signals may be based on one or more of a satellite positioning system (SPS) 170 (e.g., a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning 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 other systems / signals / sensors.

[0055] Examples of UE 104 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0056] Reference again Figure 1In certain aspects, the UE 104 may have a map-assisted positioning / sensing component 198 that may be configured to: obtain first map information associated with at least one of a positioning session or an RF sensing session; select a first set of TRPs or at least one second network node for at least one of the positioning session or the RF sensing session based on the first map information; and configure the first set of TRPs or at least one second network node for at least one of the positioning session or the RF sensing session. In certain aspects, the map-assisted positioning / sensing component 198 may be configured to: obtain map information associated with at least one of the positioning session or the RF sensing session for the UE; and send an indication of the first set of TRPs or at least one of the at least one network node for at least one of the positioning session or the RF sensing session based on the map information. In certain aspects, the LMF 166 and / or the SnMF 167 may have a map-assisted positioning / sensing component 199 that may be configured to: obtain first map information associated with at least one of a positioning session or an RF sensing session; select a first set of TRPs or at least one of at least one second network nodes for at least one of the positioning session or the RF sensing session based on the first map information; and configure the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session.

[0057] 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 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 2CIn 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 can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via the received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0058] Figures 2A to 2D The frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, 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 symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0059]

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

[0061] 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 μ time slots / 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. Symbol length / duration is inversely related to subcarrier spacing. Figures 2A to 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 approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

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

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

[0064] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of a RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring opportunity on the 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), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and 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.

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

[0066] Figure 2DExamples 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 a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (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.

[0067] Figure 3 3 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 (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (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 transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0068] 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 transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles the mapping onto signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-order phase-shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined 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. The channel estimates may be derived based on a reference signal and / or channel condition feedback transmitted 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 using a corresponding spatial stream for transmission.

[0069] At the UE 350, each receiver 354Rx receives a signal via 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 streams 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, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted 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 a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0070] 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 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 an ACK and / or NACK protocol to support HARQ operations.

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

[0072] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback transmitted 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.

[0073] 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 corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0074] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and 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.

[0075] 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 Various aspects related to the map-assisted positioning / sensing component 198.

[0076] Figure 4 FIG4 is a diagram illustrating an example of UE positioning based on reference signal measurement. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX Receive DL Positioning Reference Signal (PRS) (DL-PRS) 410. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. The UE 404 may receive the DL-PRS 410 before transmitting the UL-SRS 412, or may transmit the UL-SRS 412 before receiving the DL-PRS 410. In both cases, the positioning server (e.g., the location server 168) or the UE 404 may determine the UL-SRS 412 based on the || T SRS_RX -T PRS_TX |-|T SRS_TX -T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE Rx-Tx time difference measurements (ie, |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. UE 404 uses assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and optionally the DL-PRS-RSRP of the received signal), and TRP 402, 406 uses assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and optionally the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or UE 404 to determine the RTT, which is used to estimate the position of UE 404. Other methods for determining RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

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

[0078] DL-TDOA positioning may utilize DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 uses assistance data received from a positioning server to measure the DL RSTD (and optionally DL-PRS-RSRP) of the received signals, and the resulting measurements, along with other configuration information, are used to position the UE 404 relative to neighboring TRPs 402, 406.

[0079] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of uplink signals transmitted from a UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the UL-RTOA (and optionally UL-SRS-RSRP) 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.

[0080] 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 a 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 are used along with other configuration information to estimate the position of the UE 404.

[0081] 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. It should be noted that data / measurements from various techniques may be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / refine measurements, and / or replace / provide missing information.

[0082] In addition to network-based UE positioning techniques, wireless devices (e.g., UEs, access points (APs), etc.) may also be configured to include sensing capabilities, where the wireless device may be able to sense (e.g., detect and / or track) one or more objects or target entities in an area or environment based on radio frequency. An environment may refer to a specific geographic area or location, particularly an area or location affected by human activity, or the circumstances, objects, or conditions surrounding it. For example, a wireless device may include radar capabilities (which may be referred to as "RF sensing" and / or "cellular-based RF sensing"), where the wireless device may transmit a reference signal (e.g., a radar reference signal (RSS)) and measure the reference signal reflected from one or more objects (e.g., structures, walls, living objects, and / or objects in the environment). Based on the measurements, the wireless device may determine or estimate the distance between the wireless device and the one or more objects and / or obtain environmental information associated with its surrounding environment. In another example, a first wireless device may receive a signal transmitted from a second wireless device, where the first wireless device may determine or estimate the distance between the first wireless device and the second wireless device based on the received signal. For example, a tracking device (e.g., a Bluetooth tracker, an item tracker, an asset tracking device, etc.) can be configured to regularly send a signal (e.g., a beacon signal) or a small amount of data to a receiving device, so that the receiving device can monitor the location or relative distance of the tracking device. Thus, a user can track the location of an item by attaching the tracking device to an item (e.g., a car key, a wallet, a remote control, etc.). For the purposes of this disclosure, a device / apparatus capable of performing sensing (e.g., sending and / or receiving signals for detecting at least one object or for estimating the distance between the device and at least one object) may be referred to as a "sensing device" or "sensing node." For example, a sensing device may be a UE, an AP device (e.g., a Wi-Fi router), a base station, a component of a base station, a TRP, a device capable of performing radar functions, etc. Furthermore, a target entity may be any object (e.g., a person, a vehicle, a UE, etc.) for which a positioning or sensing session is performed, for example, to determine its location, speed, heading, physiological characteristics, etc. Furthermore, a device / apparatus capable of sending a signal to a sensing device for the sensing device to determine the location or relative distance of the device / apparatus may be referred to as a "tracking device," "tracker," or "tag."

[0083] For the purposes of this disclosure, a positioning session may refer to the transmission, reception, and measurement of reference signals performed to determine a positioning result or state (e.g., position, heading, velocity, etc.) of a target entity. An RF sensing session may refer to the transmission, reception, and measurement of reference signals performed to determine a sensing result or state (e.g., a change in the environment) of an environment including a target entity, at least one physiological characteristic of the target entity, the position of the target entity, the velocity of the target entity, the heading of the target entity, etc.

[0084] For a positioning session, the fusion of map information and radio signal measurements can enhance positioning performance. For example, map-assisted positioning can be used for satellite selection. Based on the future (or predicted) three-dimensional (3D) environment of the vehicle and the known satellite positions, one or more satellites that will be visible during the predicted vehicle trajectory can be determined and selected. In another example, map-assisted positioning can be used for adaptive sampling of inertial sensors, where the device's sensors can be turned on (e.g., activated) in areas where positioning is challenging (as indicated by a map) to improve positioning accuracy, and turned off (e.g., deactivated) in areas where positioning is less challenging. In another example, map-assisted positioning can be implemented using non-line-of-sight (NLOS) paths, where NLOS components are measured and projected on a map to provide additional formulas for positioning. In yet another example, map-assisted positioning can be used for crowdsourcing for radar positioning, where global reference maps can be generated based on radar inputs from different vehicles, which are then used to match new car radar signature inputs to generate new car positions.

[0085] Node selection (e.g., TRP, UE, etc.) in Uu (UE-Terrestrial Radio Access Network (TRAN)) positioning or sidelink-based positioning can play a role in improving positioning or RF sensing performance. Different metrics can be utilized for node selection. Such metrics include, but are not limited to, signal-to-noise ratio (SNR), RSRP, etc. In some aspects, the TRP for NR UE-based positioning can be selected based on the geometric dilution of precision (GDOP) of different TRPs. For the purposes of this disclosure, a device / apparatus capable of selecting a node for a positioning or sensing session (e.g., to coordinate a positioning or sensing session) is referred to as a coordinator node. As described herein, examples of coordinator nodes include LMF 166, SnMF 167, or a UE (e.g., UE 104, UE 350, or UE 404).

[0086] In some aspects, a TRP can be selected based on PRS measurements. For example, a common set of TRPs can be selected for measurement by two UEs in a joint UE positioning session. In some aspects, node selection can be used for RFFP (Random Forest Fingerprint) federated learning, where the selection of UEs to participate in training a federated learning positioning model is based on several criteria including, but not limited to, region, coverage area, UE computational power, etc.

[0087] Within the positioning frequency layer, the DL PRS resources may be sorted in descending order of priority of the measurements to be performed by the UE, with the reference indicated by nr-DL-PRS-ReferenceInfo as the highest priority for the measurement, and assuming the following priority: sort up to 64 dl-PRS-IDs (downlink PRS identifiers identifying the corresponding TRP) of the frequency layer according to priority; and sort up to 2 DL PRS resource sets per dl-PRS-ID of the frequency layer according to priority.

[0088] Using map information at a coordinator node (e.g., LMF 166 for uplink and / or downlink-based positioning sessions, SnMF 167 for uplink and / or downlink-based sensing sessions, or a coordinator UE for sidelink-based positioning or sensing sessions), the coordinator node can select PRS resources (e.g., TRPs or anchor nodes (e.g., UEs)) to be measured by the target UE. For the purposes of this disclosure, a device / apparatus capable of participating in the transmission or reception of sidelink reference signals for a target UE is referred to as an anchor node. The set of d1-PRS-IDs provided to the target UE may be a result of using map information. For example, with access to a map and an approximate UE location, the coordinator node may estimate that some TRPs or anchor UEs will be blocked (or located in NLOS to the target UE) and may then exclude such TRPs or anchor UEs from the list of UE PRS measurements. The selection process may affect the priority order of the d1-PRS-IDs that the target UE can measure. The coordinator node may use the map information and its UE position estimate to update the list of PRS measurements performed by the target UE. For example, in a periodic positioning session, the coordinator node may estimate and track the target UE location. Based on the target UE location, the coordinator node may update a list of TRPs or anchor UEs that the target UE can measure. The list of PRS signals that may be updated based on the map information may include a Uu PRS (e.g., for uplink or downlink-based positioning or sensing), a sidelink PRS (e.g., for sidelink-based positioning or sensing), or a combination of a Uu PRS and a SL PRS (e.g., for joint Uu / sidelink-based positioning or sensing).

[0089] For example, Figure 5 FIG5 is a diagram illustrating an environment in which a positioning or RF sensing session is performed according to various aspects of the present disclosure. Figure 5As shown, diagram 500 illustrates a first TRP 502, a second TRP 506, a target UE 504, a geographic information system (GIS) based database 508, an LMF 166, and a SnMF 167. The LMF 166 may be used to perform a positioning session for the target UE 504, and the SnMF 167 may be used to perform a sensing session for the target UE 504. The LMF 166 and / or the SnMF 167 may obtain map information of the environment from the GIS based database 508. For example, the LMF 166 and / or the SnMF 167 may provide a request for map information to the GIS based database 508, and the GIS based database 508 may provide a response including the map information. The map information may include geographic data representing various features located within the environment. The features may include both natural features and man-made features. Examples of natural features include, but are not limited to, trees, vegetation, canyons, mountains, etc. Examples of man-made features include, but are not limited to, roads, buildings, houses, bridges, utility poles, etc. In Figure 5 In the example shown, the geographic data provided to the LMF 166 and / or SnMF 167 may represent road A 510 , road B 512 , building A 514 , and building B 516 .

[0090] The LMF 166 and / or the SnMF 167 may be configured to select one or more TRPs (e.g., TRPs 502 and 506) based on map information obtained from a GIS-based database 508 and an approximate location of the target UE 504. In some aspects, the approximate location of the target UE 504 may correspond to a location previously determined for the target UE 504, for example, via a previously performed positioning or sensing session. In other aspects, the approximate location may be based on global navigation satellite system (GNSS) positioning coordinates (e.g., global positioning system (GPS) coordinates). In such aspects, the target UE 504 may provide its GNSS-based positioning coordinates to the LMF 166 and / or the SnMF 167.

[0091] exist Figure 5In the example shown, LMF 166 and / or SnMF 167 may select TRP 506 for the positioning and / or sensing session based on map information and the approximate location of target UE 504 and exclude TRP 502 from the positioning and / or sensing session. LMF 166 and / or SnMF 167 may select TRP 506 because it is within the line of sight of target UE 504. That is, reference signal 518 transmitted by TRP 506 is provided directly to target UE 504 without being reflected from any obstacles in the environment. Similarly, reference signal 522 transmitted by target UE 504 is received by TRP 506 without being reflected from any obstacles in the environment. LMF 166 and / or SnMF 167 may exclude TRP 502 because it is not within the line of sight of target UE 504. That is, the reference signal 520 transmitted by the TRP 502 is received by the target UE 504 as an NLOS because the reference signal 520 is reflected from an obstacle (e.g., Building B 516) before being received by the target UE 504. Similarly, the reference signal 524 transmitted by the target UE 504 is received by the TRP 502 as an NLOS because the reference signal 524 is reflected from an obstacle (e.g., Building B 616) before being received by the TRP 502.

[0092] LMF 166 and / or SnMF 167 may update the list of reference signal measurements to indicate that TRP 506 is selected, and provide the list to target UE 504. Target UE 504 may utilize the list to perform measurements on reference signals received from TRP 506 instead of reference signals received from TRP 502. In the event that multiple TRPs are selected, LMF 166 and / or SnMF 167 may prioritize the multiple TRPs, for example, based on the distance of each of the TRPs relative to target UE 504, where a TRP with a closer distance to target UE 504 has a higher priority in the list.

[0093] In some aspects, map-based node selection may be performed without the LMF 166 and / or SnMF 167. For example, for a sidelink-based positioning or sensing session, the coordinator UE may utilize map information to select an anchor node (e.g., an anchor UE) that will participate in the positioning or sensing session. The coordinator node may be the target UE itself, an anchor node, or a sidelink node (e.g., a sidelink UE) whose role is to coordinate the SL positioning or sensing session. The anchor node may be a node that participates in the transmission or reception of a sidelink reference signal.

[0094] For example, Figure 6 FIG6 is a diagram illustrating an environment in which a sidelink-based positioning or sidelink RF sensing session is performed according to various aspects of the present disclosure. Figure 6 As shown, diagram 600 illustrates a coordinator UE 604A, an anchor UE 604B, an anchor UE 604C, a target UE 604D, and a GIS-based database 608. The coordinator UE 604A may obtain map information of an environment from the GIS-based database 608. For example, the coordinator UE 604A may provide a request for map information to the GIS-based database 608, and the GIS-based database 608 may provide a response including the map information. Figure 6 In the example shown, the geographic data provided to the coordinator UE 604A may represent Road A 610 , Road B 612 , Building A 614 , and Building B 616 .

[0095] The coordinator UE 604A may be configured to select one or more anchor UEs based on map information obtained from a GIS-based database 608 and the approximate location of the target UE 604D. Figure 6 In the illustrated example, coordinator UE 604A may select anchor UE 604C for a positioning and / or sensing session based on map information and the approximate location of target UE 604D, and exclude anchor UE 604B from the positioning and / or sensing session. Coordinator UE 604A may select anchor UE 604C because it is within line of sight of target UE 604D. That is, reference signal 618 transmitted by anchor UE 604C is provided directly to target UE 504 without being reflected from any obstacles in the environment. Similarly, reference signal 622 transmitted by target UE 604D is received by anchor UE 604C without being reflected from any obstacles in the environment. Coordinator UE 604A may exclude anchor UE 604B because it is not within line of sight of target UE 504. That is, the reference signal 620 transmitted by the anchor UE 604B is received by the target UE 604D as NLOS because the reference signal 620 is reflected from an obstacle (e.g., Building B 616) before being received by the target UE 604D. Similarly, the reference signal 624 transmitted by the target UE 604D is received by the anchor UE as NLOS because the reference signal 624 is reflected from an obstacle (e.g., Building B 616) before being received by the anchor UE 604B.

[0096] The coordinator UE 604A may update the reference signal measurement list to indicate that the anchor UE 604C is selected, and provide the list to the target UE 604D. The target UE 604D may use the list to perform measurements on reference signals received from the anchor UE 604C instead of the reference signals received from the anchor UE 604B. In the event that multiple anchor nodes are selected, the coordinator UE 604A may prioritize the multiple anchor UEs, for example, based on the distance of each of the anchor UEs relative to the target UE 604D, where the closer the anchor UE is to the target UE 604, the higher the priority in the list.

[0097] In some aspects, the target UE may use its map information to provide a list of suitable or desired TRPs / anchor UEs to a node coordinating a positioning or sensing session (e.g., LMF 166, SnMF 167, or coordinator UE 604A). The target UE may obtain its map information from a map application or web mapping platform executed on the target UE. Examples of map applications include, but are not limited to, Google Maps published by Google LLC of Mountain View, California. TM Apple Maps, published by Apple Inc. of Cupertino, California TM Etc. The list may enable the coordinator node to update the priority of TRP / SL UEs to be measured by the target UE, discard (e.g., ignore) certain PRS measurements of the target UE, or turn off (e.g., disable) certain PRS measurements from certain TRP / anchor UEs.

[0098] In some aspects, a target UE may indicate (or suggest) to the LMF 166, SnMF 167, or a sidelink UE (e.g., coordinator UE 604A) that it is dropping (or may drop) Uu / SL PRS measurements for X time units, where X may be represented by a number of time slots, a number of subframes, a number of milliseconds, a number of seconds, or a number of future resources. PRS resources may be part of a Uu-based positioning or sensing session, a sidelink-based positioning or sensing session, or a combined Uu / sidelink-based positioning or sensing session. When utilizing UE-based positioning (where the target UE determines the location of an entity (including itself) and does not share the results with another entity), the target UE may drop measurements, and the indication from the target UE may help conserve and optimize over-the-air (OTA) resources. When utilizing UE-assisted positioning (where the target UE does not determine the location of an entity (including itself), but instead performs measurements and shares the measurements with the LMF 166, SnMF 167, or coordinator UE 604A), the target UE may recommend / suggest dropping certain resources. However, the network or UE coordinating the session (e.g., for sidelink-based positioning or sensing) determines whether to activate the UE recommendation. The indications and / or recommendations described above may be communicated to the LMF 166 or SnMF 167 via LTE Positioning Protocol (LPP) signaling, or to the coordinator UE 604A via Sidelink-based Positioning Protocol (SLPP) signaling.

[0099] In some aspects, when utilizing UE-assisted positioning, the target UE's ability to discard measurements or change the priority of PRS measurements, as provided by the LMF 166 or SnMF 167, based on its map information may be disabled or enabled by the LMF 166 or SnMF 167. For example, the LMF 166, SnMF 167, or coordinator UE 604A may provide an indication to the target UE 504 or 640D to disable or enable such capability. The target UE 504 or 604D may have a default behavior if it includes map-based processing capabilities. For example, by default, the target UE 504 or 604D may be enabled to use its map information to adjust the priority of PRS measurements.

[0100] Figure 7A and Figure 7B Depicted are call flow diagram 700 and call flow diagram 701, respectively, illustrating methods of wireless communication according to various aspects of the present disclosure. Figure 7AAs shown, diagram 700 includes one or more TRPs 702, one or more anchor nodes 704B, a target UE 704E, a LMF 706, a SnMF 710, a coordinator UE 704A, and a GIS-based database 708. The LMF 706 and TRP 702 may be used for an uplink and / or downlink-based positioning session for the target UE 704E. The SnMF 710 and TRP 702 may be used for an uplink and / or downlink-based RF sensing session for the target UE 704E. The coordinator UE 704A and the anchor node 704B may be used for a sidelink-based positioning session or a sidelink-based RF sensing session. The GIS-based database 708 may be an example of the GIS-based database 608. The LMF 706 may be an example of the LMF 166. The SnMF 710 may be an example of the SnMF 167. Coordinator UE 704A may be an example of UE 104, UE 350, UE 404, or coordinator UE 604A. TRP 702 may be an example of base station 102, base station 310, TRP 402, TRP 406, TRP 502, and TRP 506. Anchor node 704B may be an example of UE 104, UE 350, UE 404, anchor UE 604B, or anchor UE 604C. Target UE 704E may be an example of UE 104, UE 350, UE 404, target UE 504, or target UE 604D. Although various aspects are described with respect to TRP 702, these aspects may be performed by the network node as a whole and / or by one or more components of TRP 702 (e.g., such as CU 110, DU 130, and / or RU 140). As Figure 7A As shown, at 712, the LMF 706, SnMF, and / or coordinator UE 704A may obtain map information from the GIS-based database 708. In some aspects, the coordinator UE 704A may obtain the map information from a map application or web mapping platform executing on the coordinator UE 704A.

[0101] At 714, the LMF 706, the SnMF, and / or the coordinator UE 704A may determine the location of the target UE 704E. In some aspects, the location of the target UE 704E may correspond to a location previously determined for the target UE 704E, for example, via a previously performed positioning or sensing session. In other aspects, the location may be based on global navigation satellite system (GNSS) positioning coordinates (e.g., global positioning system (GPS) coordinates). In such aspects, the target UE 704E may provide its GNSS-based positioning coordinates to the LMF 166, the SnMF 167, and / or the coordinator UE 704A.

[0102] At 716, in aspects where a downlink and / or uplink-based positioning session is to be performed for the target UE 704E, the LMF 706 may select one or more of the TRPs 702 for the positioning session based on map information and / or the location of the target UE 704E. In aspects where a downlink and / or uplink-based RF sensing session is to be performed for the target UE 704E, the SnMF 710 may select one or more of the TRPs 702 for the RF sensing session based on map information and / or the location of the target UE 704E. In aspects where a sidelink-based positioning session or a sidelink RF sensing session is to be performed for the target UE 704E, the coordinator UE 704A may select one or more of the anchor nodes 704B for the positioning session or the RF sensing session based on map information and / or the location of the target UE 704E.

[0103] At 717, the target UE 704 may obtain map information associated with the target UE 704E. The target UE 704E may obtain its map information from a map application or web mapping platform executed on the target UE 704E. The map information may include geographic data representing various features within the environment in which the target UE 704E is located.

[0104] In some aspects, at 718, the LMF 166, the SnMF 167, and / or the coordinator UE 704A may receive information indicating a TRP and / or anchor node 704B from the target UE 704E. The information may be based on the map information associated with the target UE 704E obtained at 717. For example, at 718, in aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for the target UE 704E, the target UE 704 may provide a list of suitable or desired TRPs in the TRPs 702 to the LMF 706 and / or the SnMF 710. The list of suitable or desired TRPs in the TRPs 702 may be based on the map information associated with the target UE 704E. At 720, the LMF 706 and / or the SnMF 710 may update the priority of the TRP 702 for the target UE 704E to measure its reference signal (e.g., PRS) based on the received information at 718. In an aspect where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, the target UE 704E may provide the coordinator UE 704A with a list of suitable or desired anchor nodes from the anchor nodes 704B. At 720, the coordinator UE 704A may update the priority of the anchor node 704B for the target UE 704E to measure its reference signal based on the received information at 718.

[0105] In some aspects, each TRP in TRP 702 may be associated with an ID that is associated with an ID of each reference signal (e.g., PRS) sent by the TRP.

[0106] At 722, in aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for the target UE 704E, the LMF 166 and / or the SnMF 167 may configure a TRP in the TRP 702 based on the selection at 716 and / or the list of suitable or desired TRPs received from the target UE 704E. For example, the LMF 166 and / or the SnMF 167 may send an indication of the configuration to the TRP in the TRP 702 based on the selection at 716 and / or the list of suitable or desired TRPs received from the target UE 704E. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, the coordinator UE 704A may configure an anchor node in the anchor node 704B based on the selection at 716 and / or the list of suitable or desired anchor nodes received from the target UE 704E. For example, the coordinator UE 704A may send an indication of the configuration to an anchor node in the anchor nodes 704B based on the selection at 716 and / or the list of suitable or desired anchor nodes received from the target UE 704E.

[0107] In some aspects, in aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for a target UE 704E, the configuration may indicate that a selected one of the TRPs 702 is to enable transmission and / or reception of reference signals (e.g., PRS). Thus, at 724, the selected one of the TRPs 702 may activate transmission and / or reception of reference signals. In some aspects, the LMF 166 and / or the SnMF 167 may configure the unselected ones of the TRPs 702 to disable transmission and / or reception of reference signals. Thus, at 724, the unselected ones of the TRPs 702 may deactivate transmission and / or reception of reference signals. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, the configuration may indicate that a selected one of the anchor nodes 704B is to enable transmission and / or reception of reference signals (e.g., PRS). Thus, at 724, the selected anchor node among the anchor nodes 704B may activate transmission and / or reception of reference signals. In some aspects, the coordinator UE 704A may configure the unselected anchor nodes among the anchor nodes 704B to disable transmission and / or reception of reference signals. Thus, at 724, the unselected anchor nodes among the anchor nodes 704B may deactivate transmission and / or reception of reference signals.

[0108] At 726, in aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for the target UE 704E, a selected one of the TRPs 702 may transmit a downlink reference signal to the target UE 704E as part of the uplink and / or downlink-based positioning or RF sensing session. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, at 726, a selected one of the anchor nodes 704B may transmit a sidelink reference signal to the target UE 704E as part of the uplink and / or downlink-based positioning or RF sensing session.

[0109] At 728, in aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for the target UE 704E, the target UE 704E may send an uplink reference signal as part of the uplink-based positioning or RF sensing session to a selected one of the TRPs 702. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, at 728, the target UE 704E may send a sidelink reference signal as part of the sidelink-based positioning or RF sensing session to a selected one of the anchor nodes 704B.

[0110] In some aspects, the downlink and uplink reference signals may comprise a UE-TRAN PRS. In some aspects, the sidelink reference signal may comprise a sidelink (SL) PRS.

[0111] In some aspects, at 730, the target UE 704E may provide an indication to the LMF 166, the SnMF 167, and / or the coordinator UE 704A that the target UE 704E is discarding reference signal measurements of reference signals received at 726 from the TRP 702 (e.g., for uplink and / or downlink-based positioning or RF sensing sessions) or reference signal measurements of reference signals received at 726 from the anchor node 704B (e.g., for sidelink-based positioning or RF sensing sessions). The indication may be based on the map information associated with the target UE 704E obtained at 717. The indication may indicate that the target UE 704E is discarding measurements within a specific time unit. In some aspects, the specific time unit may include at least one of a certain number of time slots, a certain number of subframes, a certain number of milliseconds, or a certain number of seconds.

[0112] In an aspect where an uplink and / or downlink-based positioning session or an RF sensing session is being performed for the target UE 704E, at 730, the target UE 704E may provide an indication to the LMF 166 and / or the SnMF 167 indicating (e.g., recommending or suggesting) dropping reference signal resources for at least one of the TRPs 702. The LMF 166 and / or the SnMF 167 may send an indication of a configuration for at least one of the TRPs 702 to drop reference signal resources at 732. The indication may be based on the map information associated with the target UE 704E obtained at 717. In an aspect where a sidelink-based positioning session or an RF sensing session is being performed for the target UE 704E, at 730, the target UE 704E may provide an indication to the coordinator UE 704A indicating (e.g., recommending or suggesting) dropping reference signal resources for at least one of the anchor nodes 704B. At 732, the coordinator UE 704A may send an indication of a configuration to drop reference signal resources for at least one of the anchor nodes 704B.

[0113] In some aspects, the indication (e.g., recommendation or suggestion) may be sent via LPP signaling to the LMF 166 and / or SnMF 167. In some aspects, the indication (e.g., recommendation or suggestion) may be sent via SLPP signaling to the coordinator UE 704A.

[0114] In aspects where an uplink and / or downlink-based positioning session or RF sensing session is being performed for the target UE 704E, the LMF 166 and / or the SnMF 167 may track the location of the target UE 704E and update a list of TRPs 702 for measurement by the target UE 704E. For example, at 734, the LMF 166 and / or the SnMF 167 may determine an updated location of the target UE 704E and, at 736, select another set of TRPs 702 based on the updated location and map information. At 738, the LMF 166 and / or the SnMF 167 may configure another set of TRPs 702 for the positioning or RF sensing session based on the updated location. In aspects where a sidelink-based positioning session or an RF sensing session is being performed for a target UE 704E, the coordinator UE 704A may track the location of the target UE 704E and update a list of anchor nodes 704B for measurement by the target UE 704E. For example, at 734, the coordinator UE 704A may determine an updated location of the target UE 704E and, at 736, select another set of anchor nodes 704B based on the updated location and map information. At 738, the coordinator UE 704A may configure the other set of anchor nodes 704B for the positioning or RF sensing session.

[0115] In some aspects, in aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for a target UE 704E, the configuration may indicate that a selected one of the TRPs 702 is to enable transmission and / or reception of reference signals (e.g., PRS). Thus, at 740, the selected one of the TRPs 702 may activate transmission and / or reception of reference signals. In some aspects, the LMF 166 and / or the SnMF 167 may configure the unselected ones of the TRPs 702 to disable transmission and / or reception of reference signals. Thus, at 740, the unselected ones of the TRPs 702 may deactivate transmission and / or reception of reference signals. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, the configuration may indicate that a selected one of the anchor nodes 704B is to enable transmission and / or reception of reference signals (e.g., PRS). Thus, at 740, the selected anchor node among the anchor nodes 704B may activate transmission and / or reception of reference signals. In some aspects, the coordinator UE 704A may configure the unselected anchor nodes among the anchor nodes 704B to disable transmission and / or reception of reference signals. Thus, at 740, the unselected anchor nodes among the anchor nodes 704B may deactivate transmission and / or reception of reference signals.

[0116] At 742, in aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for the target UE 704E, the newly selected TRP in the TRPs 702 may transmit a downlink reference signal to the target UE 704E as part of the uplink and / or downlink-based positioning or RF sensing session. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, at 742, the newly selected anchor node in the anchor nodes 704B may transmit a sidelink reference signal to the target UE 704E as part of the uplink and / or downlink-based positioning or RF sensing session.

[0117] At 744, in aspects where uplink and / or downlink-based positioning or an RF sensing session is being performed for the target UE 704E, the target UE 704E may transmit an uplink reference signal as part of the uplink-based positioning or RF sensing session to a newly selected TRP in the TRP 702. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, at 744, the target UE 704E may transmit a sidelink reference signal as part of the sidelink-based positioning or RF sensing session to a newly selected anchor node in the anchor nodes 704B.

[0118] Figure 8 8 is a flow chart illustrating a method of wireless communication at a first network node according to various aspects of the present disclosure. In some aspects, the first network node may be LMF 166, LMF 706, SnMF 167, SnMF 710, UE 104, UE 350, UE 404, coordinator UE 604A, or coordinator UE 704A. Figure 12 The hardware implementation of the device 1204, or Figure 12 The network entity 1460 in the hardware specific implementation.

[0119] At 802, a first network node may obtain first map information associated with at least one of a positioning session or an RF sensing session. Figure 7A At 712, the LMF 706, the SnMF, and / or the coordinator UE 704A may obtain first map information associated with at least one of the positioning session or the RF sensing session from the GIS-based database 708. In aspects where uplink and / or downlink-based positioning or RF sensing sessions are being performed, 802 may be performed by the map-assisted positioning / sensing component 199. In aspects where sidelink-based positioning or RF sensing sessions are being performed, 802 may be performed by the map-assisted positioning / sensing component 198.

[0120] In some aspects, the first network node may be a first UE configured to coordinate at least one of a positioning session or an RF sensing session for at least one second network node, and the at least one second network node may be a second UE. Figure 7A , the first network node may be a coordinator UE 704A that may be configured to coordinate at least one of a positioning session or an RF sensing session for at least one of the anchor nodes 704B. As described above, at least one of the anchor nodes 704B may be a UE.

[0121] At 804, the first network node may select at least one of the first set of TRPs or at least one second network node for at least one of the positioning session or the RF sensing session based on the first map information. Figure 7AIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 716, the LMF 706 or the SnMF 710 may select at least one TRP from the first set of TRPs 702 for at least one of the positioning session or the RF sensing session based on the first map information. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 716, the coordinator UE 704A may select at least one anchor node from the first set of anchor nodes 704B for at least one of the positioning session or the RF sensing session based on the first map information. In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, 804 may be performed by the map-assisted positioning / sensing component 199. In aspects where a sidelink-based positioning or RF sensing session is being performed, 804 may be performed by the map-assisted positioning / sensing component 198.

[0122] In some aspects, a first network node may determine a first location of a target UE for which at least one of a positioning session or an RF sensing session is to be performed. The first network node may select the first set of TRPs or at least one of the at least one second network nodes by selecting the first set of TRPs or at least one of the at least one second network nodes based on the first location and map information. For example, referring to Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 714, the LMF 706 or the SnMF 710 may determine a first location of the target UE 704E. At 716, the LMF 706 or the SnMF 710 may select at least one TRP in the TRPs 702 based on the first location and the map information. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 714, the coordinator UE 704A may determine a first location of the target UE 704E. At 716, the coordinator UE 704A may select at least one anchor node in the anchor nodes 704B based on the first location and the map information.

[0123] In some aspects, the first network node may receive information indicating at least one of the first set of TRPs or at least one second network node, wherein the information is based on second map information associated with the target UE, and wherein at least one of a positioning session or an RF sensing session is performed for the target UE. For example, referring to Figure 7AIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 718, the LMF 706 or the SnMF 710 may receive information indicating at least one TRP from the first set of TRPs 702. The information may be based on map information associated with the target UE 704E and obtained at 717. The information may include a list of suitable or desired TRPs from the TRPs 702. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 718, the coordinator UE 704A may receive information indicating at least one anchor node from the first set of anchor nodes 704B. The information may be based on map information associated with the target UE 704E and obtained at 717. The information may include a list of suitable or desired anchor nodes from the anchor nodes 704B.

[0124] In some aspects, the first network node may update the priority of at least one of the first set of TRPs or at least one second network node for which the target UE is to measure its PRS based on the information. Figure 7A In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, the LMF 706 or SnMF 710 may update the priority of the first set of TRPs 702 for which the target UE 704E is to measure PRSs based on the information at 720. In aspects where a sidelink based positioning or RF sensing session is being performed, the coordinator UE 704A may update the priority of the first set of anchor nodes 704B for which the target UE 704E is to measure PRSs based on the information at 720.

[0125] At 806, the first network node may configure at least one of the first set of TRPs or at least one second network node for at least one of a positioning session or an RF sensing session. Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 722, the LMF 706 or the SnMF 710 may configure at least one TRP from the first set of TRPs 702 for at least one of the positioning session or the RF sensing session. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 722, the coordinator UE 704A may configure at least one anchor node from the first set of anchor nodes 704B for at least one of the positioning session or the RF sensing session. In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, 806 may be performed by the map-assisted positioning / sensing component 199. In aspects where a sidelink-based positioning or RF sensing session is being performed, 806 may be performed by the map-assisted positioning / sensing component 198.

[0126] In some aspects, the ID of each TRP in the first set of TRPs is associated with the ID of each PRS in the first set of PRSs. Figure 7A , the ID of each TRP in TRP 702 is associated with the ID of each PRS in the first set of PRSs (e.g., sent at 726 by each TRP in TRP 702).

[0127] In some aspects, the PRS may include at least one of a UE-TRAN PRS or a sidelink PRS. Figure 7A In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, the PRS sent by the TRP 702 at 726 may include a UE-TRAN PRS. In aspects where a sidelink based positioning or RF sensing session is being performed, the PRS sent by the anchor node 704B may be a sidelink PRS.

[0128] In some aspects, the first network node may configure the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session by sending an indication of the configuration of the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session to the first set of TRPs or at least one of the at least one second network nodes. For example, with reference to Figure 7A In aspects where uplink and / or downlink based positioning or RF sensing sessions are being performed, at 722, the LMF 706 or the SnMF 710 may send an indication of configuration for at least one of the positioning session or the RF sensing session to the first set of TRPs 702. In aspects where sidelink based positioning or RF sensing sessions are being performed, at 722, the coordinator UE 704A may send an indication of configuration for at least one of the positioning session or the RF sensing session to the anchor node 704B.

[0129] In some aspects, the first network node may send an indication to disable PRS transmission to at least one of the first set of TRPs or at least one second network node based on the information. Figure 7AIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 722, the LMF 706 or the SnMF 710 may, based on the information, send an indication indicating that PRS transmission is to be disabled for at least one TRP in the first set of TRPs 702. The indication may be sent as part of the configured indication sent at 722. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 722, the coordinator UE 704A may, based on the information, send an indication indicating that PRS transmission is to be disabled for the anchor node 704B. The indication may be sent as part of the configured indication sent at 722.

[0130] In some aspects, the first network node may receive an indication that a target UE for which at least one of a positioning session or an RF sensing session is being performed is dropping PRS measurements within a specific time unit. The indication may be based on map information associated with the target UE. For example, referring to Figure 7B In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 730, the LMF 706 or SnMF 710 may receive an indication that the target UE 704E is dropping PRS measurements for a specific time unit. The indication may be based on map information associated with the target UE 704E. In aspects where a sidelink-based positioning or RF sensing session is being performed, the coordinator UE 704A may receive an indication that the target UE 704E is dropping PRS measurements for a specific time unit.

[0131] In some aspects, the specific time unit may include at least one of a number of time slots, a number of subframes, a number of milliseconds, or a number of seconds. Figure 7B The particular time unit that may be indicated via the indication received at 730 may include at least one of a number of time slots, a number of subframes, a number of milliseconds, or a number of seconds.

[0132] In some aspects, the first network node may receive an indication from the target UE indicating (e.g., recommending or suggesting) to drop PRS resources for one or more TRPs in the first set of TRPs or at least one of the at least one second network node. The first network node may send an indication to drop PRS resources for one or more TRPs in the first set of TRPs or at least one of the at least one second network node. For example, referring to Figure 7BIn an aspect where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 730, the LMF 706 or the SnMF 710 may receive an indication from the target UE 704E indicating (e.g., recommending or suggesting) to drop PRS resources for at least one of the TRPs 702. At 732, the LMF 706 or the SnMF 710 may send an indication to drop PRS resources for at least one of the TRPs 702. In an aspect where a sidelink-based positioning or RF sensing session is being performed, at 730, the coordinator UE 704A may receive an indication from the target UE 704E indicating (e.g., recommending or suggesting) to drop PRS resources for at least one of the anchor nodes 704B. At 732, the coordinator UE 704A may send an indication to drop PRS resources for at least one of the anchor nodes 704B.

[0133] In some aspects, the first network node may receive the indication via one of LPP signaling or SLPP signaling. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, the LMF 706 or SnMF 710 may receive the indication via LPP signaling at 730. In aspects where a sidelink based positioning or RF sensing session is being performed, the coordinator UE 704A may receive the indication via SLPP signaling at 730.

[0134] In some aspects, the first network node may determine a second location of the target UE. The first network node may select a second set of TRPs or at least one of the at least one third network nodes for at least one of the positioning session or the RF sensing session based on the second location and the map information. The first network node may configure the second set of TRPs or at least one of the at least one third network nodes for at least one of the positioning session or the RF sensing session. For example, referring to Figure 7BIn aspects where an uplink- and / or downlink-based positioning or RF sensing session is being performed, at 734, the LMF 706 or SnMF 710 may determine an updated location of the target UE 704E. At 736, the LMF 706 or SnMF 710 may select a second set of TRPs 702 based on the updated location and map information. At 738, the LMF 706 or SnMF 710 may configure one or more additional TRPs in the TRPs 702. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 734, the coordinator UE 704A may determine an updated location of the target UE 704E. At 736, the coordinator UE 704A may select at least one additional anchor node from the anchor nodes 704B based on the second location and map information. At 738, the coordinator UE 704A may configure at least one additional anchor node in the anchor nodes 704B.

[0135] Figure 9 900 is a flowchart illustrating a method of wireless communication at a first network node according to various aspects of the present disclosure. In some aspects, the first network node may be LMF 166, LMF 706, SnMF 167, SnMF 710, UE 104, UE 350, UE 404, coordinator UE 604A, or coordinator UE 704A, Figure 12 The hardware implementation of the device 1204, or Figure 12 The network entity 1460 in the hardware specific implementation.

[0136] At 902, a first network node may obtain first map information associated with at least one of a positioning session or an RF sensing session. Figure 7A At 712, the LMF 706, the SnMF, and / or the coordinator UE 704A may obtain map information associated with at least one of the positioning session or the RF sensing session from the GIS-based database 708. In one aspect, 902 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0137] In some aspects, the first network node may be a first UE configured to coordinate at least one of a positioning session or an RF sensing session for at least one second network node, and the at least one second network node may be a second UE. Figure 7A , the first network node may be a coordinator UE 704A that may be configured to coordinate at least one of a positioning session or an RF sensing session for at least one of the anchor nodes 704B. As described above, at least one of the anchor nodes 704B may be a UE.

[0138] At 904, the first network node may determine a first location of a target UE for which at least one of a positioning session or an RF sensing session is performed. Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 714, the LMF 706 or the SnMF 710 may determine a first position of the target UE 704E. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 714, the coordinator UE 704A may determine a first position of the target UE 704E. In an aspect, 904 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0139] At 906, the first network node may select at least one of the first set of TRPs or at least one second network node for at least one of the positioning session or the RF sensing session based on the first map information. Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 716, the LMF 706 or the SnMF 710 may select at least one TRP from the first set of TRPs 702 for at least one of the positioning session or the RF sensing session based on the map information. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 716, the coordinator UE 704A may select at least one anchor node from the first set of anchor nodes 704B for at least one of the positioning session or the RF sensing session based on the map information. In an aspect, 906 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0140] In some aspects, as part of 906, at 908, the first network node may select at least one of the first set of TRPs or at least one second network node based on the first location and the map information. Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 716, the LMF 706 or the SnMF 710 may select at least one of the TRPs 702 based on the first location and the map information. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 716, the coordinator UE 704A may select at least one of the anchor nodes 704B based on the first location and the map information. In an aspect, 908 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0141] At 910, the first network node may receive information indicating at least one of a first set of TRPs or at least one second network node from a target UE, wherein the information is based on second map information associated with the target UE, and wherein at least one of a positioning session or an RF sensing session is performed for the target UE. For example, referring to Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 718, the LMF 706 or the SnMF 710 may receive information indicating a first set of TRPs 702 from the target UE 704E, wherein the information is based on second map information associated with the target UE 704E and received at 717. The information may include a list of suitable or desired TRPs in the TRPs 702. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 718, the coordinator UE 704A may receive information indicating a first set of anchor nodes 704B from the target UE 704E, wherein the information is based on second map information associated with the target UE 704E and received at 717. The information may include a list of suitable or desired anchor nodes in the anchor nodes 704B. In an aspect, 910 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0142] At 912, the first network node may update the priority of at least one of the first set of TRPs or at least one second network node for which the target UE is to measure its PRS based on the information. Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 720, the LMF 706 or the SnMF 710 may update the priority of a first set of TRPs 702 for which the target UE 704E is to measure its PRS based on the information. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 720, the coordinator UE 704A may update the priority of a first set of anchor nodes 704B for which the target UE 704E is to measure its PRS based on the information. In an aspect, 912 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0143] At 914, the first network node may configure at least one of the first set of TRPs or at least one second network node for at least one of a positioning session or an RF sensing session. Figure 7AIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 722, the LMF 706 or the SnMF 710 may configure at least one TRP from the first set of TRPs 702 for at least one of the positioning session or the RF sensing session. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 722, the coordinator UE 704A may configure at least one anchor node from the first set of anchor nodes 704B for at least one of the positioning session or the RF sensing session. In an aspect, 914 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0144] In some aspects, the ID of each TRP in the first set of TRPs is associated with the ID of each PRS in the first set of PRSs. Figure 7A , the ID of each TRP in TRP 702 is associated with the ID of each PRS in the first set of PRSs (e.g., sent at 726 by each TRP in TRP 702).

[0145] In some aspects, the PRS may include at least one of a UE-TRAN PRS or a sidelink PRS. Figure 7A In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, the PRS sent by the TRP 702 at 726 may include a UE-TRAN PRS. In aspects where a sidelink based positioning or RF sensing session is being performed, the PRS sent by the anchor node 704B may be a sidelink PRS.

[0146] In some aspects, as part of 914, at 916, the first network node may configure the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session by sending an indication of the configuration of the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session to the first set of TRPs or at least one of the at least one second network nodes. For example, with reference to Figure 7AIn aspects where uplink and / or downlink-based positioning or RF sensing sessions are being performed, at 722, the LMF 706 or the SnMF 710 may send an indication of configuration for at least one of the positioning session or the RF sensing session to at least one of the first set of TRPs 702. In aspects where sidelink-based positioning or RF sensing sessions are being performed, at 722, the coordinator UE 704A may send an indication of configuration for at least one of the positioning session or the RF sensing session to at least one of the first set of anchor nodes 704B. In an aspect, 916 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0147] In some aspects, as part of 914, at 918, the first network node may send an indication to at least one of the first set of TRPs or at least one second network node indicating that PRS transmission is to be disabled based on the information. Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 722, the LMF 706 or the SnMF 710 may, based on the information, transmit an indication indicating that PRS transmission is to be disabled for at least one TRP in the first set of TRPs 702. The indication may be transmitted as part of the configured indication transmitted at 722. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 722, the coordinator UE 704A may, based on the information, transmit an indication indicating that PRS transmission is to be disabled for the anchor node 704B. The indication may be transmitted as part of the configured indication transmitted at 722. In an aspect, 918 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0148] At 920, the first network node may receive an indication that a target UE for which at least one of a positioning session or an RF sensing session is being performed is dropping PRS measurements within a specific time unit, wherein the indication is based on second map information associated with the target UE. Figure 7BIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 730, the LMF 706 or the SnMF 710 may receive an indication that the target UE 704E is dropping PRS measurements for a specific time unit, wherein the indication is based on map information associated with the target UE 704E and obtained at 717. In aspects where a sidelink-based positioning or RF sensing session is being performed, the coordinator UE 704A may receive an indication that the target UE 704E is dropping PRS measurements for a specific time unit, wherein the indication is based on map information associated with the target UE 704E and obtained at 717. In an aspect, 920 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0149] In some aspects, the specific time unit may include at least one of a number of time slots, a number of subframes, a number of milliseconds, or a number of seconds. Figure 7B The particular time unit that may be indicated via the indication received at 730 may include at least one of a number of time slots, a number of subframes, a number of milliseconds, or a number of seconds.

[0150] At 922, the first network node may receive an indication from the target UE indicating (eg, recommending or suggesting) to drop PRS resources for at least one of one or more TRPs in the first set of TRPs or at least one of the at least one second network node. Figure 7B In an aspect where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 730, the LMF 706 or the SnMF 710 may receive an indication from the target UE 704E indicating (e.g., recommending or suggesting) to drop PRS resources for at least one of the TRPs 702. In an aspect where a sidelink-based positioning or RF sensing session is being performed, at 730, the coordinator UE 704A may receive an indication from the target UE 704E indicating (e.g., recommending or suggesting) to drop PRS resources for at least one of the anchor nodes 704B. In an aspect, 922 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0151] In some aspects, as part of 922, at 924, the first network node may receive the indication via one of LPP signaling or SLPP signaling. Figure 7BIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, the LMF 706 or SnMF 710 may receive the indication via LPP signaling at 730. In aspects where a sidelink-based positioning or RF sensing session is being performed, the coordinator UE 704A may receive the indication via SLPP signaling at 730. In an aspect, 924 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0152] At 926, the first network node may send an indication to drop PRS resources for at least one of one or more TRPs in the first set of TRPs or at least one second network node. Figure 7B In an aspect where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 732, the LMF 706 or the SnMF 710 sends an indication to discard PRS resources for at least one of the TRPs 702. In an aspect where a sidelink-based positioning or RF sensing session is being performed, at 732, the coordinator UE 704A may send an indication to discard PRS resources for at least one of the anchor nodes 704B. In an aspect, 926 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0153] At 928, the first network node may determine a second location of the target UE. Figure 7B In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 734, the LMF 706 or SnMF 710 may determine an updated position of the target UE 704E. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 734, the coordinator UE 704A may determine an updated position of the target UE 704E. In an aspect, 928 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0154] At 930, the first network node may select at least one of the second set of TRPs or at least one third network node for at least one of the positioning session or the RF sensing session based on the second location and the map information. Figure 7BIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 736, the LMF 706 or the SnMF 710 may select a second set of TRPs 702 based on the second location and the map information. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 736, the coordinator UE 704A may select at least one other node from the anchor node 704B based on the second location and the map information. In an aspect, 930 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0155] At 932, the first network node may configure at least one of the second set of TRPs or at least one third network node for at least one of the positioning session or the RF sensing session. Figure 7B In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, at 738, the LMF 706 or the SnMF 710 may configure at least one TRP in the TRPs 702. In aspects where a sidelink-based positioning or RF sensing session is being performed, at 738, the coordinator UE 704A may configure a node in the anchor node 704B. In one aspect, 932 may be performed by the map-assisted positioning / sensing component 198 or the map-assisted positioning / sensing component 199.

[0156] Figure 10 1000 is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure. In some aspects, the UE may be UE 104, UE 350, UE 404, target UE 504 and target UE 604D, or target UE 704E, or Figure 12 The device 1204 is implemented in hardware.

[0157] At 1002, the UE may obtain map information associated with at least one of a positioning session or an RF sensing session for the UE. Figure 7A At 717 , the target UE 704E may obtain map information associated with at least one of a positioning session or an RF sensing session for the target UE 704E. In one aspect, 1002 may be performed by the map-assisted positioning / sensing component 198 .

[0158] At 1004, the UE may send an indication of a first set of TRPs or at least one of at least one network node for at least one of a positioning session or an RF sensing session based on the map information. Figure 7AIn aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for the target UE 704E, at 718 or 730, the target UE 704E may send an indication of a first set of TRPs 702. For example, the target UE 704E may provide a list of suitable or desired TRPs in the TRPs 702. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, at 718 or 730, the target UE may send an indication of an anchor node 704B. For example, the target UE 704E may provide a list of suitable or desired anchor nodes in the anchor nodes 704B. In one aspect, 1004 may be performed by the map-assisted positioning / sensing component 198.

[0159] In some aspects, the indication may indicate that the UE is discarding PRS measurements for at least one of the first set of TRPs or at least one network node within a specific time unit. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication that the target UE 704E is discarding PRS measurements for at least one of the first TRPs in the TRPs 702. In aspects where a sidelink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication that the target UE 704E is discarding PRS measurements for at least one of the anchor nodes 704B.

[0160] In some aspects, the UE may discard PRS measurements for at least one of the first set of TRPs or at least one network node within a specific time unit. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, the target UE 704E may discard PRS measurements for PRS reference signals received from at least one TRP in the first set of TRPs 702 received at 726. In aspects where a sidelink based positioning or RF sensing session is being performed, the target UE 704E may discard PRS measurements for PRS reference signals received from at least one of the anchor nodes 704B received at 726.

[0161] In some aspects, the specific time unit includes at least one of a certain number of time slots, a certain number of subframes, a certain number of milliseconds, or a certain number of seconds. Figure 7B , the specific time unit indicated at 730 may include at least one of a certain number of time slots, a certain number of subframes, a certain number of milliseconds, or a certain number of seconds.

[0162] In some aspects, the indication may indicate discarding PRS resources for at least one of the first set of TRPs or at least one network node. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication indicating (e.g., recommending or suggesting) dropping PRS resources for the first set of TRPs 702. In aspects where a sidelink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication indicating (e.g., recommending or suggesting) dropping PRS resources for at least one of the anchor nodes 704B.

[0163] In some aspects, the indication indicates that PRS transmission for at least one of the first set of TRPs or at least one network node is to be disabled. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, the indication sent at 730 may indicate that a first TRP in the TRPs 702 is to be disabled. In aspects where a sidelink based positioning or RF sensing session is being performed, the indication sent at 730 may indicate that at least one of the anchor nodes 704B is to be disabled.

[0164] In some aspects, the UE may send the indication via one of LPP signaling or SLPP signaling. Figure 7B In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, the target UE 704E may send the indication via LPP signaling at 718 or 730. In aspects where a sidelink-based positioning or RF sensing session is being performed, the target UE 704E may send the indication via SLPP signaling at 718 or 730.

[0165] Figure 11 1100 is a flow chart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure. In some aspects, the UE may be UE 104, UE 350, UE 404, target UE 504 and target UE 604D, or target UE 704E, or Figure 12 The device 1204 is implemented in hardware.

[0166] At 1102, the UE may obtain map information associated with at least one of a positioning session or an RF sensing session for the UE. Figure 7AAt 717 , the target UE 704E may obtain map information associated with at least one of a positioning session or an RF sensing session for the target UE 704E. In one aspect, 1102 may be performed by the map-assisted positioning / sensing component 198 .

[0167] At 1104, the UE may send an indication of a first set of TRPs or at least one of the at least one network nodes for at least one of the positioning session or the RF sensing session based on the map information. Figure 7A In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed for the target UE 704E, at 718 or 730, the target UE 704E may send an indication of a first set of TRPs 702. For example, the target UE 704E may provide a list of suitable or desired TRPs in the TRPs 702. In aspects where a sidelink-based positioning or RF sensing session is being performed for the target UE 704E, at 718 or 730, the target UE may send an indication of an anchor node 704B. For example, the target UE 704E may provide a list of suitable or desired anchor nodes in the anchor nodes 704B. In one aspect, 1104 may be performed by the map-assisted positioning / sensing component 198.

[0168] In some aspects, as part of 1104, at 1106, the UE may send the indication via one of LPP signaling or SLPP signaling. Figure 7B In aspects where an uplink and / or downlink-based positioning or RF sensing session is being performed, the target UE 704E may send the indication via LPP signaling at 718 or 730. In aspects where a sidelink-based positioning or RF sensing session is being performed, the target UE 704E may send the indication via SLPP signaling at 718 or 730. In one aspect, 1106 may be performed by the map-assisted positioning / sensing component 198.

[0169] At 1108, the UE may discard PRS measurements for at least one of the first set of TRPs or at least one network node within a specific time unit. Figure 7BIn an aspect where an uplink and / or downlink-based positioning or RF sensing session is being performed, the target UE 704E may discard PRS measurements for PRS reference signals received from at least one TRP in the first set of TRPs 702 received at 726. In an aspect where a sidelink-based positioning or RF sensing session is being performed, the target UE 704E may discard PRS measurements for PRS reference signals received from at least one of the anchor nodes 704B received at 726. In one aspect, 1108 may be performed by the map-assisted positioning / sensing component 198.

[0170] In some aspects, the indication may indicate that the UE is discarding PRS measurements for at least one of the first set of TRPs or at least one network node within a specific time unit. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication that the target UE 704E is discarding PRS measurements for at least one of the first TRPs in the TRPs 702. In aspects where a sidelink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication that the target UE 704E is discarding PRS measurements for at least one of the anchor nodes 704B.

[0171] In some aspects, the specific time unit includes at least one of a certain number of time slots, a certain number of subframes, a certain number of milliseconds, or a certain number of seconds. Figure 7B , the specific time unit indicated at 730 may include at least one of a certain number of time slots, a certain number of subframes, a certain number of milliseconds, or a certain number of seconds.

[0172] In some aspects, the indication may indicate discarding PRS resources for at least one of the first set of TRPs or at least one network node. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication indicating (e.g., recommending or suggesting) dropping PRS resources for the first set of TRPs 702. In aspects where a sidelink based positioning or RF sensing session is being performed, at 730, the target UE 704E may send an indication indicating (e.g., recommending or suggesting) dropping PRS resources for at least one of the anchor nodes 704B.

[0173] In some aspects, the indication indicates that PRS transmission for at least one of the first set of TRPs or at least one network node is to be disabled. Figure 7B In aspects where an uplink and / or downlink based positioning or RF sensing session is being performed, the indication sent at 730 may indicate that a first TRP in the TRPs 702 is to be disabled. In aspects where a sidelink based positioning or RF sensing session is being performed, the indication sent at 730 may indicate that at least one of the anchor nodes 704B is to be disabled.

[0174] Figure 1212 is a diagram illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include a cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., a cellular RF transceiver). The cellular baseband processor 1224 may include on-chip memory 1224′. In some aspects, the apparatus 1204 may also include one or more subscriber identity module (SIM) cards 1220 and an application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor 1206 may include on-chip memory 1206′. In some aspects, the device 1204 may also include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (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 1226, a power source 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas and / or utilize an antenna 1280 for communication. The cellular baseband processor 1224 communicates with the UE 104, the core network 120, and / or RUs associated with the network entity 1202 via one or more antennas 1280 through the transceiver 1222. The cellular baseband processor 1224 and the application processor 1206 may each include computer-readable media / memory 1224', 1206', respectively. The additional memory module 1226 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1224', 1206', 1226 may be non-transitory. The cellular baseband processor 1224 and the application processor 1206 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 1224 / application processor 1206, the software enables the cellular baseband processor 1224 / application processor 1206 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1224 / application processor 1206 when executing the software.The cellular baseband processor 1224 / application processor 1206 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 1204 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1224 and / or the application processor 1206, and in another configuration, the device 1204 may be the entire UE (e.g., see ). Figure 3 UE 350) and includes additional modules of device 1204.

[0175] As discussed above, component 198 may be configured to: obtain first map information associated with at least one of a positioning session or an RF sensing session; select a first set of TRPs or at least one of at least one second network nodes for at least one of the positioning session or the RF sensing session based on the first map information; and configure the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session. In some aspects, component 198 may be configured to: obtain map information associated with at least one of a positioning session or an RF sensing session for a UE; and send an indication of the first set of TRPs or at least one of the at least one network nodes for at least one of the positioning session or the RF sensing session based on the map information. Component 198 may be configured to perform in conjunction with Figures 8 to 11 The various aspects described in the flowchart in and / or by the coordinator UE 704A or the target UE 704E in 7A to 7BComponent 198 may be within the cellular baseband processor 1224, the application processor 1206, or both. Component 198 may be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1204 may include various components configured for various functions. In one configuration, device 1204, and in particular cellular baseband processor 1224 and / or application processor 1206, may include: means for obtaining first map information associated with at least one of a positioning session or an RF sensing session; means for selecting a first set of TRPs or at least one of at least one second network nodes for at least one of the positioning session or the RF sensing session based on the first map information; and means for configuring the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session. In another configuration, the device 1204, and in particular the cellular baseband processor 1224 and / or the application processor 1206, may include means for: obtaining map information associated with at least one of a positioning session or an RF sensing session for the UE; and sending an indication of a first set of TRPs or at least one of the at least one network node for at least one of the positioning session or the RF sensing session based on the map information. The means may be the component 198 of the device 1204 configured to perform the functions recited by the means. As described above, the device 1204 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.

[0176] Figure 13Diagram 1300 illustrates an example hardware implementation for a network entity 1302. Network entity 1302 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1302 may include at least one of a CU 1310, a DU 1330, or a RU 1340. For example, depending on the layer functionality handled by component 199, network entity 1302 may include a CU 1310; both the CU 1310 and the DU 1330; each of the CU 1310, the DU 1330, and the RU 1340; the DU 1330; both the DU 1330 and the RU 1340; or the RU 1340. CU 1310 may include a CU processor 1312. CU processor 1312 may include on-chip memory 1312′. In some aspects, CU 1310 may also include an additional memory module 1314 and a communication interface 1318. The CU 1310 communicates with the DU 1330 via a midhaul link, such as an F1 interface. The DU 1330 may include a DU processor 1332. The DU processor 1332 may include on-chip memory 1332′. In some aspects, the DU 1330 may also include an additional memory module 1334 and a communication interface 1338. The DU 1330 communicates with the RU 1340 via a fronthaul link. The RU 1340 may include a RU processor 1342. The RU processor 1342 may include on-chip memory 1342′. In some aspects, the RU 1340 may also include an additional memory module 1344, one or more transceivers 1346, an antenna 1380, and a communication interface 1348. The RU 1340 communicates with the UE 104. The on-chip memories 1312′, 1332′, 1342′ and the additional memory modules 1314, 1334, 1344 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 1312, 1332, and 1342 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0177] Figure 1414 is a diagram illustrating an example of a hardware implementation for a network entity 1460. In one example, the network entity 1460 may be within the core network 120. The network entity 1460 may include a network processor 1412. The network processor 1412 may include on-chip memory 1412′. In some aspects, the network entity 1460 may also include an additional memory module 1414. The network entity 1460 communicates with the CU 1402 and the anchor node 1404, which is an example of the anchor node 704B, via a network interface 1480, either directly (e.g., a backhaul link) or indirectly (e.g., via an RIC). The on-chip memory 1412′ and the additional memory module 1414 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1412 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the processor when executing software.

[0178] As discussed above, component 199 may be configured to: obtain first map information associated with at least one of a positioning session or an RF sensing session; select a first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session based on the first map information; and configure the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session. Component 199 may be configured to perform a combination Figures 8 and 9 The various aspects described in the flowchart in and / or by the coordinator UE 704A or the target UE 704E in 7A to 7BAny of the aspects performed in the communication flow in . Component 199 may be within processor 1412. Component 199 may be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1460 may include various components configured for various functions. In one configuration, network entity 1460 may include: means for obtaining first map information associated with at least one of a positioning session or an RF sensing session; means for selecting a first set of TRPs or at least one of at least one second network nodes for at least one of the positioning session or the RF sensing session based on the first map information; and means for configuring the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session. A component may be component 199 of network entity 1460 configured to perform the functions recited by the component.

[0179] Various aspects relate generally to positioning systems. Some aspects relate more specifically to positioning or RF sensing utilizing map information. In some examples, a coordinator node may obtain map information about the environment of a target entity for which a positioning or sensing session is to be performed. Based at least on the map information, the coordinator node may select and / or configure a set of transmit receive points (TRPs) or anchor nodes to be used or not to be used for the positioning or sensing session. For example, the coordinator node may activate or deactivate the transmission or reception of reference signals (e.g., positioning reference signals (PRS)) from the set of TRPs or anchor nodes based on the configuration. The coordinator node may select and / or configure a set of TRPs for uplink or downlink based positioning or sensing, and may select and / or configure anchor nodes for sidelink based positioning or sensing. In some aspects, a target UE may provide an indication of a set of TRPs or anchor nodes to be used for its positioning or sensing session based on its map information.

[0180] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. By utilizing map information associated with the specific environment in which the target entity is located, the coordinator node may determine TRPs or anchor nodes that do not have a direct line of sight to the target entity due to obstacles in the environment indicated by the map information. The coordinator node may disable the transmission or reception of reference signals from such TRPs or anchor nodes. By disabling the transmission or reception of reference signals from such TRPs or anchor nodes, such TRPs or anchor nodes (and target entities configured to detect such reference signals) may save computing resources (e.g., processing cycles, memory, power, etc.). The coordinator node may also enable the transmission or reception of reference signals from TRPs or anchor nodes that have a direct line of sight to the target entity. By enabling the transmission or reception of reference signals from such TRPs or anchor nodes, the positioning of the target entity may be determined more accurately.

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

[0182] 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 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 does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean 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 there is no need for a specific or immediate time limit for the action to occur. The word "exemplary" is used in this article 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, which may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “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, B, and C, where any such combination may include one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from a second device or sends data to a 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. A device configured to "output" data (such as, transmit, signal or message) may (for example) send the data with a transceiver, or may transmit the data to a device that sends the data. A device configured to "obtain" data (such as, transmit, signal or message) may (for example) receive the data with a transceiver, or may obtain the data from a device that receives the data. The information stored in the memory includes instructions and / or data. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims.Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not intended to replace the word "component." Thus, no claim element will be construed as part-plus-function unless the element is explicitly recited using the phrase "means for..."

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

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

[0185] Aspect 1 is a method for wireless communication at a first network node, the method comprising: obtaining first map information associated with at least one of a positioning session or an RF sensing session; selecting a first set of TRPs or at least one of at least one second network nodes for the positioning session or at least one of the RF sensing session based on the first map information; and configuring the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session.

[0186] Aspect 2 is a method according to Aspect 1, wherein configuring the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session includes: sending an indication of the configuration of the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session to the first set of TRPs or at least one of the at least one second network nodes.

[0187] Aspect 3 is a method according to any one of aspects 1 and 2, wherein the first network node is a first user equipment (UE) configured to coordinate at least one of the positioning session or the RF sensing session for the at least one second network node, and wherein the at least one second network node is a second UE.

[0188] Aspect 4 is a method according to any one of aspects 1 and 2, wherein the first network node is at least one of an LMF or an SnMF.

[0189] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: receiving information indicating the first set of TRPs or at least one of the at least one second network nodes from a target UE, wherein the information is based on second map information associated with the target UE, and wherein the positioning session or the at least one of the RF sensing sessions is performed for the target UE.

[0190] Aspect 6 is a method according to any one of aspects 1 to 5, the method further comprising: updating the priority of at least one of the first set of TRPs of which the target UE is to measure the PRS or the at least one second network node based on the information.

[0191] Aspect 7 is a method according to aspect 6, the method further comprising: sending an indication to disable PRS transmission to at least one of the first set of TRPs or the at least one second network node based on the information.

[0192] Aspect 8 is a method according to any one of Aspects 1 to 7, the method further comprising: receiving an indication that a target UE for which at least one of the positioning session or the RF sensing session is performing is discarding PRS measurements within a specific time unit, wherein the indication is based on second map information associated with the target UE.

[0193] Aspect 9 is a method according to aspect 8, wherein the specific time unit includes at least one of the following: a certain number of time slots; a certain number of subframes; a certain number of milliseconds; or a certain number of seconds.

[0194] Aspect 10 is a method according to any one of Aspects 1 to 9, the method further comprising: receiving an indication from the target UE to discard PRS resources for one or more TRPs in the first set of TRPs or at least one of the at least one second network nodes; and sending an indication to discard the PRS resources for the one or more TRPs in the first set of TRPs or at least one of the at least one second network nodes.

[0195] Aspect 11 is the method according to aspect 10, wherein receiving the indication comprises receiving the indication via one of LPP signaling or SLPP signaling.

[0196] Aspect 12 is a method according to any one of aspects 1 to 11, wherein the ID of each TRP in the first set of TRPs is associated with the ID of each PRS in the first set of PRSs.

[0197] Aspect 13 is the method according to aspect 12, wherein the PRS comprises at least one of: UE-TRANPRS; or SL PRS.

[0198] Aspect 14 is a method according to any one of Aspects 1 to 13, the method further comprising: determining a first position of a target UE for which at least one of the positioning session or the RF sensing session is performed, wherein selecting the first set of TRPs or at least one of the at least one second network nodes comprises: selecting the first set of TRPs or at least one of the at least one second network nodes based on the first position and the map information.

[0199] Aspect 15 is a method according to Aspect 14, which further includes: determining a second location of the target UE; selecting a second set of TRPs or at least one of the at least one third network nodes for at least one of the positioning session or the RF sensing session based on the second location and the map information; and configuring the second set of TRPs or at least one of the at least one third network nodes for at least one of the positioning session or the RF sensing session.

[0200] Aspect 16 is a method for wireless communication at a UE, the method comprising: obtaining map information associated with at least one of a positioning session or an RF sensing session for the UE; and sending an indication of a first set of TRPs or at least one of at least one network nodes for at least one of the positioning session or the RF sensing session based on the map information.

[0201] Aspect 17 is a method according to aspect 16, further comprising discarding PRS measurements for at least one of the first set of TRPs or the at least one network node within a specific time unit.

[0202] Aspect 18 is a method according to aspect 17, wherein the indication indicates that the UE is discarding the PRS measurement for at least one of the first set of TRPs or the at least one network node within the specific time unit.

[0203] Aspect 19 is a method according to any one of aspects 17 and 18, wherein the specific time unit includes: a certain number of time slots; a certain number of subframes; a certain number of milliseconds; or a certain number of seconds.

[0204] Aspect 20 is a method according to any one of aspects 16 to 19, wherein the indication indicates dropping PRS resources for at least one of the first set of TRPs or the at least one network node.

[0205] Aspect 21 is a method according to any one of aspects 16 to 20, wherein sending the indication comprises sending the indication via one of LPP signaling or SLPP signaling.

[0206] Aspect 22 is a method according to aspects 16 to 21, wherein the indication indicates that PRS transmission for at least one of the first set of TRPs or the at least one network node is to be disabled.

[0207] Aspect 23 is an apparatus for wireless communication at a first network node. The apparatus comprises: a memory; and at least one processor coupled to the memory, and the at least one processor is configured to implement any one of aspects 1 to 15 based at least in part on information stored in the memory.

[0208] Aspect 24 is the apparatus of aspect 23, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0209] Aspect 25 is an apparatus for wireless communication at a first network node, the apparatus comprising: a memory; and at least one processor coupled to the memory, and the at least one processor configured to implement any one of aspects 16 to 22 based at least in part on information stored in the memory.

[0210] Aspect 26 is the apparatus of aspect 25, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0211] Aspect 27 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 15.

[0212] Aspect 28 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 16 to 22.

[0213] Aspect 29 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 15.

[0214] Aspect 30 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 16 to 22 .

Claims

1. An apparatus for wireless communication at a first network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: obtaining first map information associated with at least one of a positioning session or a radio frequency (RF) sensing session; selecting at least one of a first set of transmit reception points (TRPs) or at least one second network node for at least one of the positioning session or the RF sensing session based on the first map information; as well as At least one of the first set of TRPs or the at least one second network node is configured for at least one of the positioning session or the RF sensing session.

2. The apparatus of claim 1 , wherein to configure at least one of the first set of TRPs or the at least one second network node for at least one of the positioning session or the RF sensing session, the at least one processor is configured to: An indication of the configuration of the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session is sent to the first set of TRPs or at least one of the at least one second network nodes.

3. The apparatus of claim 1 , wherein the first network node is a first user equipment (UE) configured to coordinate at least one of the positioning session or the RF sensing session for the at least one second network node, and wherein the at least one second network node is a second UE. 4 . The apparatus of claim 1 , wherein the first network node is at least one of a Location Management Function (LMF) or a Sensing Management Function (SnMF).

5. The apparatus of claim 1 , wherein the at least one processor is further configured to: Information indicating the first set of TRPs or at least one of the at least one second network nodes is received from a target UE, wherein the information is based on second map information associated with the target UE, and wherein the positioning session or the at least one of the RF sensing session is performed for the target UE.

6. The apparatus of claim 5, wherein the at least one processor is further configured to: A priority of at least one of the first set of TRPs for which the target UE is to measure a positioning reference signal (PRS) or the at least one second network node is updated based on the information.

7. The apparatus of claim 5, wherein the at least one processor is further configured to: An indication is sent to at least one of the first set of TRPs or the at least one second network node based on the information, indicating that PRS transmission is to be disabled.

8. The apparatus of claim 1 , wherein the at least one processor is further configured to: An indication is received that a target UE for which at least one of the positioning session or the RF sensing session is performed is configured to discard PRS measurements within a specific time unit, wherein the indication is based on second map information associated with the target UE.

9. The apparatus of claim 8, wherein the specific time unit comprises at least one of: A certain number of time slots; A certain number of subframes; a certain number of milliseconds; or A certain number of seconds.

10. The apparatus of claim 1 , further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is further configured to: receiving, from a target UE via at least one of the transceiver or the antenna, an indication to drop PRS resources for one or more TRPs in the first set of TRPs or at least one of the at least one second network node; and An indication to discard the PRS resources is sent to at least one of the one or more TRPs in the first set of TRPs or the at least one second network node via at least one of the transceiver or the antenna.

11. The apparatus of claim 10, wherein to receive the indication, the at least one processor is configured to: The indication is received via one of Long Term Evolution (LTE) Positioning Protocol (LPP) signaling or Sidelink-based Positioning Protocol (SLPP) signaling.

12. The apparatus of claim 1, wherein an identifier (ID) of each TRP in the first set of TRPs is associated with an ID of each PRS in the first set of PRSs.

13. The apparatus of claim 12, wherein the PRS comprises at least one of: UE-Terrestrial Radio Access Network (TRAN) PRS; or Sidelink (SL) PRS.

14. The apparatus of claim 1 , wherein the at least one processor is further configured to: determining a first position of a target UE, wherein the at least one of the positioning session or the RF sensing session is for the target UE, Wherein, in order to select at least one of the first set of TRPs or the at least one second network node, the at least one processor is configured to: At least one of the first set of TRPs or the at least one second network node is selected based on the first location and the map information.

15. The apparatus of claim 14, wherein the at least one processor is further configured to: determining a second location of the target UE; selecting, based on the second location and the map information, at least one of a second set of TRPs or at least one third network node for at least one of the positioning session or the RF sensing session; and At least one of the second set of TRPs or the at least one third network node is configured for at least one of the positioning session or the RF sensing session.

16. 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 information stored in the memory, configured to: obtaining map information associated with at least one of a positioning session or a radio frequency (RF) sensing session for the UE; and An indication of at least one of a first set of transmit reception points (TRPs) or at least one network node for at least one of the positioning session or the RF sensing session is sent based on the map information.

17. The apparatus of claim 16, wherein the at least one processor is further configured to: Positioning Reference Signal (PRS) measurements for at least one of the first set of TRPs or the at least one network node within a specific time unit are discarded.

18. The apparatus of claim 17, wherein the indication indicates that the UE is configured to discard the PRS measurement for at least one of the first set of TRPs or the at least one network node within the specific time unit.

19. The apparatus of claim 17, wherein the specific time unit comprises at least one of: A certain number of time slots; A certain number of subframes; a certain number of milliseconds; or A certain number of seconds.

20. The apparatus of claim 16, wherein the indication indicates discarding of PRS resources for at least one of the first set of TRPs or the at least one network node.

21. The apparatus of claim 16, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein to send the indication, the at least one processor is configured to: The indication is sent via at least one of the transceiver or the antenna via one of Long Term Evolution (LTE) Positioning Protocol (LPP) signaling or Sidelink-based Positioning Protocol (SLPP) signaling.

22. The apparatus of claim 21, wherein the indication indicates that PRS transmission for at least one of the first set of TRPs or the at least one network node is to be disabled.

23. A method of wireless communication at a first network node, the method comprising: obtaining first map information associated with at least one of a positioning session or a radio frequency (RF) sensing session; selecting at least one of a first set of transmit reception points (TRPs) or at least one second network node for at least one of the positioning session or the RF sensing session based on the first map information; as well as At least one of the first set of TRPs or the at least one second network node is configured for at least one of the positioning session or the RF sensing session.

24. The method of claim 23, wherein configuring at least one of the first set of TRPs or the at least one second network node for at least one of the positioning session or the RF sensing session comprises: An indication of the configuration of the first set of TRPs or at least one of the at least one second network nodes for at least one of the positioning session or the RF sensing session is sent to the first set of TRPs or at least one of the at least one second network nodes.

25. The method of claim 23, wherein the first network node is a first user equipment (UE) configured to coordinate at least one of the positioning session or the RF sensing session for the at least one second network node, and wherein the at least one second network node is a second UE.

26. The method of claim 23, wherein the first network node is at least one of a Location Management Function (LMF) or a Sensing Management Function (SnMF).

27. A method of wireless communication at a user equipment (UE), the method comprising: obtaining map information associated with at least one of a positioning session or a radio frequency (RF) sensing session for the UE; as well as An indication of at least one of a first set of transmit reception points (TRPs) or at least one network node for at least one of the positioning session or the RF sensing session is sent based on the map information.

28. The method according to claim 27, further comprising: Positioning Reference Signal (PRS) measurements for at least one of the first set of TRPs or the at least one network node within a specific time unit are discarded.

29. The method of claim 28, wherein the indication indicates that the UE is discarding the PRS measurements for at least one of the first set of TRPs or the at least one network node within the specific time unit.

30. The method of claim 28, wherein the specific time unit comprises at least one of: A certain number of time slots; A certain number of subframes; a certain number of milliseconds; or A certain number of seconds.

Images