Positioning reference unit information network

Abstract

A wireless device may receive a set of positioning signals from at least one of a user equipment (UE), a first network node, or a positioning reference unit (PRU). The wireless device may measure the set of positioning signals. The wireless device may send a PRU tag assist report for the first network node or the second network node. The PRU tag assisted report may include a set of positioning measurements based on the measured set of positioning signals. The PRU tag assistance report may include PRU assistance information associated with measuring the set of positioning signals. The wireless device may include a PRU. The PRU may be a UE or a mobile TRP having a known and fixed position when the PRU receives the positioning signal. The positioning signal may include at least one of a positioning reference signal (PRS) or a sounding reference signal (SRS).

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. non-provisional patent application serial number 18 / 169,837, entitled “POSITIONING REFERENCE UNIT INFORMATION NETWORKS,” filed on February 15, 2023, which is expressly incorporated herein by reference in its entirety. Technical Field

[0002] The present disclosure relates generally to communication systems, and more particularly to positioning systems utilizing positioning reference units (PRUs). Background Art

[0003] 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 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), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and time division synchronous code division multiple access (TD-SCDMA).

[0004] 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, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued evolution of mobile broadband promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., for 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. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ them. Summary of the Invention

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

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a positioning reference unit (PRU). The apparatus may receive a positioning signal set from at least one of a user equipment (UE), a first network node, or a second PRU. The apparatus may measure the positioning signal set. The apparatus may send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a positioning measurement set based on the measured positioning signal set. The PRU tag assistance report may include PRU assistance information associated with measuring the positioning signal set. The apparatus may send a second positioning signal set to at least one of the UE, the first network node, or the second PRU. The apparatus may send second PRU assistance information associated with the second positioning signal set to at least one of the first network node or the second network node. The PRU tag assistance report may include the second PRU assistance information associated with the second positioning signal set.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a UE. The apparatus may transmit a sounding reference signal (SRS) set for a PRU. The apparatus may receive a PRU tag assistance report from a network node. The PRU tag assistance report may include a positioning measurement set based on the SRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a first network node. The apparatus may transmit a positioning reference signal (PRS) set for a PRU. The apparatus may receive a PRU tag assistance report from a second network node. The PRU tag assistance report may include a positioning measurement set based on the PRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set.

[0009] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may include a network node. The network node may include a location management function (LMF). The apparatus may send a request to a PRU for a PRU tag assistance report associated with a set of positioning signals transmitted or received by the PRU. The apparatus may receive the PRU tag assistance report including a set of PRU assistance information associated with the set of positioning signals.

[0010] 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

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

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

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

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

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

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

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

[0018] Figure 5 is a diagram illustrating an example of a Positioning Reference Unit (PRU) configured to communicate positioning signals with other wireless devices, such as another PRU, a Transmit Reception Point (TRP), a UE, or a Location Management Function (LMF).

[0019] Figure 6 is a connection flow diagram illustrating an example of a UE / PRU set and a PRU set configured to perform positioning according to various aspects of the present disclosure.

[0020] Figure 7 is a connection flow diagram illustrating an example of a network node / PRU set and a PRU set configured to perform positioning according to various aspects of the present disclosure.

[0021] Figure 8 is a flow chart of a method of wireless communication.

[0022] Figure 9 is a flow chart of a method of wireless communication.

[0023] Figure 10 is a flow chart of a method of wireless communication.

[0024] Figure 11 is a flow chart of a method of wireless communication.

[0025] Figure 12 is a flow chart of a method of wireless communication.

[0026] Figure 13 is a flow chart of a method of wireless communication.

[0027] Figure 14 is a flow chart of a method of wireless communication.

[0028] Figure 15 is a flow chart of a method of wireless communication.

[0029] Figure 16 is a flow chart of a method of wireless communication.

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

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

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

[0033] The following description refers to certain specific examples for the purpose of describing the innovative aspects of the present disclosure. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. Some or all of the examples described may be implemented in a system capable of implementing a system in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, the Bluetooth standard as defined by the Bluetooth Special Interest Group (SIG), or the like. ®The examples may be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals in accordance with one or more of the Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards, or standards promulgated by the Third Generation Partnership Project (3GPP). The described examples may be implemented in any device, system, or network capable of transmitting and receiving RF signals in accordance with one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), spatial division multiple access (SDMA), rate splitting multiple access (RSMA), multi-user shared access (MUSA), single-user (SU) multiple-input multiple-output (MIMO), and multi-user (MU) MIMO. The described examples may also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), a wireless metropolitan area network (WMAN), or an Internet of Things (IoT) network.

[0034] A user equipment (UE) can be configured to perform positioning relative to a network node, such as a transmit receive point (TRP) of a base station. The UE can transmit a set of sounding reference signals (SRS) to the network node for measurement, and the network node can transmit a set of positioning reference signals (PRS) for measurement by the UE. The measurements can be used to calculate the UE's position relative to one or more network nodes with known locations. For example, the UE can measure the round-trip time (RTT) between the transmission of an SRS from the UE to a network node and the transmission of a PRS from the network node back to the UE to calculate the distance between the UE and the network node. The UE can triangulate its position by calculating the distance to two or more network nodes with known locations.

[0035] Efficient positioning models, such as those trained using artificial intelligence machine learning (AIML), can be used to perform positioning more efficiently. For example, a positioning model can be trained using a set of inputs (e.g., measurements of a reference signal (RS) set from a transmitting wireless device (such as a base station), antenna orientation, and network synchronization error) and a set of expected labels (e.g., the position of a receiving wireless device that received the RS set, and the angle of arrival (AoA) of the RS set received by the receiving wireless device). After the positioning model has been trained, it can be used to calculate positioning information, such as the position of the receiving wireless device or intermediate measurements (e.g., AoA, reference signal time difference (RSTD), and line-of-sight (LOS) identification) that can be used to calculate the position of the receiving wireless device based on measurements of the RS set. However, obtaining accurate data or labels to train the positioning model can be difficult because the UE or TRP may not be configured to share such assistance information with other wireless devices. These other wireless devices may be distributed by different UE vendors or different network (NW) operators and therefore may not have access to such assistance data.

[0036] A Positioning Reference Unit (PRU) can be configured to emulate a UE or network node when performing positioning. This allows the PRU to act as a network node when communicating with a UE (e.g., by sending a set of PRSs to the UE and receiving / measuring a set of SRSs from the UE), and to act as a UE when communicating with a network node (e.g., by sending a set of SRSs to the network node and receiving / measuring a set of PRSs from the network node). The PRU can be used by the UE, network node, and / or other PRUs to generate positioning information, such as positioning measurements or location information, and can use one or more protocols to share PRU label assistance reports to collect and share data used to train positioning models, including input data and output labels. A label is a computational expected result from an input set that can be used to train the positioning model. The PRU can be configured to act as a UE fixed at a known location when performing positioning, as well as as a mobile network node fixed at a known location when performing positioning, to help enrich and diversify the training data for uplink (UL) and downlink (DL) inputs and labels used to train the positioning model. The PRU tag assistance report shared by the PRU may include the private location and proprietary information of the PRU, such as the PRU's location, beam angle information of the transmitted or received positioning signal, antenna information used to transmit or receive positioning signals, or PRU sensor information. The information in the PRU tag assistance report can be used to assist the UE or network node in obtaining tags for training positioning models without the network vendor, network operator, or UE vendor disclosing proprietary information about their equipment or infrastructure.

[0037] A wireless device (e.g., configured to emulate a PRU of a UE or a network node when performing positioning) may receive a set of positioning signals from at least one of a UE, a first network node, or a PRU. The wireless device may measure the set of positioning signals. The wireless device may send a PRU tag assistance report to the first network node or a second network node. The PRU tag assistance report may include a set of positioning measurements based on the measured set of positioning signals. The PRU tag assistance report may include PRU assistance information associated with measuring the set of positioning signals. The second network node may send a request for a PRU tag assistance report to the wireless device. The second network node may receive the PRU tag assistance report. The second network node may send at least a portion of the received PRU tag assistance report to the UE or network node to assist in training or utilizing a positioning model. The UE may send a set of sounding reference signals (SRS) for the wireless device. The UE may receive the PRU tag assistance report from the first network node or the second network node. The first network node may send a set of positioning reference signals (PRS) for the wireless device. The first network node may receive a PRU tag assistance report from the second network node or the wireless device.

[0038] Various aspects generally relate to sharing PRU tag assistance reports with wireless devices, such as PRUs, UEs, and / or network nodes. Some aspects more specifically relate to using PRU tag assistance report data collected by one or more PRUs to train one or more positioning models. The PRUs may communicate with the wireless devices via Long Term Evolution (LTE) Positioning Protocol (LPP) Annex (LPPa) messages. The PRUs may communicate with the wireless devices via New Radio (NR) Positioning Protocol (NRPP) Annex (NRPPa) messages. In this way, the PRUs may collect assistance information, such as the PRU's position, beam angle, antenna delay, or group delay, and may send the assistance information to an entity that trains the positioning model for accurate positioning.

[0039] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by configuring PRUs to share PRU assistance information in PRU tag assistance reports, a positioning wireless device, such as a UE or network node, can collect training data for training a positioning model, or for using the positioning model to calculate the position of the wireless device or calculate intermediate values ​​(e.g., AoA, RSTD) that can be used to calculate the position of the wireless device. In some examples, by configuring PRUs to share PRU assistance information in PRU tag assistance reports, a UE or network node can collect training data for training a positioning model while maintaining privacy and proprietary information of the UE or network node using infrastructure supporting PRU communication.

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

[0041] Several aspects of telecommunications systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, "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.

[0042] As an example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform the 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 to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, or any combination thereof.

[0043] Thus, in one or more example aspects, implementations, and / or use cases, the functionality described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. A storage medium can 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.

[0044] While aspects, implementations, and / or use cases are described herein through the lens of a few examples, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may arise via integrated chip implementations and other non-module component-based devices (e.g., end-user devices, vehicles, communications equipment, computing devices, industrial equipment, retail / purchase equipment, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically targeted at use cases or applications, the examples described may have broad applicability. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques described herein. In some practical settings, devices incorporating the described aspects and features 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 involve 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.

[0045] 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 the network, a radio access network (RAN) node, a core network node, a network element, or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functions can be implemented in a converged or disaggregated architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell) can be implemented as a converged base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0046] 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 disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across 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).

[0047] 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 utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration 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 the functionality of at least one unit, which enables flexibility in network design. The 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.

[0048] Figure 1 FIG100 is a diagram 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, a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CUs 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as the F1 interface. The DUs 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RUs 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.

[0049] Each of the units (i.e., CU 110, DU 130, RU 140, as well as 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 the 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 the 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 the wireless transmission medium.

[0050] 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 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 implementations, the CU 110 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0051] 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 also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured for signal communication with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0052] 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 Transforms (FFTs), Inverse FFTs (iFFTs), 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-plane and user-plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0053] 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 instantiating virtualized network elements) via cloud computing platform interfaces (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the 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 the 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 .

[0054] 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 via an interface (e.g., via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and an O-eNB with the near-RT RIC 125.

[0055] 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. This 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 execute corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or through the creation of RAN management policies (such as A1 policies).

[0056] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides a UE 104 with access to core network 120. 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 known as 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 a total of up to Yx MHz (x component carriers) for transmission in each direction. These carriers may or may not be adjacent to each other. Carrier allocation 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).

[0057] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. D2D communication links 158 may utilize DL / UL wireless wide area network (WWAN) spectrum. D2D communication links 158 may utilize 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 via various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0059] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, and so on, based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 extends beyond 6 GHz, FR1 is often (and interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often (and interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0060] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range 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.

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

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

[0063] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, 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).

[0064] 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 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Locating the UE 104 may involve signal measurements, position estimates, and optionally velocity calculations based on these measurements. 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., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell identifier (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.

[0065] 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, a utility 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 rate 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.

[0066] Reference again Figure 1 In certain aspects, the UE 104 or base station 102 may include a PRU component 198 that may be configured to receive a set of positioning signals from at least one of the UE, a first network node, or a PRU. The PRU component 198 may be configured to measure the set of positioning signals. The PRU component 198 may be configured to send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a positioning measurement set based on the measured set of positioning signals. The PRU tag assistance report may include PRU assistance information associated with measuring the set of positioning signals. The PRU component 198 may be configured to send a second set of positioning signals to at least one of the UE, the first network node, or the second PRU. The PRU component 198 may be configured to send second PRU assistance information associated with the second set of positioning signals to at least one of the first network node or the second network node. The PRU tag assistance report may include the second PRU assistance information associated with the second set of positioning signals. The first set of positioning signals may be an SRS set or a PRS set. The second set of positioning signals may be an SRS set or a PRS set. The second network node may be a LMF, such as LMF 166 .

[0067] In certain aspects, the UE 104 may have a UE component 199 that may be configured to transmit a sounding reference signal (SRS) set for a PRU. The UE component 199 may be configured to receive a PRU tag assistance report from a network node. The PRU tag assistance report may include a positioning measurement set based on the SRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set. The UE component 199 may be configured to receive a PRS set from the PRU. The UE component 199 may be configured to measure the PRS set. The UE component 199 may be configured to calculate the UE's position based on the measured PRS set and the positioning measurement set. The PRU tag assistance report may include PRU assistance information associated with the PRS set from the PRU.

[0068] In certain aspects, the base station 102 may have a BS component 197 that may be configured to transmit a positioning reference signal (PRS) set for a PRU. The BS component 197 may be configured to receive a PRU tag assistance report from a second network node, such as the LMF 166. The PRU tag assistance report may include a positioning measurement set based on the PRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set.

[0069] In certain aspects, the base station 102 may include an LMF component 196 that may be configured to send a request for a PRU tag assistance report to a PRU associated with a set of positioning signals transmitted or received using the PRU. The LMF component 196 may receive a PRU tag assistance report that includes a set of PRU assistance information associated with the set of positioning signals.

[0070] Using one or more of the PRU component 198, the UE component 199, the BS component 197, and / or the LMF component 196, the PRUs can be configured to share PRU tag assistance reports having PRU assistance information associated with the positioning signal set, such as the location of the PRU, beam angle information, antenna orientation information, or sensor information, to assist the UE or base station in tagging for training a positioning model, for example, by using artificial intelligence machine learning (AIML) techniques to train the model using the input set and the expected tag set. This sharing of PRU assistance information can be performed without the network vendor, network operator, UE vendor, or UE operator disclosing proprietary information about their equipment, infrastructure, or location information.

[0071] 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 2CFIG250 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) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A 、 Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, with subframe 4 configured with slot format 28 (mostly DL), where D stands for DL, U stands for UL, and F stands for flexible use between DL / UL, and subframe 3 configured with slot format 1 (all UL). While subframes 3 and 4 are shown with 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 a received slot format indicator (SFI), either dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling. Note that the following description also applies to the 5G NR frame structure as TDD.

[0072] Figures 2A to 2D This example illustrates a frame structure, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. Symbols on the DL may be CP-orthogonal frequency division multiplexing (OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or discrete Fourier transform (DFT)-spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe depends 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.

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

[0074]

[0075] 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. Therefore, for normal CP and parameter set µ, there are 14 symbols / slot and 2 µ time slots / subframe. The subcarrier spacing can be equal to ,in For parameter sets 0 to 4. Therefore, the subcarrier spacing for parameter set µ=0 is 15 kHz, and the subcarrier spacing for parameter set µ=4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set µ=2 with 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67µs. Within a frame set, there may be one or more different bandwidth parts (BWPs) frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0076] A resource grid can be used to represent the frame structure. Each slot consists of 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.

[0077] 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 one specific 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 beamforming RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0078] Figure 2BExamples of various downlink 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 consists of six resource element groups (REGs), with each REG consisting of 12 contiguous REs within an OFDM symbol of a RB. The PDCCH within a BWP is referred to as a control resource set (CORESET). During PDCCH monitoring opportunities within a CORESET, the UE is configured to monitor PDCCH search spaces (e.g., common search space, UE-specific search space) for PDCCH candidates with different DCI formats and 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 specific subframes of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of specific subframes of a 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 known 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.

[0079] 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 can transmit the DM-RS for the physical uplink control channel (PUCCH) and the DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and on the specific PUCCH format used. The UE can transmit a sounding reference signal (SRS). The SRS can be transmitted in the last symbol of the subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb structures within the comb structure. The SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

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

[0081] Figure 3 Figure 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 the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with 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.

[0082] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping onto the signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-order phase-shift keying (M-PSK), 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 the time-domain OFDM symbol stream. The OFDM stream is spatially precoded 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 from 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.

[0083] 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 performs spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then 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 may 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.

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

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

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

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

[0088] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport 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 an ACK and / or NACK protocol to support HARQ operations.

[0089] 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 PRU component 198.

[0090] 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 UE component 199.

[0091] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Various aspects related to the PRU component 198.

[0092] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Various aspects related to BS component 197.

[0093] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Various aspects related to the LMF component 196.

[0094] Figure 4 4 is a diagram illustrating an example of positioning based on reference signal measurements. Wireless device 402 may be a UE, a base station, or a positioning reference unit (PRU). Wireless device 404 may be a UE, a base station, or a PRU. Wireless device 406 may be a UE, a base station, or a PRU. Wireless device 402 may be referred to as a positioning target wireless device, and the position of the positioning target wireless device may be calculated based on measurements of one or more reference signals. Wireless device 404 and wireless device 406 may be referred to as positioning neighboring wireless devices, and the positions of the positioning neighboring wireless devices may be known and used to calculate the position of wireless device 402. Wireless device 404 may be at time T. SRS_TX The SRS 412 is sent to the wireless device 406. The wireless device 404 may PRS_RX A positioning reference signal (PRS) 410 is received from wireless device 406. SRS 412 may be a UL-SRS. PRS 410 may be a DL-PRS. In some aspects, wireless device 402 may be a TRP and wireless device 406 may be a TRP, both of which may be configured to transmit the DL-PRS to wireless device 404. Wireless device 404 may be a UE configured to transmit the UL-SRS to wireless device 402 and wireless device 406.

[0095] The wireless device 406 may be configured to receive a signal at time T SRS_RXSRS 412 is received from wireless device 404 and at time T PRS_TX The PRS 410 is sent to the wireless device 404. The wireless device 404 may receive the PRS 410 before sending the SRS 412. The wireless device 404 may send the SRS 412 before receiving the PRS 410. The wireless device 404 may send the SRS 412 in response to receiving the PRS 410. The wireless device 406 may send the PRS 410 in response to receiving the SRS 412. A positioning server (e.g., location server 168), the wireless device 404, or the wireless device 406 may determine the location of the wireless device 404 based on the || T SRS_RX – T PRS_TX | – |T SRS_TX –T PRS_RX || to determine the round trip time (RTT) 414. Multi-RTT positioning can utilize Rx-Tx time difference measurements (ie, |T SRS_TX – T PRS_RX |) and PRS reference signal received power (RSRP) (PRS-RSRP), and Rx-Tx time difference measurements (i.e., |T SRS_RX – T PRS_TX |) and SRS-RSRP. Wireless device 404 may use assistance data received from a positioning server, wireless device 402, and / or wireless device 406 to measure Rx-Tx time difference measurements and / or PRS-RSRP of received signals. Wireless device 402 and wireless device 406 may use assistance data received from a positioning server to measure Rx-Tx time difference measurements and / or SRS-RSRP of received signals. These measurements may be used at the positioning server or wireless device 404 to determine RTT, which may be used to estimate the location of wireless device 404. Other methods for determining RTT are possible, such as, for example, using time difference of arrival (TDOA) measurements, such as DL-TDOA and / or UL-TDOA measurements.

[0096] DL-AoD positioning can utilize the measured PRS-RSRP of signals transmitted from multiple wireless devices (such as wireless device 402 and wireless device 406) and received at wireless device 404. AoD positioning can also be referred to as DL-AoD positioning, where PRS is a DL signal. Wireless device 404 can use assistance data received from a positioning server to measure the PRS-RSRP of the received signals, and the resulting measurements can be used together with the azimuth angle of departure (A-AoD), the zenith angle of departure (Z-AoD), and other configuration information to locate wireless device 404 relative to neighboring wireless devices (such as wireless device 402 and wireless device 406) that transmit PRS.

[0097] DL-TDOA positioning may utilize DL reference signal time difference (RSTD) and / or PRS-RSRP of signals received at the wireless device 404 from multiple wireless devices, such as the wireless device 402 and the wireless device 406. The wireless device 404 may measure the RSTD and / or PRS-RSRP of the received PRS signals using assistance data received from a positioning server, and the resulting measurements may be used along with other configuration information to position the wireless device 404 relative to neighboring wireless devices transmitting PRS, such as the wireless device 402 and the wireless device 406.

[0098] UL-TDOA positioning may utilize UL relative time of arrival (RTOA) and / or SRS-RSRP of signals transmitted from wireless device 404 at multiple wireless devices, such as wireless device 402 and wireless device 406. Wireless devices, such as wireless device 402 and wireless device 406, may measure RTOA and / or SRS-RSRP of received signals using assistance data received from a positioning server, and the resulting measurements may be used along with other configuration information to estimate the position of wireless device 404.

[0099] UL-AoA positioning may utilize measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of signals transmitted from wireless device 404 at multiple wireless devices, such as wireless device 402 and wireless device 406. Wireless device 402 and wireless device 406 may measure the A-AoA and Z-AoA of received signals using assistance data received from a positioning server, and the resulting measurements may be used along with other configuration information to estimate the position of wireless device 404.

[0100] Additional positioning methods may be used to estimate the position of the wireless device 404, such as, for example, UL-AoD and / or DL-AoA at the wireless device 404. Note 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.

[0101] Figure 5 5 is a diagram illustrating an example of a PRU 504 configured to communicate positioning signals with a TRP / PRU 506, a UE / PRU 502, and an LMF 508. In one aspect, the PRU 504 can be configured to emulate a UE when communicating with the TRP / PRU 506, and can be configured to emulate the TRP / PRU 502 when communicating with the UE / PRU 506. In another aspect, the PRU 504 can be configured to emulate a UE when performing positioning with the TRP / PRU 506 via signals 514, and the PRU 504 can be configured to emulate a TRP when performing positioning with the UE / PRU 502 via signals 512. The PRU 504 can be configured to send an SRS set to the TRP / PRU 506, and can be configured to receive and measure a PRS set from the TRP / PRU 506. The PRU 504 may be configured to transmit a PRS set to the UE / PRU 502 and may be configured to receive and measure an SRS set from the UE / PRU 502. The UE / PRU 502 and the TRP / PRU 506 may be configured to perform positioning with each other via signal 522. The LMF 508 may be configured to coordinate positioning with the UE / PRU 502 via signal 520, with the PRU 504 via signal 518, and with the TRP / PRU 506 via signal 516. The UE / PRU 502 may be configured to communicate with the LMF 508 via the LPPa protocol (using LPPa messages). The TRP / PRU 506 may be configured to communicate with the LMF 508 via the NRPPa protocol (using NRPPa messages). The PRU 504 may be configured to communicate with the LMF 508 using either the LPPa protocol or the NRPPa protocol, as appropriate. For example, the PRU 504 may be configured to share PRU tag assistance reports based on SRS measurements with the LMF 508 via the NRPPa protocol, and may be configured to share PRU tag assistance reports based on PRS measurements with the LMF 508 via the LPPa protocol.

[0102] Although one TRP, one PRU, and one UE are shown in diagram 500, in other aspects of the present disclosure, multiple TRPs, multiple PRUs, and / or multiple UEs may be configured to perform positioning with each other. For example, UE / PRU 502 may be configured to perform positioning with multiple TRPs, multiple PRUs, or both TRP / PRU 506 and PRU 504. In another example, PRU 504 may be configured to perform positioning with multiple TRPs and / or multiple UEs. UE / PRU 502 may be a UE, a PRU, or a PRU configured to operate as a UE when performing positioning with another wireless device. TRP / PRU 506 may be a TRP, a PRU, or a PRU configured to operate as a TRP when performing positioning with another wireless device.

[0103] PRUs, such as the PRU 504, the UE / PRU 502, and / or the TRP / PRU 506, can be configured to share PRU tag assistance reports with the LMF 508 to utilize the measurement data and tags to train a positioning model, or to use the positioning model to calculate results using the measurement data. The LMF 508 can be configured to share at least a portion of the received PRU tag assistance reports with a UE or network node so that the UE or network node can train or use an AIML model. A wireless device configured to train a positioning model can use the measurement data and tag data to train the positioning model to calculate results using the measurement data. In one aspect, a first wireless device can train the positioning model to calculate a target location for a second wireless device. The first wireless device can input measurements (such as the channel impulse response (CIR) of a measured PRS or the CIR of a measured SRS) and direct tags (such as the known location of the second wireless device) into the positioning model to train the positioning model to calculate the location. In another aspect, the first wireless device can train the positioning model to calculate intermediate measurements that can be used to calculate the target location of the second wireless device. The first wireless device can input measurements (such as the measured CIR of a PRS or the measured CIR of an SRS) and intermediate signatures (such as known positioning timing, a known angle of arrival (AoA) of a positioning signal, a known angle of departure (AoD) of a positioning signal, or a line-of-sight (LOS) path to a second wireless device) into a positioning model to train the positioning model to calculate intermediate measurements that can be used to calculate the position of the second wireless device. Once the positioning model is trained, the first wireless device can calculate direct results or intermediate results based on the one or more input measurements. The first wireless device can use the intermediate results to calculate a target position for the second wireless device, for example, by using a Chans algorithm, a Kalman filter (KF) algorithm, or some other algorithm that uses the intermediate results to calculate the target position.

[0104] The PRU 504 may collect various data to train or use a positioning model. In some aspects, the PRU may collect DL measurements and / or UL measurements of positioning signals, such as an SRS signal sent from the UE / PRU 502 as signal 512 or a PRS signal sent from the TRP / PRU 506 as signal 514. The training data may include reference signal measurements, clean labels (e.g., labels with an accuracy above a threshold level), noisy labels (e.g., labels with an accuracy below a threshold level), and / or PRU assistance information (e.g., PRU location, BWP, number of TRPs, beam information, beam angle information, PRS configuration, SRS configuration).

[0105] The PRU may have one or more high-accuracy sensors that can be used to calculate the PRU's position. For example, the PRU may have a high-accuracy GPS, GNSS equipment, LIDAR sensor, or other sensor that can be used to calculate the PRU's position with high accuracy. The position calculated using such high-accuracy equipment can be used as a tag to train the positioning model. The PRU can calculate the ground truth by collecting other PRU assistance information associated with the positioning signal, such as time of arrival (ToA), reference signal time difference (RSTD), line-of-sight (LOS) identification, or non-line-of-sight (NLOS) identification. A PRU (such as the PRU 504, UE / PRU 502, or TRP / PRU 506) can be configured to share some private or proprietary information, such as its private position, beam angle information, antenna orientation, or other sensor information, to help the UE or network node collect accurate tags for training the positioning model.

[0106] A wireless device (e.g., configured to emulate a PRU of a UE or a network node when performing positioning) may receive a set of positioning signals from at least one of a UE, a first network node, or a second PRU. The wireless device may measure the set of positioning signals. The wireless device may send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a set of positioning measurements based on the measured set of positioning signals. The PRU tag assistance report may include PRU assistance information associated with measuring the set of positioning signals. The wireless device may send a second set of positioning signals to at least one of the UE, the first network node, or the second PRU. The device may send second PRU assistance information associated with the second set of positioning signals to at least one of the first network node or the second network node. The PRU tag assistance report may include the second PRU assistance information associated with the second set of positioning signals. The second network node may send a request for a PRU tag assistance report to the wireless device. The second network node may receive the PRU tag assistance report. The second network node may send at least a portion of the received PRU tag assistance report to a UE or network node to assist in training or utilizing a positioning model. The UE may send a sounding reference signal (SRS) set for the wireless device. The UE may receive a PRU tag assistance report from the first network node or the second network node. The first network node may send a positioning reference signal (PRS) set for the wireless device. The first network node may receive a PRU tag assistance report from the second network node or the wireless device.

[0107] A PRU configured to share its PRU assistance data via PRU Tag Assistance Reporting enables a UE or network node to collect training data. Such training data can be used to train a positioning model with direct or intermediate tags. By sharing PRU assistance data via PRU Tag Assistance Reporting, the PRU can maintain privacy and / or proprietary information about the deployed infrastructure while allowing the UE or network node to collect training data from the PRU. Such a PRU can be equipped with high-accuracy sensors to obtain cleaner tags than other wireless devices, allowing such a PRU to be used specifically for training positioning models. In some aspects, a network TRP can be configured not to share the TRP's location, or network-side beam angle information, or network synchronization and timing errors, which can limit the ability of a wireless device such as a UE or network node to collect training data or tags for training a positioning model. A PRU or a network TRP configured to share data like a PRU can be used to collect training data without violating its configuration specifications. In some aspects, a UE or TRP can be configured to share PRU Tag Assistance Reporting information via a chip that supports such PRU functionality.

[0108] The PRU tag assistance report may include data useful for training a positioning model, such as a positioning measurement set based on a measured positioning signal set, an expected tag set, and a PRU assistance information set associated with the measured positioning signal set. A positioning measurement can be any measurement of a positioning signal, such as a PRS, SRS, or CSI-RS. The positioning measurement expected tag can be a clean tag or a noisy tag. A clean tag can have high accuracy, such as the known location of a wireless device based on GPS coordinates, or a known LOS path between the antenna of a positioning target and the antenna of a positioning neighbor. A noisy tag can have low accuracy, such as the location of a wireless device based on GNSS positioning using a sensor in a noisy environment, or an estimated AoD or AoA of the beam between the antenna of the positioning target and the antenna of a positioning neighbor. The PRU assistance information set may include metrics associated with the positioning signal set, such as BWP, number of TRPs, beam information, PRS configuration information, or SRS configuration information. The positioning measurement set and the assistance information set can be used as inputs to a positioning model, and the expected tag set can be used to train the positioning model to use at least some of these inputs to calculate a positioning result close to the expected tag.

[0109] Figure 6 FIG6 is a connection flow diagram 600 illustrating an example of a UE / PRU set 602 and a PRU set 604 configured to perform positioning on each other. The UE / PRU set 602 may include at least one UE, at least one PRU, or at least one UE and at least one PRU. The UEs in the UE / PRU set 602 may not be configured to share PRU tag assistance reports with other wireless devices, but may be configured to share measurement reports of measured positioning signals (such as measured PRSs). In some aspects, the PRUs may be implemented by UEs with known locations. In some aspects, the PRUs may be implemented by mobile TRPs with known locations. In some aspects, the UE / PRU set 602 may include PRUs configured to impersonate UEs during positioning. The network entity 606 may include a LMF. The network entity 606 may include a positioning server. In some aspects, the PRU set 604 may include the network entity 606 so that one of the PRU sets 604 can coordinate positioning between the UE / PRU set 602 and the PRU set 604.

[0110] The UEs in the UE / PRU set 602 and / or the network entity 606 may know the location of the PRU set 604 or any of the PRUs in the UE / PRU set 602. For example, the network entity 606 may have a database of known locations for each of the PRUs in the PRU set 604. In some aspects, the PRUs may calculate their locations using positioning or using other sensor / non-RF positioning methods (e.g., using high-accuracy GNSS or GNSS positioning by traveling to a known location at a pre-scheduled time) and may send their locations to the network entity 606, which may update the locations of the PRUs to other wireless devices, such as the UE / PRU set 602. In other aspects, the PRUs in the PRU set 604 may broadcast their calculated locations to other wireless devices, such as the UE / PRU set 602. In other aspects, the network entity 606 may perform positioning on the PRUs in the PRU set 604 and may then update the locations of the PRUs to other wireless devices, such as the UEs in the UE / PRU set 602.

[0111] At least one of the UE / PRU set 602 may send a request 608 for positioning to the network entity 606. The network entity 606 may receive the request 608 for positioning. The request 608 may be sent as part of an assistance data exchange of the LPPa protocol between the UE / PRU set 602 and the network entity 606. In one aspect, the UE / PRU set 602 may send an assistance exchange message including the request 608 for positioning to the network entity 606. In one aspect, the UE / PRU set 602 may send an LPPa message including the request 608 for positioning to the network entity 606. The request 608 for positioning may request the network entity 606 to configure positioning between the UE / PRU set 602 and the PRU set 604, e.g., configure an SRS set 618 and / or configure a PRS set 620.

[0112] The request for positioning 608 may include a request for the PRU to transmit a PRU tag assistance report that may be shared with at least one of the UE / PRU set 602. The request for positioning 608 may include an indication of information that may be included in the PRU tag assistance report. The request for positioning 608 may include a request for PRU positioning measurements, such as a request for measurements of an SRS set by the PRU set 604 and / or a request for measurements of a PRS set by the UE / PRU set 602. The request for positioning 608 may include a request for the network entity 606 to configure resources for positioning. In one aspect, the request for positioning 608 may include a request for the network entity 606 to configure SRS resources for the UE / PRU set 602 to transmit an SRS set 618 to the PRU set 604 and to configure SRS resources for the PRU set 604 to receive an SRS set 618. In one aspect, the request for positioning 608 may include a request to the network entity 606 to configure SRS resources for the PRU set 604 to transmit the PRS set 620 to the UE / PRU set 602 and to configure SRS resources for the UE / PRU set 602 to receive the PRS set 620 .

[0113] The request for positioning 608 may include a request for PRU assistance information. The PRU assistance information may include an indication of the location of at least one of the PRUs in the UE / PRU set 604. The PRU assistance information may include an indication of the location of at least one of the PRUs in the UE / PRU set 602. The PRU assistance information may include an indication of the beam angle associated with the set of positioning signals received or transmitted by the PRU set 604. In one aspect, the PRU assistance information may include the calculated angle of arrival (AoA) of the SRS set 618. In another aspect, the PRU assistance information may include the calculated angle of departure (AoD) of the PRS set 620. The PRU assistance information may include an indication of the beam angle associated with the set of positioning signals received or transmitted by the PRUs in the UE / PRU set 602. In one aspect, the PRU assistance information may include the calculated AoA of the PRS set 620 received by the PRUs in the UE / PRU set 602. In another aspect, the PRU assistance information may include the calculated AoA of the SRS set 618 transmitted by the PRUs in the UE / PRU set 602. The PRU assistance information may include an indication of antenna orientations associated with the PRU set 604 transmitting or receiving the positioning signal set. In one aspect, the PRU assistance information may include an orientation set of antennas for the PRU set 604 receiving the SRS set 618. In another aspect, the PRU assistance information may include an orientation set of antennas for the PRU set 604 transmitting the PRS set 620. The PRU assistance information may include an indication of antenna orientations associated with PRUs in the UE / PRU set 602 transmitting or receiving the positioning signal set. In one aspect, the PRU assistance information may include an orientation set of antennas for the PRUs in the UE / PRU set 602 receiving the PRS set 620. In another aspect, the PRU assistance information may include an orientation set of antennas for the PRUs in the UE / PRU set 602 transmitting the SRS set 618. The PRU assistance information may include an indication of group delay associated with the PRU set 604 measuring the SRS set 618. The PRU assistance information may include an indication of group delay associated with the PRUs in the UE / PRU set 602 measuring the PRS set 620. The PRU assistance information may include an indication of sensor measurements associated with the PRU set 604 measuring the SRS set 618. For example, an indication of a position calculated via a high-accuracy GNSS device, an indication of a position calculated via a high-accuracy LIDAR device, or an indication of a reference signal received power (RSRP) measured for the SRS set 618, or an indication of a round-trip time (RTT) measured for the SRS set 618. The PRU assistance information may include an indication of sensor measurements associated with the PRUs in the UE / PRU set 602 measuring the PRS set 620.The PRU assistance information may include an indication of a sensor type associated with at least one PRU in the PRU set 604. For example, an indication of a LIDAR sensor being used, or an indication of a GPS device being used. The PRU assistance information may include an indication of a sensor type associated with the PRUs in the UE / PRU set 602. The PRU assistance information may include an indication of a synchronization error associated with the PRU set 604 that measures the SRS set 618. The PRU assistance information may include an indication of a synchronization error associated with the PRUs in the UE / PRU set 602 that measures the PRS set 620. The PRU assistance information may include an indication of a Tx-Rx or Rx-Tx timing error associated with the PRU set 604 that measures the SRS set 618. The PRU assistance information may include an indication of a Tx-Rx or Rx-Tx timing error associated with the PRUs in the UE / PRU set 602 that measures the PRS set 620. The PRU assistance information may include an indication of a clock drift range associated with the PRU set 604 that measures the SRS set 618. The PRU assistance information may include an indication of a clock drift range associated with the PRUs in the UE / PRU set 602 measuring the PRS set 620 .

[0114] In response to receiving the request for positioning 608, the network entity 606 may send a PRS / SRS resource scheduling set 610 to the PRU set 604. The PRU set 604 may receive the PRS / SRS resource scheduling set 610. The PRS / SRS resource scheduling set 610 may configure the PRU set 604 to receive an SRS set 618. The PRS / SRS resource scheduling set 610 may configure the PRU set 604 to transmit a PRS set 620. The PRS / SRS resource scheduling set 610 may request that the PRU set 604 share PRU tag assistance reports with the network entity 606. Such a request may indicate what types of PRU positioning measurements and / or PRU assistance information may be included in the PRU tag assistance reports. The PRS / SRS resource scheduling set 610 may request that the PRU set 604 share admissibility / consent rules with the network entity 606. The network entity 606 may send the PRS / SRS resource scheduling set 610 via an NRPPa message. The network entity 606 may send the PRS / SRS resource scheduling set 610 as part of the NRPPa TRP information exchange and measurement exchange.

[0115] In some aspects, at least some of the PRU sets 604 may configure a PRS / SRS resource scheduling set 612 based on the PRS / SRS resource scheduling set 610. For example, some of the PRU sets 604 may be serving cells of the UE / PRU set 602. The PRU set 604 may transmit the PRS / SRS resource scheduling set 612 to the UE / PRU set 602. The UE / PRU set 602 may receive the PRS / SRS resource scheduling set 612 from the PRU set 604. The PRS / SRS resource scheduling set 612 may configure the UE / PRU set 602 to transmit an SRS set 618 to the PRU set 604. The PRS / SRS resource scheduling set 612 may configure the UE / PRU set 602 to receive a PRS set 620 from the PRU set 604. The PRU set 604 may transmit the PRS / SRS resource scheduling set 612 as an RRC configuration.

[0116] In other aspects, the network entity 606 may directly configure a PRS / SRS resource scheduling set 614 for the UE / PRU set 602. The network entity 606 may send the PRS / SRS resource scheduling set 614 to the UE / PRU set 602. The UE / PRU set 602 may receive the PRS / SRS resource scheduling set 614 from the network entity 606. The PRS / SRS resource scheduling set 614 may configure the UE / PRU set 602 to send an SRS set 618 to the PRU set 604. The PRS / SRS resource scheduling set 614 may configure the UE / PRU set 602 to receive a PRS set 620 from the PRU set 604. The network entity 606 may send the PRS / SRS resource scheduling set 614 as an RRC configuration.

[0117] In response to receiving a request from the network entity 606 to share PRU tag assistance reports with the network entity 606, the PRU set 604 may send an indication 616 of permission to share PRU tag assistance reports to the network entity 606. The network entity 606 may receive the indication 616 of permission to share PRU tag assistance reports. The indication 616 of permission to share PRU tag assistance reports may include permissibility / consent rules for sharing PRU tag assistance reports, PRU assistance information, and / or PRU positioning measurements with the set of wireless devices. The permissibility / consent rules may indicate the set of wireless devices with which the PRU tag assistance reports may be shared. In some aspects, the permissibility / consent rules may be open without specifying the UEs, network nodes, and / or PRUs that may obtain PRU positioning measurements, PRU assistance information, or PRU tag assistance reports. In some aspects, the permissibility / consent rules may specify the UEs, network nodes, and / or PRUs that may obtain PRU positioning measurements, PRU assistance information, or PRU tag assistance reports. In some aspects, the admissibility / consent rules may categorize a set of UEs and / or PRUs based on their UE identifiers (IDs), UE vendors, and / or UE chipset vendors. For example, the admissibility / consent rules may include a list of UE identifiers (IDs). In some aspects, the admissibility / consent rules may categorize a set of network nodes and / or PRUs based on their cell IDs, TRP IDs, network vendors, and / or network operators. In other words, the indication 616 of permission to share PRU tag assistance reporting may include at least one of: (a) a set of UE IDs associated with a set of UEs authorized to receive PRU tag assistance reporting; (b) an indication of UE vendors associated with a first set of UEs authorized to receive PRU tag assistance reporting; (c) an indication of UE chip vendors associated with a second set of UEs authorized to receive PRU tag assistance reporting; (d) a set of TRP IDs associated with TRPs authorized to receive PRU tag assistance reporting; (e) an indication of NW operators associated with a first set of TRPs authorized to receive PRU tag assistance reporting; and / or (f) an indication of NW vendors associated with a second set of TRPs authorized to receive PRU tag assistance reporting. The PRU set 604 may send the indication 616 of permission to share PRU tag assistance reporting using the TRP Information Indication of the NRPPa protocol. In some aspects, the PRU set 604 may send a TRP Information Indication message including the indication 616 of permission to share PRU tag assistance reporting. In some aspects, the PRU set 604 may send an NRPPa message including an indication 616 of permission to share PRU tag assistance reporting. The network entity 606 may share PRU tag assistance reporting with one or more wireless entities based on the indication 616 of permission to share PRU tag assistance reporting.For example, the network entity 606 may share PRU tag assistance reporting with a set of UEs having UE IDs that match the set of UE IDs indicated by the indication of permission to share PRU tag assistance reporting 616 .

[0118] The UE / PRU set 602 may send an SRS set 618 to the PRU set 604. The PRU set 604 may receive the SRS set 618 from the UE / PRU set 602. At 624, the PRU set 604 may measure the SRS set 618 for positioning. The PRU set 604 may send a PRU tag assistance report set 626 to the network entity 606. The network entity 606 may receive the PRU tag assistance report set 626 from the PRU set 604. The PRU tag assistance report set 626 may include PRU positioning measurements based on the measurements of the SRS set 618 performed at 624. The PRU tag assistance report set 626 may include PRU assistance information associated with the PRU set 604, associated with the SRS set 618 received by the PRU set 604, associated with measurements made at 624 on the SRS set 618, and / or associated with the PRS set 620 transmitted by the PRU set 604 and received by the UE / PRU set 602 (e.g., the location of the transmitting PRU, PRS beam angle information, TX group delay information). The PRU set 604 may transmit the PRU tag assistance report set 626 as part of the NRPPaTRP information exchange and measurement exchange. In other words, the PRU set 604 may transmit the TRP information exchange and measurement exchange messages that include at least one of the PRU tag assistance report set 626.

[0119] The PRU set 604 may send a PRS set 620 to the UE / PRU set 602. The UE / PRU set 602 may receive the PRS set 620 from the PRU set 604. At 622, the UE / PRU set 602 may measure the PRS set 620 for positioning. The PRUs in the UE / PRU set 602 may send a PRU tag assistance report set as a PRU tag assistance / measurement report set 628 to the network entity 606. The network entity 606 may receive the PRU tag assistance report set as a PRU tag assistance / measurement report set 628 from the PRUs in the UE / PRU set 602. The PRU tag assistance report set in the PRU tag assistance / measurement report set 628 may include PRU positioning measurements based on the measurements performed on the PRS set 620 at 622. The PRU tag assistance report set in the PRU tag assistance / measurement report set 628 may include PRU assistance information associated with the PRUs in the UE / PRU set 602, associated with the PRS set 620 received by the PRUs in the PRU set 604, associated with measurements made at 622 on the PRS set 620, and / or associated with the SRS set 618 transmitted by the UE / PRU set 602 and received by the PRU set 602 (e.g., the location of the transmitting PRU, SRS beam angle information, TX group delay information). The UEs in the UE / PRU set 602 may send a measurement report set as the PRU tag assistance / measurement report set 628 to the network entity 606. The network entity 606 may receive the measurement report set as the PRU tag assistance / measurement report set 628 from the UEs in the UE / PRU set 602. The measurement report set in the PRU tag assistance / measurement report set 628 may include PRU positioning measurements based on the measurements made at 622 on the PRS set 620.

[0120] The network entity 606 may send a PRU tag assistance report set 630 based on the PRU tag assistance reports in the PRU tag assistance report set 626 and / or the PRU tag assistance / measurement report set 628. The PRU tag assistance report set 630 may include at least a portion of the PRU tag assistance report set 626 and / or the PRU tag assistance reports in the PRU tag assistance / measurement report set 628. The network entity 606 may send the PRU tag assistance report set 630 to the UE / PRU set 602 (e.g., the UE that sent the request 608 for positioning to the network entity 606). The UE / PRU set 602 may receive the PRU tag assistance report set 630 from the network entity 606. The network entity 606 may send an assistance exchange message including the PRU tag assistance report set 630. The network entity 606 may send an LPPa message including the PRU tag assistance report set 630. In other words, the network entity 606 may share the PRU tag assistance report set 630 with the UE / PRU set 602 using the LPPa protocol's assisted exchange.

[0121] At 632, the UE / PRU set 602 may process the PRU tag assistance report set 630. In one aspect, the UE / PRU set 602 may train a positioning model based on the data and tags of the PRU tag assistance report set 630. In another aspect, the UE / PRU set 602 may calculate the location of the wireless device based on the PRU tag assistance report set 630 by utilizing the trained positioning model.

[0122] At 634, the network entity 606 may process the PRU tag assistance reports in the PRU tag assistance report set 626 and / or the PRU tag assistance / measurement report 628. In one aspect, the network entity 606 may train a positioning model based on the data and tags of the PRU tag assistance reports in the PRU tag assistance report set 626 and / or the PRU tag assistance / measurement report 628. In another aspect, the network entity 606 may calculate the location of the wireless device based on the PRU tag assistance reports in the PRU tag assistance report set 626 and / or the PRU tag assistance / measurement report 628 by utilizing the trained positioning model.

[0123] Figure 7FIG7 is a connection flow diagram 700 illustrating an example of a PRU set 702 and a TRP / PRU set 704 configured to perform positioning on each other. The TRP / PRU set 704 may include at least one TRP, at least one PRU, or at least one TRP and at least one PRU. The TRPs in the TRP / PRU set 704 may not be configured to share PRU tag assistance reports with other wireless devices, but may be configured to share measurement reports of measured positioning signals (such as measured SRS). In some aspects, the PRUs may be implemented by a UE with a known location. In some aspects, the PRUs may be implemented by a mobile TRP with a known location. In some aspects, the TRP / PRU set 704 may include PRUs configured to emulate a TRP during positioning. The network entity 706 may include a LMF. The network entity 706 may include a positioning server. In some aspects, the TRP / PRU set 704 may include a network entity 706 such that one of the TRP / PRU sets 704 may coordinate positioning between the PRU set 702 and the TRP / PRU set 704 .

[0124] The TRP / PRU set 704 and / or the network entity 706 may know the location of any of the TRP / PRU set 704 or the PRUs in the PRU set 702. For example, the network entity 706 may have a database of known locations for each of the PRUs in the PRU set 702. In some aspects, the PRUs may calculate their locations using positioning or using other sensor / non-RF positioning methods (e.g., using high-accuracy GNSS or GNSS positioning by traveling to a known location at a pre-scheduled time) and may send their locations to the network entity 706, which may update the locations of the PRUs to other wireless devices, such as the TRP / PRU set 704. In other aspects, the PRUs in the PRU set 702 may broadcast their calculated locations to other wireless devices, such as the TRP / PRU set 704. In other aspects, the network entity 706 may perform positioning on the PRUs in the PRU set 702 and may then update the locations of the PRUs to other wireless devices, such as the TRP / PRU set 704.

[0125] At least one of the TRP / PRU sets 704 may send a request 708 for positioning to the network entity 706. The network entity 706 may receive the request 708 for positioning. The request 708 may be sent as part of a TRP information exchange of the NRPPa protocol between the TRP / PRU set 704 and the network entity 706. In one aspect, the TRP / PRU set 704 may send an NRPPa message including the request 708 for positioning to the network entity 706. In one aspect, the TRP / PRU set 704 may send a TRP information exchange and a measurement exchange message including the request 708 for positioning to the network entity 706. The request 708 for positioning may request the network entity 706 to configure positioning between the PRU set 702 and the TRP / PRU set 704, for example, to configure an SRS set 718 and / or to configure a PRS set 720.

[0126] The request for positioning 708 may include a request for the PRU to send a PRU tag assistance report that may be shared with at least one of the TRP / PRU sets 704. The request for positioning 708 may include an indication of information to be included in the PRU tag assistance report. The request for positioning 708 may include a request for PRU positioning measurements, such as a request for measurements of an SRS set by the TRP / PRU set 704 and / or a request for measurements of a PRS set by the PRU set 702. The request for positioning 708 may include a request for the network entity 706 to configure resources for positioning. In one aspect, the request for positioning 708 may include a request for the network entity 706 to configure SRS resources for the PRU set 702 to send an SRS set 718 to the TRP / PRU set 704 and to configure SRS resources for the TRP / PRU set 704 to receive an SRS set 718. In one aspect, the request for positioning 708 may include a request to the network entity 706 to configure the PRS resources for the TRP / PRU set 704 to send the PRS set 720 to the PRU set 702 and to configure the PRS resources for the PRU set 702 to receive the PRS set 720.

[0127] The request for positioning 708 may include a request for PRU assistance information. The PRU assistance information may include an indication of the location of at least one of the PRUs in the TRP / PRU set 704. The PRU assistance information may include an indication of the location of at least one of the PRUs in the TRP / PRU set 704. The PRU assistance information may include an indication of the beam angle associated with the set of positioning signals received or transmitted by the PRU set 702. In one aspect, the PRU assistance information may include the calculated AoA of the PRS set 720. In another aspect, the PRU assistance information may include the calculated AoD of the SRS set 718. The PRU assistance information may include an indication of the beam angle associated with the set of positioning signals received or transmitted by the PRUs in the TRP / PRU set 704. In one aspect, the PRU assistance information may include the calculated AoA of the SRS set 718 received by the PRUs in the TRP / PRU set 704. In another aspect, the PRU assistance information may include the calculated AoD of the PRS set 720 transmitted by the PRUs in the TRP / PRU set 704. The PRU assistance information may include an indication of the antenna orientations associated with the PRU set 702 that transmits or receives the positioning signal set. In one aspect, the PRU assistance information may include a set of orientations for the antenna set of the PRU set 702 that receives the PRS set 720. In another aspect, the PRU assistance information may include a set of orientations for the antenna set of the PRU set 702 that transmits the SRS set 718. The PRU assistance information may include an indication of the antenna orientations associated with the PRUs in the TRP / PRU set 704 that transmits or receives the positioning signal set. In one aspect, the PRU assistance information may include a set of orientations for the antenna set of the PRUs in the TRP / PRU set 704 that receives the SRS set 718. In another aspect, the PRU assistance information may include a set of orientations for the antenna set of the PRUs in the TRP / PRU set 704 that transmits the PRS set 720. The PRU assistance information may include an indication of the group delay associated with the PRU set 702 that measures the PRS set 720. The PRU assistance information may include an indication of a group delay associated with a PRU in the TRP / PRU set 704 that measures the SRS set 718. The PRU assistance information may include an indication of a sensor measurement associated with the PRU set 702 that measures the PRS set 720. The PRU assistance information may include an indication of a sensor measurement associated with the PRU in the TRP / PRU set 704 that measures the SRS set 718. The PRU assistance information may include an indication of a sensor type associated with at least one PRU in the PRU set 702. The PRU assistance information may include an indication of a sensor type associated with a PRU in the TRP / PRU set 704. The PRU assistance information may include an indication of a synchronization error associated with the PRU set 702 that measures the PRS set 720.The PRU assistance information may include an indication of a synchronization error associated with the PRUs in the TRP / PRU set 704 for measuring the SRS set 718. The PRU assistance information may include an indication of a Tx-Rx or Rx-Tx timing error associated with the PRU set 702 for measuring the PRS set 720. The PRU assistance information may include an indication of a Tx-Rx or Rx-Tx timing error associated with the PRUs in the TRP / PRU set 704 for measuring the SRS set 718. The PRU assistance information may include an indication of a clock drift range associated with the PRU set 702 for measuring the PRS set 720. The PRU assistance information may include an indication of a clock drift range associated with the PRUs in the TRP / PRU set 704 for measuring the SRS set 718.

[0128] In response to receiving the request for positioning 708, the network entity 706 may send a PRS / SRS resource scheduling set 710 to the TRP / PRU set 704. The TRP / PRU set 704 may receive the PRS / SRS resource scheduling set 710. The PRS / SRS resource scheduling set 710 may configure the TRP / PRU set 704 to receive an SRS set 718. The PRS / SRS resource scheduling set 710 may configure the TRP / PRU set 704 to send a PRS set 720. The network entity 706 may send the PRS / SRS resource scheduling set 710 via an NRPPa message. The network entity 706 may send the PRS / SRS resource scheduling set 710 as part of an NRPPa TRP information exchange and measurement exchange.

[0129] In some aspects, at least some of the TRP / PRU sets 704 may configure a PRS / SRS resource scheduling set 712 based on the PRS / SRS resource scheduling set 710. For example, some of the TRP / PRU sets 704 may be serving cells for the PRU set 702. The TRP / PRU set 704 may transmit the PRS / SRS resource scheduling set 712 to the PRU set 702. The PRU set 702 may receive the PRS / SRS resource scheduling set 712 from the TRP / PRU set 704. The PRS / SRS resource scheduling set 712 may configure the PRU set 702 to transmit an SRS set 718 to the TRP / PRU set 704. The PRS / SRS resource scheduling set 712 may configure the PRU set 702 to receive a PRS set 720 from the TRP / PRU set 704. The TRP / PRU set 704 may transmit the PRS / SRS resource scheduling set 712 as an RRC configuration.

[0130] In other aspects, the network entity 706 may directly configure a PRS / SRS resource scheduling set 714 for the PRU set 702. The network entity 706 may send the PRS / SRS resource scheduling set 714 to the PRU set 702. The PRU set 702 may receive the PRS / SRS resource scheduling set 714 from the network entity 706. The PRS / SRS resource scheduling set 714 may configure the PRU set 702 to send an SRS set 718 to the TRP / PRU set 704. The PRS / SRS resource scheduling set 714 may configure the PRU set 702 to receive a PRS set 720 from the TRP / PRU set 704. The network entity 706 may send the PRS / SRS resource scheduling set 714 as an RRC configuration. The PRS / SRS resource scheduling set 714 may request that the PRU set 702 share a PRU tag assistance report with the network entity 706. Such a request may indicate what type of PRU positioning measurements and / or PRU assistance information may be included in the PRU tag assistance report. The PRS / SRS resource scheduling set 714 may request the PRU set 702 to share admissibility / consent rules with the network entity 706 .

[0131] In response to receiving a request from the network entity 706 to share PRU tag assistance reports with the network entity 706, the PRU set 702 may send an indication 716 of permission to share PRU tag assistance reports to the network entity 706. The network entity 706 may receive the indication 716 of permission to share PRU tag assistance reports. The indication 716 of permission to share PRU tag assistance reports may include permissibility / consent rules for sharing PRU tag assistance reports, PRU assistance information, and / or PRU positioning measurements with a set of wireless devices. The permissibility / consent rules may indicate the set of wireless devices with which the PRU tag assistance reports may be shared. In some aspects, the permissibility / consent rules may be open without specifying the UEs, network nodes, and / or PRUs that may obtain PRU positioning measurements, PRU assistance information, or PRU tag assistance reports. In some aspects, the permissibility / consent rules may specify the UEs, network nodes, and / or PRUs that may obtain PRU positioning measurements, PRU assistance information, or PRU tag assistance reports. In some aspects, the admissibility / consent rules may categorize a set of UEs and / or PRUs based on their UE IDs, UE vendors, and / or UE chipset vendors. For example, the admissibility / consent rules may include a list of UE identifiers (IDs). In some aspects, the admissibility / consent rules may categorize a set of network nodes and / or PRUs based on their cell IDs, TRP IDs, network vendors, and / or network operators. In other words, the indication 716 of permission to share PRU tag assistance reporting may include at least one of: (a) a set of UE IDs associated with a set of UEs authorized to receive PRU tag assistance reporting; (b) an indication of UE vendors associated with a first set of UEs authorized to receive PRU tag assistance reporting; (c) an indication of UE chip vendors associated with a second set of UEs authorized to receive PRU tag assistance reporting; (d) a set of TRP IDs associated with TRPs authorized to receive PRU tag assistance reporting; (e) an indication of NW operators associated with a first set of TRPs authorized to receive PRU tag assistance reporting; and / or (f) an indication of NW vendors associated with a second set of TRPs authorized to receive PRU tag assistance reporting. The PRU set 702 may send the indication 716 of permission to share PRU tag assistance reporting using a UE capability message indication of the LPPa protocol. In some aspects, the PRU set 702 may send a capability message including the indication 716 of permission to share PRU tag assistance reporting. In some aspects, the PRU set 702 may send an LPPa message including an indication of permission to share PRU tag assistance reporting 716. The network entity 706 may share PRU tag assistance reporting with one or more wireless entities based on the indication of permission to share PRU tag assistance reporting 716.For example, the network entity 706 may share PRU tag assistance reporting with a set of UEs having UE IDs that match the set of UE IDs indicated by the indication of permission to share PRU tag assistance reporting 716 .

[0132] The TRP / PRU set 704 may send a PRS set 720 to the PRU set 702. The PRU set 702 may receive the PRS set 720 from the TRP / PRU set 704. At 722, the PRU set 702 may measure the PRS set 720 for positioning. The PRU set 702 may send a PRU tag assistance report set 726 to the network entity 706. The network entity 706 may receive the PRU tag assistance report set 726 from the PRU set 702. The PRU tag assistance report set 726 may include PRU positioning measurements based on the measurements of the PRS set 720 performed at 722. The PRU tag assistance report set 726 may include PRU assistance information associated with the PRU set 702, associated with the PRS set 720 received by the PRU set 702, associated with measurements made at 722 on the PRS set 720, and / or associated with the SRS set 718 transmitted by the PRU set 702 and received by the TRP / PRU set 704 (e.g., the location of the transmitting PRU, PRS beam angle information, TX group delay information). The PRU set 702 may transmit the PRU tag assistance report set 726 as part of an assistance data exchange of the LPPa protocol. In other words, the PRU set 702 may transmit an assistance data exchange message including at least one of the PRU tag assistance report set 726.

[0133] The PRU set 702 may send an SRS set 718 to the TRP / PRU set 704. The TRP / PRU set 704 may receive the SRS set 718 from the PRU set 702. At 724, the TRP / PRU set 704 may measure the SRS set 718 for positioning. The PRUs in the TRP / PRU set 704 may send a PRU tag assistance report set as a PRU tag assistance / measurement report set 728 to the network entity 706. The network entity 706 may receive the PRU tag assistance report set as a PRU tag assistance / measurement report set 728 from the PRUs in the TRP / PRU set 704. The PRU tag assistance report set in the PRU tag assistance / measurement report set 728 may include PRU positioning measurements based on the measurements of the SRS set 718 performed at 724. The PRU tag assistance report set in the PRU tag assistance / measurement report set 728 may include PRU assistance information associated with the PRUs in the TRP / PRU set 704, associated with the SRS set 718 received by the PRUs in the TRP / PRU set 704, associated with the measurements performed at 724 on the SRS set 718, and / or associated with the PRS set transmitted by the TRP / PRU set 704 and received by the PRU set 702 (e.g., the location of the transmitting PRU, SRS beam angle information, TX group delay information). The TRPs in the TRP / PRU set 704 may transmit the measurement report set as the PRU tag assistance / measurement report set 728 to the network entity 706. The network entity 706 may receive the measurement report set as the PRU tag assistance / measurement report set 728 from the UEs in the PRU set 702. The measurement report set in the PRU tag assistance / measurement report set 728 may include PRU positioning measurements based on the measurements performed at 724 on the SRS set 718.

[0134] The network entity 706 may send a PRU tag assistance report set 730 based on the PRU tag assistance reports in the PRU tag assistance report set 726 and / or the PRU tag assistance / measurement report set 728. The PRU tag assistance report set 730 may include at least a portion of the PRU tag assistance report set 726 and / or the PRU tag assistance reports in the PRU tag assistance / measurement report set 728. The network entity 706 may send the PRU tag assistance report set 730 to the TRP / PRU set 704 (e.g., the TRP that sent the request for positioning 708). The TRP / PRU set 704 may receive the PRU tag assistance report set 730 from the network entity 706. The network entity 706 may send a TRP information exchange and measurement exchange message including the PRU tag assistance report set 730. The network entity 706 may send an NRPPa message including the PRU tag assistance report set 730. In other words, the network entity 706 may share the PRU tag assistance report set 730 with the TRP / PRU set 704 using the TRP information exchange and measurement exchange of the NRPPa protocol.

[0135] At 732, the TRP / PRU set 704 may process the PRU tag assistance report set 730. In one aspect, the TRP / PRU set 704 may train a positioning model based on the data and tags of the PRU tag assistance report set 730. In another aspect, the TRP / PRU set 704 may calculate the location of the wireless device based on the PRU tag assistance report set 730 by utilizing the trained positioning model.

[0136] At 734, the network entity 706 may process the PRU tag assistance reports in the PRU tag assistance report set 726 and / or the PRU tag assistance / measurement report 728. In one aspect, the network entity 706 may train a positioning model based on the data and tags of the PRU tag assistance reports in the PRU tag assistance report set 726 and / or the PRU tag assistance / measurement report 728. In another aspect, the network entity 706 may calculate the location of the wireless device based on the PRU tag assistance reports in the PRU tag assistance report set 726 and / or the PRU tag assistance / measurement report 728 by utilizing the trained positioning model.

[0137] Figure 8800 is a flow chart of a method of wireless communication. The method may be performed by a wireless device (e.g., UE 104, UE 350; wireless device 402, wireless device 404, wireless device 406; UE / PRU 502; UE / PRU set 602; PRU 504; PRU set 604, PRU set 702; base station 102, base station 310; TRP / PRU 506, TRP / PRU set 704; network entity 606, network entity 706; apparatus 1704; network entity 1702, network entity 1802, network entity 1960). At 802, the wireless device may receive a set of positioning signals from at least one of a UE, a first network node, or a PRU. For example, 802 may be performed by Figure 6 , which may receive an SRS set 618 from the UE / PRU set 602. In another example, 802 may be performed by Figure 7 802 may be executed by the PRU set 702 in the embodiment, which may receive the PRS set 720 from the TRP / PRU set 704. Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0138] At 804, the wireless device may measure a set of positioning signals. For example, 804 may be performed by Figure 6 In another example, 804 may be performed by the PRU set 604 in the embodiment, which may measure the SRS set 618 at 624. Figure 7 702 in the PRU set, which may measure the PRS set 720 at 722. In addition, 804 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0139] At 806, the wireless device may send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a positioning measurement set based on the measured positioning signal set. The PRU tag assistance report may include PRU assistance information associated with measuring the positioning signal set. For example, 806 may be performed by Figure 6The PRU set 604 in the network entity 606 may be executed, and the PRU set may send a PRU tag assistance report set 626 to the network entity 606. The PRU tag assistance report set 626 may include a set of positioning measurements made at 624 based on the SRS set 618. The PRU tag assistance report set 626 may include PRU assistance information associated with measuring the SRS set 618. In another example, 806 may be performed by Figure 7 The PRU set 702 in the network entity 706 may be executed, and the PRU set may send a PRU tag assistance report set 726 to the network entity 706. The PRU tag assistance report set 726 may include a set of positioning measurements made at 722 based on the PRS set 720. The PRU tag assistance report set 726 may include PRU assistance information associated with the measured PRS set 720. In addition, 806 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0140] Figure 9 900 is a flow chart of a method of wireless communication. The method may be performed by a wireless device (e.g., UE 104, UE 350; wireless device 402, wireless device 404, wireless device 406; UE / PRU 502; UE / PRU set 602; PRU 504; PRU set 604, PRU set 702; base station 102, base station 310; TRP / PRU 506, TRP / PRU set 704; network entity 606, network entity 706; apparatus 1704; network entity 1702, network entity 1802, network entity 1960). At 902, the wireless device may receive a set of positioning signals from at least one of a UE, a first network node, or a PRU. For example, 902 may be performed by Figure 6 , which may receive an SRS set 618 from the UE / PRU set 602. In another example, 902 may be performed by Figure 7 The PRU set 702 in the embodiment of the present invention may receive the PRS set 720 from the TRP / PRU set 704. In addition, 902 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0141] At 904, the wireless device may measure a set of positioning signals. For example, 904 may be performed by Figure 6 In another example, 904 may be performed by the PRU set 604 in the embodiment, which may measure the SRS set 618 at 624. Figure 7The PRU set 702 in the embodiment may measure the PRS set 720 at 722. In addition, 904 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0142] At 905, the wireless device sends an indication of permission for shared PRU tag assisted reporting to at least one of the first network node or the second network node. For example, 905 may be Figure 6 In another example, 905 may be performed by the PRU set 604 in the network entity 606 or another network node such as the LMF or core network, which may send an indication 616 of permission for shared PRU tag assistance reporting. Figure 7 The PRU set 702 in the network may send an indication 716 of permission for shared PRU tag assisted reporting to the network entity 706 or another network node such as the LMF or core network. In addition, 905 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0143] At 906, the wireless device may send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a positioning measurement set based on the measured positioning signal set. The PRU tag assistance report may include PRU assistance information associated with measuring the positioning signal set. For example, 906 may be performed by Figure 6 The PRU set 604 in the network entity 606 may be executed, and the PRU set may send a PRU tag assistance report set 626 to the network entity 606. The PRU tag assistance report set 626 may include a set of positioning measurements made at 624 based on the SRS set 618. The PRU tag assistance report set 626 may include PRU assistance information associated with measuring the SRS set 618. In another example, 906 may be performed by Figure 7 The PRU set 702 in the network entity 706 may be executed, and the PRU set may send a PRU tag assistance report set 726 to the network entity 706. The PRU tag assistance report set 726 may include a set of positioning measurements made at 722 based on the PRS set 720. The PRU tag assistance report set 726 may include PRU assistance information associated with the measured PRS set 720. In addition, 906 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0144] At 908, the wireless device may send a second set of positioning signals to at least one of the UE, the first network node, or the PRU. For example, 908 may be performed by Figure 6 The PRU set 604 in the UE / PRU set 602 may send a PRS set 620 to the UE / PRU set 602. The PRS set 620 may also be received by the network entity 606. In another example, 908 may be performed by Figure 7 The PRU set 702 in the network may send an SRS set 718 to the TRP / PRU set 704. The SRS set 718 may also be received by the network entity 706. Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0145] At 910, the wireless device may send second PRU assistance information associated with a second positioning signal set to at least one of the first network node or the second network node. The second PRU assistance information may include TX configuration, such as beam angle information for the second positioning signal set. For example, 910 may be performed by Figure 6 The PRU set 604 in the embodiment may be executed, which may send a PRU tag assistance report set 626 that may include second PRU assistance information associated with the PRS set 620 to the network entity 606 or another network node such as the LMF or the core network. In another example, 910 may be performed by Figure 7 The PRU set 702 in the embodiment may be executed, which may send a PRU tag assistance report set 726 that may include second PRU assistance information associated with the SRS set 718 to the network entity 706 or another network node such as the LMF or the core network. In addition, 910 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0146] In some aspects, the wireless device may receive a request to send a PRU tag assistance report from at least one of the first network node or the second network node. In response to receiving the request, the wireless device may send a PRU tag assistance report including second PRU assistance information associated with the second positioning signal set to the first network node or the second network node. For example, this may be done by Figure 6The PRU set 604 in the network may receive a request for a PRU tag assistance report set 626 from a network entity 606 or another network node such as an LMF or a core network. The PRU set 604 may send the PRU tag assistance report set 626 to the network entity 606 or another network node such as an LMF or a core network in response to the request. In another example, this may be performed by Figure 7 The PRU set 702 in FIG. 1 may receive a request for a PRU tag assistance report set 726 from a network entity 706 or another network node such as an LMF or a core network. The PRU set 702 may send the PRU tag assistance report set 726 to the network entity 706 or another network node such as an LMF or a core network in response to the request.

[0147] At 912, the wireless device sends a TRP information indication message including an indication of permission for shared PRU tag assisted reporting. For example, 912 may be Figure 6 The PRU set 604 in the embodiment of the present invention may send an indication 616 of permission for shared PRU tag assistance reporting as a TRP information indication message to the network entity 606. In addition, 912 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0148] At 914, the wireless device sends an NRPPa message including an indication of permission for shared PRU tag assisted reporting. For example, 914 may be Figure 6 The PRU set 604 in the embodiment of the present invention may send an indication 616 of permission for shared PRU tag assisted reporting as an NRPPa message to the network entity 606. In addition, 914 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0149] At 916, the wireless device sends a capability message including an indication of permission to share PRU tag assisted reporting. For example, 916 may be Figure 6 In another example, 916 may be performed by the PRU set 604 in the network entity 606, which may send an indication 616 of permission for shared PRU tag assistance reporting as a capability message to the network entity 606. Figure 7 The PRU set 702 in the embodiment of the present invention may send an indication 716 of permission for shared PRU tag assistance reporting as a capability message to the network entity 706. In addition, 916 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0150] At 918, the wireless device sends an LPPa message including an indication of permission for shared PRU tag assisted reporting. For example, 918 may be Figure 7 The PRU set 702 in the embodiment of the present invention may send an indication 716 of permission for shared PRU tag assistance reporting as an LPPa message to the network entity 706. In addition, 918 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0151] Figure 10 1000 is a flow chart of a method of wireless communication. The method may be performed by a wireless device (e.g., UE 104, UE 350; wireless device 402, wireless device 404, wireless device 406; UE / PRU 502; UE / PRU set 602; PRU 504; PRU set 604, PRU set 702; base station 102, base station 310; TRP / PRU 506, TRP / PRU set 704; network entity 606, network entity 706; apparatus 1704; network entity 1702, network entity 1802, network entity 1960). At 1002, the wireless device may receive a set of positioning signals from at least one of a UE, a first network node, or a PRU. For example, 1002 may be performed by Figure 6 , which may receive an SRS set 618 from the UE / PRU set 602. In another example, 1002 may be performed by Figure 7 1002 may be executed by the PRU set 702 in the embodiment, which may receive the PRS set 720 from the TRP / PRU set 704. Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0152] At 1004, the wireless device may measure a set of positioning signals. For example, 1004 may be performed by Figure 6 In another example, 1004 may be performed by the PRU set 604 in the embodiment, which may measure the SRS set 618 at 624. Figure 7 , which may measure the PRS set 720 at 722. In addition, 1004 may be performed by the PRU set 702 in Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0153] At 1005, the wireless device may receive a request to send a PRU tag assistance report from at least one of the first network node or the second network node. For example, 1005 may be performed by Figure 6 In another example, 1005 may be performed by the PRU set 604 in the network entity 606 or a second network node such as the LMF or the core network to receive a request to send the PRU tag assistance report set 626. Figure 7 The PRU set 702 in the network entity 706 or a second network node such as the LMF or the core network may receive a request to send the PRU tag assistance report set 726. In addition, 1005 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0154] At 1006, the wireless device may send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a positioning measurement set based on the measured positioning signal set. The PRU tag assistance report may include PRU assistance information associated with measuring the positioning signal set. For example, 1006 may be performed by Figure 6 The PRU set 604 in the network entity 606 may be executed, and the PRU set may send a PRU tag assistance report set 626 to the network entity 606. The PRU tag assistance report set 626 may include a set of positioning measurements made at 624 based on the SRS set 618. The PRU tag assistance report set 626 may include PRU assistance information associated with measuring the SRS set 618. In another example, 1006 may be performed by Figure 7 The PRU set 702 in the network entity 706 may be executed, and the PRU set may send a PRU tag assistance report set 726 to the network entity 706. The PRU tag assistance report set 726 may include a set of positioning measurements made at 722 based on the PRS set 720. The PRU tag assistance report set 726 may include PRU assistance information associated with the measured PRS set 720. In addition, 1006 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0155] At 1008, the wireless device may receive a configuration of a set of positioning signals from at least one of the first network node or the second network node. Receiving the set of positioning signals may be based on the configuration. For example, 1008 may be performed by Figure 6 The PRU set 604 in the network may receive a PRS / SRS resource scheduling set 610 from a network entity 606 or another network node such as an LMF or a core network. The PRS / SRS resource scheduling set 610 may configure an SRS set 618 and / or a PRS set 620. The received SRS set 618 may be based on the PRS / SRS resource scheduling set 610. In another example, 1008 may be performed by Figure 7 The PRU set 702 in the network entity 706 may receive a PRS / SRS resource scheduling set 714 or a PRS / SRS resource scheduling set 712 from at least one of the TRP / PRU set 704. The PRS / SRS resource scheduling set 712 or the PRS / SRS resource scheduling set 714 may configure an SRS set 718 and / or a PRS set 720. The received PRS set 720 may be based on at least one of the PRS / SRS resource scheduling set 712 or the PRS / SRS resource scheduling set 714. In addition, 1008 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0156] At 1010, the wireless device may send a TRP information and measurement exchange message including a PRU tag assistance report. For example, 1010 may be performed by Figure 6 The PRU set 604 in the embodiment of the present invention may be executed, which may send a PRU tag assistance report set 626 as a TRP information and measurement exchange message including a report set. In addition, 1010 may be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0157] At 1012, the wireless device may send an NRPPa message including a PRU tag assistance report. For example, 1012 may be performed by Figure 6 The PRU set 604 in the PRU tag can be executed, and the PRU set can send the PRU tag assistance report set 626 as an NRPPa message including the report set. In addition, 1012 can be performed by Figure 1 、 Figure 3 、 Figure 17 、 Figure 18 or Figure 19 Component 198 in is executed.

[0158] Figure 11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350; wireless device 404; UE / PRU 502; UE / PRU set 602; PRU 504; PRU set 702; apparatus 1704). At 1102, the UE may transmit an SRS set for a PRU. For example, 1102 may be performed by Figure 6 1102 may be performed by the UE / PRU set 602 in the embodiment, which may send the SRS set 618 to the PRU set 604. Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0159] At 1104, the UE may receive a PRU tag assistance report from the network node, the PRU tag assistance report including a positioning measurement set based on the SRS set and including PRU assistance information associated with the positioning measurement set. For example, 1104 may be performed by Figure 6 The UE / PRU set 602 in the embodiment may receive a PRU tag assistance report set 630 from the network entity 606, the PRU tag assistance report set including a positioning measurement set based on the SRS set 618 and including PRU assistance information associated with the positioning measurement set performed at 624. In addition, 1104 may be performed by Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0160] Figure 12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350; wireless device 404; UE / PRU 502; UE / PRU set 602; PRU 504; PRU set 702; apparatus 1704). At 1201, the UE may send a request to a network node to send a PRU tag assistance report. For example, 1201 may be performed by Figure 6 The UE / PRU set 602 in the network may send a request 608 to send a PRU tag assistance report to the network entity 606. In addition, 1201 may be performed by Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0161] At 1202, the UE may send an SRS set for a PRU. For example, 1202 may be Figure 61202 can be performed by the UE / PRU set 602 in the embodiment, which can send the SRS set 618 to the PRU set 604. Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0162] At 1204, the UE may receive a PRU tag assistance report from the network node, the PRU tag assistance report including a positioning measurement set based on the SRS set and including PRU assistance information associated with the positioning measurement set. Figure 6 The UE / PRU set 602 in the embodiment may receive a PRU tag assistance report set 630 from the network entity 606, the PRU tag assistance report set including a positioning measurement set based on the SRS set 618 and including PRU assistance information associated with the positioning measurement set performed at 624. In addition, 1204 may be performed by Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0163] At 1206, the UE may send an assisted exchange message including the request. For example, 1206 may be performed by Figure 6 The UE / PRU set 602 in the embodiment of the present invention may send the request 608 as an auxiliary exchange message including the request. In addition, 1206 may be performed by Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0164] At 1208, the UE may send a request to the network entity to configure an SRS resource set. For example, 1208 may be performed by Figure 6 The UE / PRU set 602 in the network may send a request 608 to the network entity 606 to configure the SRS resource set. Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0165] At 1210, the UE may receive a configuration of an SRS resource set from a network node. For example, 1210 may be configured by Figure 6 The UE / PRU set 602 in the embodiment may receive a PRS / SRS resource scheduling set 612 including a configuration of an SRS resource set from the PRU set 604, or may receive a PRS / SRS resource scheduling set 614 including a configuration of an SRS resource set from the network entity 606. In addition, 1210 may be performed by Figure 1 、 Figure 3or Figure 17 Component 199 in is executed.

[0166] At 1212, the UE may send an SRS set based on the SRS resource set. For example, 1212 may be Figure 6 The UE / PRU set 602 in the UE / PRU set may send an SRS set 618 based on the PRS / SRS resource scheduling set 612 or the SRS resource set in the PRS / SRS resource scheduling set 614. In addition, 1212 may be performed by Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0167] At 1214, the UE may receive an Assisted Exchange Message including a PRU Tag Assisted Report. For example, 1214 may be performed by Figure 6 The UE / PRU set 602 in the embodiment may receive an auxiliary exchange message including a PRU tag auxiliary report set 630 from the network entity 606. In addition, 1214 may be performed by Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0168] At 1216, the UE may receive an LPPa message including a PRU tag assistance report. For example, 1216 may be performed by Figure 6 The UE / PRU set 602 in the embodiment may receive an LPPa message including a PRU tag assistance report set 630 from the network entity 606. In addition, 1216 may be performed by Figure 1 、 Figure 3 or Figure 17 Component 199 in is executed.

[0169] Figure 13 1300 is a flow chart of a method of wireless communication. The method may be performed by a first network node (e.g., PRU 504; PRU set 604; base station 102, base station 310; wireless device 402, wireless device 406; TRP / PRU 506, TRP / PRU set 704; network entity 606, network entity 706; network entity 1702, network entity 1802, network entity 1960). At 1302, the first network node may send a PRS set for a PRU. For example, 1302 may be performed by Figure 7 The TRP / PRU set 704 in the embodiment of the present invention may send a PRS set 720 to the PRU set 702. In addition, 1302 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0170] At 1304, the first network node may receive a PRU tag assistance report from the second network node, the PRU tag assistance report including a positioning measurement set based on the PRS set and including PRU assistance information associated with the positioning measurement set. Figure 7 The TRP / PRU set 704 in the embodiment may receive a PRU tag assistance report set 730 from the network entity 706, the PRU tag assistance report set including a positioning measurement set based on the PRS set 720 and including PRU assistance information associated with the positioning measurement set measured at 722. In addition, 1304 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0171] Figure 14 1400 is a flow chart of a method of wireless communication. The method may be performed by a first network node (e.g., PRU 504; PRU set 604, base station 102, base station 310; wireless device 402, wireless device 406; TRP / PRU 506, TRP / PRU set 704; network entity 606, network entity 706; network entity 1702, network entity 1802, network entity 1960). At 1401, the first network node may send a request to a second network node to send a PRU tag assistance report. For example, 1401 may be performed by Figure 7 The TRP / PRU set 704 in the network entity 706 may send a request 708 to send a PRU tag assistance report. Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0172] At 1402, a first network node may send a PRS set for a PRU. For example, 1402 may be performed by Figure 7 The TRP / PRU set 704 in the embodiment of the present invention may send a PRS set 720 to the PRU set 702. In addition, 1402 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0173] At 1404, the first network node may receive a PRU tag assistance report from the second network node, the PRU tag assistance report including a positioning measurement set based on the PRS set and including PRU assistance information associated with the positioning measurement set. Figure 7 The TRP / PRU set 704 in the embodiment may receive a PRU tag assistance report set 730 from the network entity 706, the PRU tag assistance report set including a positioning measurement set based on the PRS set 720 and including PRU assistance information associated with the positioning measurement set measured at 722. In addition, 1404 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0174] At 1406, the first network node may send an auxiliary exchange message including the request. The auxiliary exchange message may be sent as part of an NRPPa framework or interface. The NRPPa may include the sent auxiliary exchange message. For example, 1406 may be sent by Figure 7 The TRP / PRU set 704 in the embodiment of the present invention may be executed, and the TRP / PRU set may send the request 708 as an auxiliary exchange message including the request. The auxiliary exchange message may be sent as part of the NRPPa framework or interface. The NRPPa may include the auxiliary exchange message sent. In addition, 1406 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0175] At 1408, the first network node may configure a configuration of a PRS resource set for a PRS set. For example, 1408 may be performed by Figure 7 1408 may be performed by the network entity 706, which may configure the configuration of the PRS resource set for the PRS set 720. In another example, 1408 may be performed by the network entity 706, which may configure the configuration of the PRS resource set for the PRS set 720. Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0176] At 1410, the first network node may send a configuration for a PRU. For example, 1410 may be performed by Figure 7The TRP / PRU set 704 in the , which can send the configuration as a PRS / SRS resource schedule set 712 to the PRU set 702. In another example, 1410 can be performed by Figure 7 The network entity 706 in the embodiment may send the configuration as a PRS / SRS resource scheduling set 714 to the PRU set 702. In addition, 1410 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0177] At 1412, the first network node may send a PRS set based on the configuration. For example, 1412 may be performed by Figure 7 The TRP / PRU set 704 in the embodiment may be executed, which may send a PRS set 720 at the PRU set 702 based on the configuration. In addition, 1412 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0178] At 1414, the first network node may receive an assistance exchange message including a PRU tag assistance report. For example, 1414 may be performed by Figure 7 The network entity 706 in the embodiment may receive an auxiliary exchange message including a PRU tag auxiliary report set 726 from the PRU set 702. In addition, 1414 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0179] At 1416, the first network node may receive an NRPPa message including a PRU tag assistance report. For example, 1416 may be performed by Figure 7 The network entity 706 in the embodiment may receive an NRPPa message including a PRU tag assistance / measurement report set 728. In addition, 1416 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0180] Figure 151500 is a flow chart of a method of wireless communication. The method may be performed by a first network node (e.g., PRU 504; PRU set 604; base station 102; base station 310; wireless device 402; wireless device 406; TRP / PRU 506; TRP / PRU set 704; network entity 606; network entity 706; network entity 1702; network entity 1802; network entity 1960). At 1502, the first network node may send a configuration of a positioning signal set for transmission or reception using the PRU. For example, 1502 may be performed by Figure 6 The network entity 606 in the embodiment may send a PRS / SRS resource scheduling set 610 to the PRU set 604. The PRS / SRS resource scheduling set 610 may include a configuration of an SRS set 618 for reception at the PRU set 604 and / or a PRS set 620 for transmission at the PRU set 604. In another example, 1502 may be performed by Figure 7 The network entity 706 in the embodiment may send a PRS / SRS resource scheduling set 714 to the PRU set 702. The PRS / SRS resource scheduling set 714 may include a configuration of an SRS set 718 for transmission at the PRU set 702 and / or a PRS set 720 for reception at the PRU set 702. Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0181] At 1504, the first network node may receive a PRU tag assistance report including a set of PRU assistance information associated with a set of positioning signals. For example, 1504 may be performed by Figure 6 In another example, 1504 may be performed by a network entity 606 in the embodiment of the present invention, the network entity may receive a PRU tag assistance report set 626 from the PRU set 604, the PRU tag assistance report set including a PRU assistance information set associated with the SRS set 618 and / or the PRS set 620. Figure 7 The network entity 706 in the embodiment may receive a PRU tag assistance report set 726 from the PRU set 702, the PRU tag assistance report set including a PRU assistance information set associated with the SRS set 718 and / or the PRS set 720. In addition, 1504 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0182] Figure 161600 is a flow chart of a method of wireless communication. The method may be performed by a first network node (e.g., PRU 504; PRU set 604; base station 102; base station 310; wireless device 402; wireless device 406; TRP / PRU 506; TRP / PRU set 704; network entity 606; network entity 706; network entity 1702; network entity 1802; network entity 1960). At 1602, the first network node may send a configuration of a positioning signal set for transmission or reception using the PRU. For example, 1602 may be performed by Figure 6 The network entity 606 in the embodiment may send a PRS / SRS resource scheduling set 610 to the PRU set 604. The PRS / SRS resource scheduling set 610 may include a configuration of an SRS set 618 for reception at the PRU set 604 and / or a PRS set 620 for transmission at the PRU set 604. In another example, 1602 may be performed by Figure 7 The network entity 706 in the embodiment may send a PRS / SRS resource scheduling set 714 to the PRU set 702. The PRS / SRS resource scheduling set 714 may include a configuration of an SRS set 718 for transmission at the PRU set 702 and / or a PRS set 720 for reception at the PRU set 702. Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0183] At 1604, the first network node may receive a PRU tag assistance report including a set of PRU assistance information associated with a set of positioning signals. For example, 1604 may be performed by Figure 6 In another example, 1604 may be performed by a network entity 606 in which the network entity may receive a PRU tag assistance report set 626 from the PRU set 604, the PRU tag assistance report set including a PRU assistance information set associated with the SRS set 618 and / or the PRS set 620. Figure 7 The network entity 706 in the embodiment may receive a PRU tag assistance report set 726 from the PRU set 702, the PRU tag assistance report set including a PRU assistance information set associated with the SRS set 718 and / or the PRS set 720. In addition, 1604 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0184] At 1606, the first network node may receive an indication of permission for shared PRU tag assisted reporting. For example, 1606 may be performed by Figure 6 In another example, 1606 may be performed by a network entity 606 in which the network entity may receive an indication 616 of permission for shared PRU tag assistance reporting from the PRU set 604. Figure 7 The network entity 706 in the embodiment may receive an indication 716 of permission for shared PRU tag assistance reporting from the PRU set 702. In addition, 1606 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0185] At 1608, the first network node may send at least a portion of a PRU tag assistance report to at least one of a second network node, a UE, or a second PRU based on the indication of permission for shared PRU tag assistance reporting. Figure 6 In another example, 1608 may be performed by a network entity 606 in the embodiment of the present invention, which may send at least a portion of a PRU tag assistance report set 626 for the UE / PRU set 602 based on an indication 616 of permission for sharing PRU tag assistance reports. Figure 7 The network entity 706 in the embodiment may send at least a portion of the PRU tag assistance report set 730 for the TRP / PRU set 704 based on the indication 716 of permission for sharing PRU tag assistance reports. In addition, 1608 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0186] At 1610, the first network node may send a configuration for a PRU. For example, 1610 may be performed by Figure 6 In another example, 1610 may be performed by a network entity 606 in the process, which may send the configuration as a PRS / SRS resource scheduling set 610 for the PRU set 604. Figure 7 The network entity 706 in the embodiment may send the configuration as a PRS / SRS resource scheduling set 714 for the PRU set 702. In addition, 1610 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0187] At 1612, the first network node may receive a PRU tag assistance report from the PRU. For example, 1612 may be performed by Figure 6In another example, 1612 may be performed by a network entity 606 in the embodiment of the present invention, which may receive a PRU tag assistance report set 626 from the PRU set 604. Figure 7 The network entity 706 in the embodiment may receive a PRU tag assistance report set 726 from the PRU set 702. In addition, 1612 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0188] At 1614, the first network node may send a TRP information and measurement exchange message including a PRU tag assistance report. For example, 1614 may be performed by Figure 6 In another example, 1614 may be performed by the network entity 606 in the PRU set 604, which may receive TRP information and measurement exchange messages including the PRU tag assistance report set 626. Figure 7 The network entity 706 in the embodiment may receive TRP information and measurement exchange messages including PRU tag assistance / measurement report set 728 from the TRP / PRU set 704. In addition, 1614 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0189] At 1616, the first network node may receive an NRPPa message including a PRU tag assistance report. For example, 1616 may be performed by Figure 6 In another example, 1616 may be performed by a network entity 606 in the embodiment of the present invention, which may receive an NRPPa message including a PRU tag assistance report set 626 from the PRU set 604. Figure 7 The network entity 706 in the embodiment may receive an NRPPa message including a PRU tag assistance report set 726 from the TRP / PRU set 704. In addition, 1616 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0190] At 1618, the first network node may receive a TRP information indication message including an indication of permission for shared PRU tag assisted reporting. For example, 1618 may be performed by Figure 6 In another example, 1618 may be performed by the network entity 606 in the embodiment of the present invention, which may receive a TRP information indication message including an indication 616 of permission for shared PRU tag assisted reporting. Figure 7The network entity 706 in the embodiment may receive a TRP information indication message including an indication 716 of permission for shared PRU tag assisted reporting. In addition, 1618 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0191] At 1620, the first network node may receive an NRPPa message including an indication of permission for shared PRU tag assisted reporting. For example, 1620 may be performed by Figure 6 In another example, 1620 may be performed by a network entity 606 in which the network entity may receive an NRPPa message including an indication 616 of permission for shared PRU tag assisted reporting. Figure 7 The network entity 706 in the embodiment may receive an NRPPa message including an indication 716 of permission for shared PRU tag assisted reporting. In addition, 1620 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0192] At 1622, the first network node may receive a capability message including an indication of permission for shared PRU tag assisted reporting. For example, 1622 may be received by Figure 6 In another example, 1622 may be performed by a network entity 606 in which the network entity may receive a capability message including an indication 616 of permission for shared PRU tag assisted reporting. Figure 7 The network entity 706 in the embodiment may receive a capability message including an indication 716 of permission for shared PRU tag assisted reporting. In addition, 1622 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19 Component 197 in is executed.

[0193] At 1624, the first network node may receive an LPPa message including an indication of permission for shared PRU tag assisted reporting. For example, 1624 may be received by Figure 6 In another example, 1624 may be performed by a network entity 606 in which the network entity may receive an LPPa message including an indication 616 of permission for shared PRU tag assisted reporting. Figure 7 The network entity 706 in the embodiment may receive an LPPa message including an indication 716 of permission for shared PRU tag assisted reporting. In addition, 1624 may be performed by Figure 1 、 Figure 3 、 Figure 18 or Figure 19Component 197 in is executed.

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

[0195] As discussed above, component 198 may be configured to receive a set of positioning signals from at least one of a UE, a first network node, or a PRU. Component 198 may be configured to measure the set of positioning signals. Component 198 may be configured to send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a set of positioning measurements based on the measured set of positioning signals. The PRU tag assistance report may include PRU assistance information associated with measuring the set of positioning signals. Component 198 may be within the cellular baseband processor 1724, the application processor 1706, or both the cellular baseband processor 1724 and the application processor 1706. 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, apparatus 1704 may include multiple components configured for various functions. In one configuration, the apparatus 1704 (and specifically the cellular baseband processor 1724 and / or the application processor 1706) may include means for receiving a set of positioning signals from at least one of the UE, the first network node, or the PRU. The means may be the component 198 of the apparatus 1704 configured to perform the functions recited by the means. As described above, the apparatus 1704 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0196] As discussed above, component 199 can be configured to transmit an SRS set for a PRU. Component 199 can be configured to receive a PRU tag assistance report from a network node. The PRU tag assistance report can include a set of positioning measurements based on the SRS set. The PRU tag assistance report can include PRU assistance information associated with the set of positioning measurements. Component 199 can reside within the cellular baseband processor 1724, the application processor 1706, or both. Component 199 can 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, apparatus 1704 can include various components configured for various functions. In one configuration, apparatus 1704 (and specifically cellular baseband processor 1724 and / or application processor 1706) can include means for transmitting an SRS set for a PRU. A means may be a component 199 of the apparatus 1704 configured to perform the functions recited by the means. As described above, the apparatus 1704 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, a 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.

[0197] Figure 18Diagram 1800 illustrates an example hardware implementation for a network entity 1802. Network entity 1802 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1802 may include at least one of a CU 1810, a DU 1830, or a RU 1840. For example, depending on the layer functionality handled by component 199, network entity 1802 may include a CU 1810; both the CU 1810 and the DU 1830; each of the CU 1810, the DU 1830, and the RU 1840; the DU 1830; both the DU 1830 and the RU 1840; or the RU 1840. CU 1810 may include a CU processor 1812. CU processor 1812 may include on-chip memory 1812′. In some aspects, CU 1810 may also include an additional memory module 1814 and a communication interface 1818. The CU 1810 communicates with the DU 1830 via a midhaul link, such as the F1 interface. The DU 1830 may include a DU processor 1832. The DU processor 1832 may include on-chip memory 1832′. In some aspects, the DU 1830 may also include an additional memory module 1834 and a communication interface 1838. The DU 1830 communicates with the RU 1840 via a fronthaul link. The RU 1840 may include a RU processor 1842. The RU processor 1842 may include on-chip memory 1842′. In some aspects, the RU 1840 may also include an additional memory module 1844, one or more transceivers 1846, an antenna 1880, and a communication interface 1848. The RU 1840 communicates with the UE 104. The on-chip memories 1812′, 1832′, 1842′ and the additional memory modules 1814, 1834, 1844 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 1812, 1832, and 1842 is responsible for general processing, including executing software stored on the computer-readable medium / memory. This software, when executed by the corresponding processor, 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.

[0198] As discussed above, component 198 may be configured to receive a set of positioning signals from at least one of a UE, a first network node, or a PRU. Component 198 may be configured to measure the set of positioning signals. Component 198 may be configured to send a PRU tag assistance report to the first network node or the second network node. The PRU tag assistance report may include a set of positioning measurements based on the measured set of positioning signals. The PRU tag assistance report may include PRU assistance information associated with measuring the set of positioning signals. Component 198 may be within one or more processors of one or more of CU 1810, DU 1830, and RU 1840. 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. Network entity 1802 may include a variety of components configured for various functions. In one configuration, the network entity 1802 may include means for receiving a set of positioning signals from at least one of a UE, a first network node, or a PRU. The means may be a component 198 of the network entity 1802 configured to perform the functions recited by the means. As described above, the network entity 1802 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0199] As discussed above, component 197 may be configured to transmit a PRS set for a PRU. Component 197 may be configured to receive a PRU tag assistance report from a second network node, such as LMF 166. The PRU tag assistance report may include a set of positioning measurements based on the PRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set. Component 197 may reside within one or more processors of one or more of CU 1810, DU 1830, and RU 1840. Component 197 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 1802 may include various components configured for various functions. In one configuration, network entity 1802 may include a component for transmitting a PRS set for a PRU. The component may be component 197 of network entity 1802 configured to perform the functions recited by the component. As described above, the network entity 1802 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, a component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by that component.

[0200] As discussed above, component 196 can be configured to send a request for a PRU tag assistance report to a PRU associated with a set of positioning signals transmitted or received by the PRU. Component 196 can receive a PRU tag assistance report including a set of PRU assistance information associated with the set of positioning signals. Component 196 can reside within one or more processors of one or more of CU 1810, DU 1830, and RU 1840. Component 196 can 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 1802 can include various components configured for various functions. In one configuration, network entity 1802 can include a component for sending a request for a PRU tag assistance report to a PRU associated with a set of positioning signals transmitted or received by the PRU. The component can be component 196 of network entity 1802 configured to perform the functions recited by the component. As described above, the network entity 1802 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, a component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by that component.

[0201] Figure 19 Diagram 1900 illustrates an example hardware implementation for a network entity 1960. In one example, network entity 1960 may be located within core network 120. Network entity 1960 may include a network processor 1912. Network processor 1912 may include on-chip memory 1912′. In some aspects, network entity 1960 may also include an additional memory module 1914. Network entity 1960 communicates with CU 1902 via network interface 1980, either directly (e.g., a backhaul link) or indirectly (e.g., via a RIC). On-chip memory 1912′ and additional memory module 1914 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Processor 1912 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, this software enables 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.

[0202] As discussed above, component 197 may be configured to transmit a PRS set for a PRU. Component 197 may be configured to receive a PRU tag assistance report from a second network node, such as LMF 166. The PRU tag assistance report may include a set of positioning measurements based on the PRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set. Component 197 may be within processor 1912. Component 197 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 1960 may include various components configured for various functions. In one configuration, network entity 1960 may include a component for transmitting a PRS set for a PRU. The component may be component 197 of network entity 1960 configured to perform the functions recited by the component.

[0203] As discussed above, component 196 can be configured to send a request for a PRU tag assistance report to a PRU associated with a set of positioning signals transmitted or received by the PRU. Component 196 can receive a PRU tag assistance report including a set of PRU assistance information associated with the set of positioning signals. Component 196 can be within processor 1912. Component 196 can 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 1960 can include various components configured for various functions. In one configuration, network entity 1960 can include means for sending a request for a PRU tag assistance report to a PRU associated with a set of positioning signals transmitted or received by the PRU. The means can be component 196 of network entity 1960 configured to perform the functions recited by the means.

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

[0205] 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, references to elements in the singular do 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 herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily to be interpreted as preferred or having an advantage 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 or sends data to a second device, the data may be received / sent directly between the first and second devices, or indirectly between the first and second devices via a collection of devices. A device configured to "output" data (such as a transmission, signal, or message) may, for example, transmit the data using a transceiver, or may transmit the data to the device that transmitted the data. A device configured to "obtain" data (such as a transmission, signal, or message) may, for example, receive the data using a transceiver, or may obtain the data from the device that received the data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed 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 is to be construed as part-plus-function unless the element is explicitly recited using the phrase "means for..."

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

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

[0208] Aspect 1 is a method of wireless communication at a wireless device, wherein the method may include receiving a set of positioning signals from at least one of a UE, a first network node, or a PRU. The method may include measuring the set of positioning signals. The method may include sending a PRU tag assistance report to the first network node or a second network node. The PRU tag assistance report may include a set of positioning measurements based on the measured set of positioning signals. The PRU tag assistance report may include PRU assistance information associated with measuring the set of positioning signals.

[0209] Aspect 2 is a method according to Aspect 1, wherein the PRU assistance information may include at least one of the following: (a) a first indication of the location of at least one PRU; (b) a second indication of the beam angle associated with the positioning signal set; (c) a third indication of the antenna orientation associated with receiving the positioning signal set; (d) a fourth indication of the group delay associated with the positioning measurement set; (e) a fifth indication of the sensor measurement associated with the positioning measurement set; (f) a sixth indication of the sensor type associated with at least one PRU; (g) a seventh indication of the synchronization error associated with the positioning measurement set; (h) an eighth indication of the timing error associated with the positioning measurement set; or (i) a ninth indication of the clock drift range associated with the positioning measurement set.

[0210] Aspect 3 is a method according to any one of Aspects 1 or 2, wherein sending the PRU tag assistance report may include sending TRP information and a measurement exchange message including the PRU tag assistance report.

[0211] Aspect 4 is a method according to any one of aspects 1 to 3, wherein sending the PRU tag assistance report may include sending an NRPPa message including the PRU tag assistance report.

[0212] Aspect 5 is a method according to any one of aspects 1 to 4, wherein the method may include sending an indication of permission to share the PRU tag assistance report to at least one of the first network node or the second network node.

[0213] Aspect 6 is a method according to Aspect 5, wherein the permission to share the PRU tag assistance report may include at least one of the following: (a) a UE ID set associated with a UE set authorized to receive the PRU tag assistance report; (b) a first indication of a UE vendor associated with a first UE set authorized to receive the PRU tag assistance report; (c) a second indication of a UE chip vendor associated with a second UE set authorized to receive the PRU tag assistance report; (d) a TRP ID set associated with a TRP authorized to receive the PRU tag assistance report; (e) a third indication of a NW operator associated with the first TRP set authorized to receive the PRU tag assistance report; or (f) a fourth indication of a NW vendor associated with a second TRP set authorized to receive the PRU tag assistance report.

[0214] Aspect 7 is a method according to any one of Aspects 5 or 6, wherein sending the indication of the permission to share the PRU tag assistance report may include sending a TRP information indication message including the indication of the permission to share the PRU tag assistance report.

[0215] Aspect 8 is a method according to any one of aspects 5 to 7, wherein sending the indication of the permission to share the PRU tag assistance report may include sending an NRPPa message including the indication of the permission to share the PRU tag assistance report.

[0216] Aspect 9 is a method according to any one of aspects 5 to 8, wherein sending the indication of the permission to share the PRU tag assistance report may include sending a capability message including the indication of the permission to share the PRU tag assistance report.

[0217] Aspect 10 is a method according to any one of aspects 5 to 9, wherein sending the indication of the permission to share the PRU tag assistance report may include sending an LPPa message including the indication of the permission to share the PRU tag assistance report.

[0218] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the method may include receiving a configuration of the set of positioning signals from at least one of the first network node or the second network node. Receiving the set of positioning signals may be based on the configuration.

[0219] Aspect 12 is a method according to any one of aspects 1 to 11, wherein the method may include receiving a request from at least one of the first network node or the second network node to send the PRU tag assistance report. Sending the PRU tag assistance report may be in response to receiving the request.

[0220] Aspect 13 is a method according to any one of aspects 1 to 12, wherein the wireless device may include a second PRU.

[0221] Aspect 14 is a method according to any one of aspects 1 to 13, wherein at least one of the first network node or the second network node may include a LMF.

[0222] Aspect 15 is a method according to any one of aspects 1 to 14, wherein the set of positioning signals may include at least one of a PRS or an SRS.

[0223] Aspect 16 is a method according to any one of aspects 1 to 15, wherein the method may include sending a second set of positioning signals to at least one of the UE, the first network node, or the PRU. The method may include sending second PRU assistance information associated with the second set of positioning signals to at least one of the first network node or the second network node.

[0224] Aspect 17 is a method according to aspect 16, wherein the second set of positioning signals may include at least one of a PRS or an SRS.

[0225] Aspect 18 is a method according to any one of Aspects 16 or 17, wherein the second PRU assistance information may include at least one of the following: (a) a first indication of the position of at least one PRU; (b) a second indication of the beam angle associated with the second positioning signal set; (c) a third indication of the antenna orientation associated with sending the second positioning signal set; (d) a fourth indication of the group delay associated with the second positioning signal set; (e) a fifth indication of the synchronization error associated with the second positioning signal set; (f) a sixth indication of the timing error associated with the second positioning signal set; or (g) a seventh indication of the clock drift range associated with the second positioning signal set.

[0226] Aspect 19 is a method of wireless communication at a UE, wherein the method may include transmitting an SRS set for a PRU. The method may include receiving a PRU tag assistance report from a network node. The PRU tag assistance report may include a positioning measurement set based on the SRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set.

[0227] Aspect 20 is a method according to Aspect 19, wherein the PRU assistance information may include at least one of the following: (a) a first indication of the location of at least one PRU; (b) a second indication of the beam angle associated with the SRS set; (c) a third indication of the antenna orientation associated with receiving the SRS set; (d) a fourth indication of the group delay associated with the positioning measurement set; (e) a fifth indication of the sensor measurement associated with the positioning measurement set; (f) a sixth indication of the sensor type associated with at least one PRU; (g) a seventh indication of the synchronization error associated with the positioning measurement set; (h) an eighth indication of the timing error associated with the positioning measurement set; or (i) a ninth indication of the clock drift range associated with the positioning measurement set.

[0228] Aspect 21 is a method of wireless communications at a network node, wherein receiving a PRU tag assistance report from the network node may include receiving an assistance exchange message including the PRU tag assistance report.

[0229] Aspect 22 is a method according to any one of aspects 19 to 21, wherein receiving the PRU tag assistance report from the network node may include receiving an LPPa message including the PRU tag assistance report.

[0230] Aspect 23 is a method according to any one of aspects 19 to 22, wherein the method may include sending a request to the network node to send the PRU tag assistance report.

[0231] Aspect 24 is a method according to aspect 23, wherein the method may include sending an auxiliary exchange message including the request.

[0232] Aspect 25 is a method according to any one of aspects 19 to 24, wherein the method may include sending a request to the network node to configure an SRS resource set. The method may include receiving a configuration of the SRS resource set from the network node. Sending the SRS set to the PRU may include sending the SRS set based on the SRS resource set.

[0233] Aspect 26 is a method according to any one of aspects 19 to 25, wherein the method may include receiving a PRS set from the PRU, measuring the PRS set, and calculating a position of the UE based on the measured PRS set and the positioning measurement set.

[0234] Aspect 27 is a method according to aspect 26, wherein the method may include receiving second PRU assistance information associated with the PRS set from the network node. Calculating the position of the UE may also be based on the second PRU assistance information. Receiving the second PRU assistance information may include receiving a PRU tag assistance report including the second PRU assistance information.

[0235] Aspect 28 is a method according to aspect 27, wherein the second PRU assistance information may include at least one of the following: (a) a first indication of the location of at least one PRU; (b) a second indication of the beam angle associated with the PRS set; (c) a third indication of the antenna orientation associated with transmitting the PRS set; (d) a fourth indication of the group delay associated with the PRS set; (e) a fifth indication of the synchronization error associated with the PRS set; (f) a sixth indication of the timing error associated with the PRS set; or (g) a seventh indication of the clock drift range associated with the PRS set.

[0236] Aspect 29 is a method of wireless communication at a first network node, wherein the method may include sending a PRS set for a PRU. The method may include receiving a PRU tag assistance report from a second network node. The PRU tag assistance report may include a positioning measurement set based on the PRS set. The PRU tag assistance report may include PRU assistance information associated with the positioning measurement set.

[0237] Aspect 30 is a method according to aspect 29, wherein the PRU assistance information may include at least one of the following: (a) a first indication of the location of at least one PRU; (b) a second indication of the beam angle associated with the PRS set; (c) a third indication of the antenna orientation associated with receiving the PRS set; (d) a fourth indication of the group delay associated with the positioning measurement set; (e) a fifth indication of the sensor measurement associated with the positioning measurement set; (f) a sixth indication of the sensor type associated with at least one PRU; (g) a seventh indication of the synchronization error associated with the positioning measurement set; (h) an eighth indication of the timing error associated with the positioning measurement set; or (i) a ninth indication of the clock drift range associated with the positioning measurement set.

[0238] Aspect 31 is a method according to any one of aspects 29 or 30, wherein receiving the PRU tag assistance report from the second network node may include receiving an assistance exchange message including the PRU tag assistance report.

[0239] Aspect 32 is a method according to any one of aspects 29 to 31, wherein receiving the PRU tag assistance report from the second network node may include receiving an NRPPa message including the PRU tag assistance report.

[0240] Aspect 33 is a method according to any one of aspects 29 to 32, wherein the method may include sending a request to the second network node to send the PRU tag assistance report.

[0241] Aspect 34 is a method according to aspect 33, wherein sending the request may include sending an auxiliary exchange message including the request. The auxiliary exchange message may be sent as part of an NRPPa framework or interface. The NRPPa may include the sent auxiliary exchange message.

[0242] Aspect 35 is a method according to any one of aspects 29 to 34, wherein the method may include configuring a configuration of a PRS resource set for the PRS set. The method may include sending the configuration for the PRU. Sending the PRS set may include sending the PRS set based on the configuration.

[0243] Aspect 36 is a method according to any one of aspects 29 to 35, wherein the method may include receiving an SRS set from the PRU, measuring the SRS set, and calculating a position of the PRU based on the measured SRS set and the positioning measurement set.

[0244] Aspect 37 is a method according to aspect 36, wherein the method may include receiving second PRU assistance information associated with the SRS set from the second network node. Calculating the position of the PRU may also be based on the second PRU assistance information.

[0245] Aspect 38 is a method according to aspect 37, wherein the second PRU auxiliary information may include at least one of the following: (a) a first indication of the position of at least one PRU; (b) a second indication of the beam angle associated with the SRS set; (c) a third indication of the antenna orientation associated with transmitting the SRS set; (d) a fourth indication of the group delay associated with the SRS set; (e) a fifth indication of the synchronization error associated with the SRS set; (f) a sixth indication of the timing error associated with the SRS set; or (g) a seventh indication of the clock drift range associated with the SRS set.

[0246] Aspect 39 is a method according to any one of aspects 29 to 38, wherein the second network node may include a LMF.

[0247] Aspect 40 is a method of wireless communication at a network entity, wherein the method may include sending a configuration of a set of positioning signals for transmission or reception using a PRU. The method may include receiving a PRU tag assistance report including a set of PRU assistance information associated with the set of positioning signals.

[0248] Aspect 41 is a method according to aspect 40, wherein the PRU tag assistance report may include a set of positioning measurements based on a set of measured positioning signals.

[0249] Aspect 42 is a method according to any one of Aspects 40 or 41, wherein the PRU assistance information may include at least one of the following: (a) a first indication of the location of at least one PRU; (b) a second indication of the beam angle associated with the positioning signal set; (c) a third indication of the first antenna orientation associated with sending the positioning signal set; (d) a fourth indication of the second antenna orientation associated with receiving the positioning signal set; (e) a fifth indication of the group delay associated with the positioning signal set; (f) a sixth indication of the sensor measurement associated with the positioning signal set; (g) a seventh indication of the sensor type associated with at least one PRU; (h) an eighth indication of the synchronization error associated with the positioning signal set; (i) a ninth indication of the timing error associated with the positioning signal set; or (j) a tenth indication of the clock drift range associated with the positioning signal set.

[0250] Aspect 43 is a method according to any one of aspects 40 to 42, wherein receiving the PRU tag assistance report may include receiving TRP information and a measurement exchange message including the PRU tag assistance report. Receiving the PRU tag assistance report may include receiving an assistance data exchange message including the PRU tag assistance report.

[0251] Aspect 44 is a method according to any one of aspects 40 to 43, wherein receiving the PRU tag assistance report may include receiving an NRPPa message including the PRU tag assistance report. Receiving the PRU tag assistance report may include receiving an LPPa message including the PRU tag assistance report.

[0252] Aspect 45 is a method according to any one of aspects 40 to 44, wherein the method may include receiving an indication of permission to share the PRU tag assistance report.

[0253] Aspect 46 is a method according to aspect 45, wherein the permission to share the PRU tag assistance report may include at least one of the following: (a) a set of UE IDs associated with a set of UEs authorized to receive the PRU tag assistance report; (b) a first indication of a UE vendor associated with a first set of UEs authorized to receive the PRU tag assistance report; (c) a second indication of a UE chip vendor associated with a second set of UEs authorized to receive the PRU tag assistance report; (d) a set of TRP IDs associated with a TRP authorized to receive the PRU tag assistance report; (e) a third indication of a NW operator associated with the first set of TRPs authorized to receive the PRU tag assistance report; or (f) a fourth indication of a NW vendor associated with a second set of TRPs authorized to receive the PRU tag assistance report.

[0254] Aspect 47 is a method according to aspect 45, wherein receiving the indication of the permission to share the PRU tag assistance report may include receiving a TRP information indication message including the indication of the permission to share the PRU tag assistance report.

[0255] Aspect 48 is a method according to any one of aspects 45 or 47, wherein receiving the indication of the permission to share the PRU tag assistance report may include receiving an NRPPa message including the indication of the permission to share the PRU tag assistance report.

[0256] Aspect 49 is a method according to any one of aspects 45, 47 or 48, wherein receiving the indication of the permission to share the PRU tag assistance report may include receiving a capability message including the indication of the permission to share the PRU tag assistance report.

[0257] Aspect 50 is a method according to any one of aspects 45 or 47 to 49, wherein receiving the indication of the permission to share the PRU tag assistance report may include receiving an LPPa message including the indication of the permission to share the PRU tag assistance report.

[0258] Aspect 51 is a method according to any one of aspects 45 or 47 to 50, wherein the method may include sending at least a portion of the PRU tag assistance report to at least one of a second network node, a UE, or a second PRU based on the indication of the permission to share the PRU tag assistance report.

[0259] Aspect 52 is a method according to any one of aspects 40 to 51, wherein the method may include sending a configuration of the set of positioning signals. The set of positioning signals may be sent or received using the PRU based on the configuration.

[0260] Aspect 53 is a method according to any one of aspects 40 to 52, wherein sending the request may include sending the request for a PRU. Receiving the PRU tag assistance report may include receiving the PRU tag assistance report from the PRU.

[0261] Aspect 54 is a method according to any one of aspects 40 to 53, wherein the network node may include a LMF.

[0262] Aspect 55 is a method according to any one of aspects 40 to 54, wherein the set of positioning signals may include at least one of a PRS or an SRS.

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

[0264] Aspect 57 is the apparatus of aspect 56, further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0265] Aspect 58 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 55.

[0266] Aspect 59 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 55.

Claims

1. An apparatus for wireless communication at a wireless device, 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: receiving a set of positioning signals from at least one of a user equipment (UE), a first network node, or a positioning reference unit (PRU); measuring the positioning signal set; as well as A PRU tag assistance report is sent to the first network node or the second network node, where the PRU tag assistance report includes a positioning measurement set based on the measured positioning signal set and includes PRU assistance information associated with measuring the positioning signal set.

2. The apparatus according to claim 1, wherein the PRU assistance information comprises at least one of the following: a first indication of a location of at least one PRU; a second indication of a beam angle associated with the set of positioning signals; a third indication of an antenna orientation associated with receiving the set of positioning signals; a fourth indication of a group delay associated with the positioning measurement set; a fifth indication of sensor measurements associated with the positioning measurement set; a sixth indication of a sensor type associated with the at least one PRU; a seventh indication of a synchronization error associated with the set of positioning measurements; an eighth indication of a timing error associated with the positioning measurement set; or A ninth indication of a clock drift range associated with the positioning measurement set.

3. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, wherein To send the PRU tag assistance report, the at least one processor is configured to: Transmitting reception point (TRP) information and a measurement exchange message including the PRU tag assistance report via the transceiver.

4. The device according to claim 1, wherein To send the PRU tag assistance report, the at least one processor is configured to: A New Radio (NR) Positioning Protocol (NRPP) Annex (NRPPa) message including the PRU Tag Assistance Report is sent.

5. The apparatus of claim 1 , wherein the at least one processor is further configured to: An indication of permission to share the PRU tag assistance report is sent to at least one of the first network node or the second network node.

6. The apparatus of claim 5, wherein the permission to share the PRU tag assistance report comprises at least one of: a set of UE identifiers (IDs) associated with a set of UEs that are authorized to receive the PRU tag assistance report; a first indication of a UE vendor associated with a first set of UEs that are authorized to receive the PRU tag assistance report; a second indication to UE chipset vendors associated with a second set of UEs that are authorized to receive the PRU tag assistance report; a set of Transmit Receiving Point (TRP) identifiers (IDs) associated with the TRPs that are authorized to receive the PRU tag assistance reports; a third indication to a network (NW) operator associated with the first set of TRPs that is authorized to receive said PRU tag assistance report; or A fourth indication to a NW provider associated with a second set of TRPs that are authorized to receive the PRU tag assistance report.

7. The device according to claim 5, wherein To send the indication of the permission to share the PRU tag assistance report, the at least one processor is configured to: A Transmission Reception Point (TRP) information indication message is sent including the indication of the permission to share the PRU tag assistance report.

8. The device according to claim 5, wherein To send the indication of the permission to share the PRU tag assistance report, the at least one processor is configured to: A New Radio (NR) Positioning Protocol (NRPP) Annex (NRPPa) message is sent including the indication of the permission to share the PRU tag assistance report.

9. The device according to claim 5, wherein To send the indication of the permission to share the PRU tag assistance report, the at least one processor is configured to: A capability message is sent including the indication of the permission to share the PRU tag assistance report.

10. The device according to claim 5, wherein To send the indication of the permission to share the PRU tag assistance report, the at least one processor is configured to: A Long Term Evolution (LTE) Positioning Protocol (LPP) Annex (LPPa) message is sent including the indication of the permission to share the PRU tag assistance report.

11. The apparatus of claim 1 , wherein the at least one processor is further configured to: The configuration of the positioning signal set is received from at least one of the first network node or the second network node, wherein: To receive the set of positioning signals, the at least one processor is configured to receive the set of positioning signals based on the configuration.

12. The apparatus of claim 1 , wherein the at least one processor is further configured to: A request to send the PRU tag assistance report is received from at least one of the first network node or the second network node, wherein: To send the PRU tag assistance report, the at least one processor is configured to send the PRU tag assistance report in response to receiving the request.

13. The apparatus of claim 1, wherein the wireless device comprises a second PRU.

14. The apparatus of claim 1, wherein at least one of the first network node or the second network node comprises a location management function (LMF).

15. The apparatus of claim 1, wherein the set of positioning signals comprises at least one of a positioning reference signal (PRS) or a sounding reference signal (SRS).

16. The apparatus of claim 1 , wherein the at least one processor is further configured to: sending a second set of positioning signals to at least one of the UE, the first network node, or a second PRU; and Second PRU assistance information associated with the second positioning signal set is sent to at least one of the first network node or the second network node. 17 . The apparatus of claim 16 , wherein the second set of positioning signals comprises at least one of a positioning reference signal (PRS) or a sounding reference signal (SRS).

18. The apparatus according to claim 16, wherein the second PRU assistance information comprises at least one of the following: a first indication of a location of at least one PRU; a second indication of a beam angle associated with the second set of positioning signals; a third indication of an antenna orientation associated with transmitting the second set of positioning signals; a fourth indication of a group delay associated with the second positioning signal set; a fifth indication of synchronization error associated with the second set of positioning signals; a sixth indication of a timing error associated with the second positioning signal set; or A seventh indication of a clock drift range associated with the second positioning signal set.

19. 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: transmitting a set of sounding reference signals (SRS) for a positioning reference unit (PRU); and A PRU tag assistance report is received from a network node, the PRU tag assistance report including a positioning measurement set based on the SRS set and including PRU assistance information associated with the positioning measurement set.

20. The apparatus of claim 19, wherein the PRU assistance information comprises at least one of the following: a first indication of a location of at least one PRU; a second indication of a beam angle associated with the SRS set; a third indication of an antenna orientation associated with receiving the set of SRS; a fourth indication of a group delay associated with the positioning measurement set; a fifth indication of sensor measurements associated with the positioning measurement set; a sixth indication of a sensor type associated with the at least one PRU; a seventh indication of a synchronization error associated with the set of positioning measurements; an eighth indication of a timing error associated with the positioning measurement set; or A ninth indication of a clock drift range associated with the positioning measurement set.

21. The apparatus of claim 19, further comprising a transceiver coupled to the at least one processor, wherein To receive the PRU tag assistance report from the network node, the at least one processor is configured to: An assistance exchange message including the PRU tag assistance report is received via the transceiver.

22. The apparatus according to claim 19, wherein To receive the PRU tag assistance report from the network node, the at least one processor is configured to: A Long Term Evolution (LTE) Positioning Protocol (LPP) Annex (LPPa) message including the PRU tag assistance report is received.

23. The apparatus of claim 19, wherein the at least one processor is further configured to: A request to send the PRU tag assistance report is sent to the network node.

24. The device according to claim 23, wherein To send the request, the at least one processor is configured to: An auxiliary exchange message including the request is sent.

25. The apparatus of claim 19, wherein the at least one processor is further configured to: sending a request for configuring an SRS resource set to the network node; and receiving a configuration of the SRS resource set from the network node, wherein: To transmit the SRS set to the PRU, the at least one processor is configured to transmit the SRS set based on the SRS resource set.

26. The apparatus of claim 19, wherein the at least one processor is further configured to: receiving a positioning reference signal (PRS) set from the PRU; measuring the PRS set; and The position of the UE is calculated based on the measured PRS set and the positioning measurement set.

27. The apparatus of claim 26, wherein the at least one processor is further configured to: receiving second PRU assistance information associated with the PRS set from the network node, wherein: To calculate the position of the UE, the at least one processor is configured to calculate the position of the UE further based on the second PRU assistance information.

28. The apparatus of claim 27, wherein the second PRU assistance information comprises at least one of the following: a first indication of a location of at least one PRU; a second indication of a beam angle associated with the set of PRSs; a third indication of an antenna orientation associated with transmitting the set of PRSs; a fourth indication of a group delay associated with the PRS set; a fifth indication of a synchronization error associated with the set of PRSs; a sixth indication of a timing error associated with the set of PRSs; or A seventh indication of a clock drift range associated with the set of PRSs.

29. A method of wireless communication at a wireless device, the method comprising: receiving a set of positioning signals from at least one of a user equipment (UE), a first network node, or a positioning reference unit (PRU); measuring the positioning signal set; as well as A PRU tag assistance report is sent to the first network node or the second network node, where the PRU tag assistance report includes a positioning measurement set based on the measured positioning signal set and includes PRU assistance information associated with measuring the positioning signal set.

30. A method of wireless communication at a user equipment (UE), the method comprising: Sending a set of sounding reference signals (SRS) for positioning reference units (PRUs); as well as A PRU tag assistance report is received from a network node, the PRU tag assistance report including a positioning measurement set based on the SRS set and including PRU assistance information associated with the positioning measurement set.

Images