Method and apparatus for selective cancellation of on-demand positioning reference signal (PRS) occasions

Abstract

Various techniques for wireless communications are disclosed. In an aspect, a user equipment (UE) receives a positioning reference signal (PRS) configuration from a network entity. The UE receives a measurement gap (MG) configuration from a serving base station. The UE determines that one or more transmission properties of one or more resources should be modified and transmits PRS modification information to the network entity based on the one or more transmission properties of the one or more PRS resources to be modified. The network entity can be a location server or a location management function.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Patent Application No. 17 / 373,999, filed July 13, 2021, entitled “SELECTIVE CANCELLATION OF ON-DEMAND POSITIONING REFERENCE SIGNAL (PRS) OCCASIONS,” which claims priority to U.S. Provisional Patent Application No. 63 / 057,272, filed July 27, 2020, entitled “SELECTIVE CANCELLATION OF ON-DEMAND POSITIONING REFERENCE SIGNAL (PRS) OCCASIONS,” each of which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety.

[0003] Public background

[0004] 1. Public domain

[0005] The various aspects of this disclosure generally relate to wireless communications.

[0006] 2. Relevant Technical Descriptions

[0007] Wireless communication systems have undergone several generations of development, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data radio service with Internet capabilities, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), etc.

[0008] The fifth-generation (5G) wireless standard (known as New Radio (NR)) demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide tens of megabits per second (Mbps) of data rate to each of tens of thousands of users, and 1 gigabits per second (Gbps) to dozens of employees on an office floor. It should support hundreds of thousands of simultaneous connections to support large-scale sensor deployments. Therefore, 5G mobile communication should have significantly improved spectral efficiency compared to the current 4G standard. Furthermore, signaling efficiency should be improved and latency significantly reduced compared to the current standard.

[0009] Overview

[0010] The following is a simplified overview relating to one or more aspects disclosed herein. Therefore, this overview should not be considered an exhaustive overview relating to all aspects of the conception, nor should it be considered to identify key or decisive elements relating to all aspects of the conception or to depict the scope associated with any particular aspect. Accordingly, the sole purpose of the following overview is to present, in a simplified form, certain concepts relating to one or more aspects of the mechanism disclosed herein before the detailed description given below.

[0011] In one aspect, a wireless communication method performed by a user equipment (UE) includes: receiving a positioning reference signal (PRS) configuration from a network entity; receiving a measurement gap (MG) configuration from a serving base station; determining that one or more transmission attributes of one or more PRS resources should be modified; and transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0012] In one aspect, a wireless communication method performed by a network entity includes: transmitting a Positioning Reference Signal (PRS) configuration to a user equipment (UE); receiving PRS modification information from the UE; updating the PRS configuration for the UE based on the PRS modification information; and transmitting the updated PRS configuration to the UE.

[0013] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a Position Reference Signal (PRS) configuration from a network entity; receive a Measurement Gauge (MG) configuration from a serving base station; determine that one or more transmission attributes of one or more PRS resources should be modified; and cause the at least one transceiver to transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0014] In one aspect, a network entity includes: a memory; at least one network interface; and at least one processor communicatively coupled to the memory and the at least one network interface, the at least one processor being configured to: cause the at least one network interface to transmit a Position Reference Signal (PRS) configuration to a user equipment (UE); receive PRS modification information from the UE; update the PRS configuration for the UE based on the PRS modification information; and cause the at least one network interface to transmit the updated PRS configuration to the UE.

[0015] In one aspect, a user equipment (UE) includes: means for receiving a positioning reference signal (PRS) configuration from a network entity; means for receiving a measurement gap (MG) configuration from a serving base station; means for determining that one or more transmission attributes of one or more PRS resources should be modified; and means for transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0016] In one aspect, a network entity includes: means for transmitting a Position Reference Signal (PRS) configuration to a user equipment (UE); means for receiving PRS modification information from the UE; means for updating the PRS configuration for the UE based on the PRS modification information; and means for transmitting the updated PRS configuration to the UE.

[0017] In one aspect, a non-transient computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a Position Reference Signal (PRS) configuration from a network entity; receive a Measurement Gauge (MG) configuration from a serving base station; determine that one or more transmission attributes of one or more PRS resources should be modified; and transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0018] In one aspect, a non-transient computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: transmit a Positioning Reference Signal (PRS) configuration to a user equipment (UE); receive PRS modification information from the UE; update the PRS configuration for the UE based on the PRS modification information; and transmit the updated PRS configuration to the UE.

[0019] Other objectives and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. Brief description of the attached diagram

[0021] The accompanying drawings are provided to help describe examples of one or more aspects of the disclosed subject matter, and these drawings are provided merely to illustrate the examples and not to limit the scope thereof:

[0022] Figure 1 Exemplary wireless communication systems based on various aspects are explained;

[0023] Figure 2A and Figure 2B The example wireless network architecture is explained from various aspects;

[0024] Figures 3A to 3C It is a simplified block diagram of several exemplary aspects of components that can be adopted in wireless communication nodes and configured to support communication according to various aspects;

[0025] Figure 4A and 4B It is an explanation of example frame structures based on various aspects and diagrams of the channels within these frame structures;

[0026] Figure 5 This is a diagram illustrating an exemplary Positioning Reference Signal (PRS) configuration for PRS transmission at a given base station, based on various aspects.

[0027] Figure 6 It is a diagram illustrating how to specify the measurement gap pattern based on the parameters in the measurement gap (MG) configuration of various aspects;

[0028] Figure 7 This is a signaling message transmission diagram illustrating how the User Equipment (UE) receives and uses PRS and MG configuration information;

[0029] Figure 8 It explains some of the problems encountered by conventional networks related to PRS and MG configuration;

[0030] Figure 9 It explains some solutions to problems related to PRS and MG configuration from various aspects;

[0031] Figure 10 This is a signaling message passing diagram illustrating how the UE can modify the PRS configuration based on various aspects; and

[0032] Figures 11 to 13 Exemplary wireless communication methods according to various aspects of this disclosure have been explained.

[0033] Detailed description

[0034] Various aspects of this disclosure are provided below in the description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of this disclosure. Furthermore, elements well-known in this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0035] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than the others. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0036] Those skilled in the art will appreciate that the information and signals described below can be represented using any of a variety of different techniques and arts. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0037] Furthermore, many aspects are described in the form of sequences of actions performed by elements of, for example, computing devices. It will be appreciated that the various actions described herein can be performed by special-purpose circuitry (e.g., application-specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequences of actions described herein can be considered to be fully embodied in any form of non-transient computer-readable storage medium storing a corresponding set of computer instructions that, upon execution, will cause an associated processor of the device to perform the functions described herein. Thus, various aspects of this disclosure can be embodied in several different forms, all of which are contemplated to fall within the scope of the claimed subject matter. Furthermore, for each aspect described herein, a corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0038] As used herein, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise stated. Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT”, “Client Equipment”, “Wireless Equipment”, “Subscriber Equipment”, “Subscriber Terminal”, “Subscriber Station”, “User Terminal” (UT), “Mobile Equipment”, “Mobile Terminal”, “Mobile Station”, or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) (e.g., based on IEEE 802.11, etc.).

[0039] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which it is deployed, and may be alternatively referred to as an Access Point (AP), Network Node, B-Node, Evolved B-Node (eNB), Next Generation eNB (ng-eNB), New Radio (NR) B-Node (also referred to as gNB or gNodeB), etc. A base station may primarily be used to support radio access by the UE, including supporting data, voice, and / or signaling connections with the supported UE. In some systems, the base station may provide purely edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can signal to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can signal to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0040] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be located in the same place. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple physical TRPs located in the same place, the physical TRP may be an antenna array of the base station (e.g., in a multiple-input multiple-output (MIMO) system or in the case of beamforming at the base station). When the term "base station" refers to multiple physical TRPs not located in the same place, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, physical TRPs not located in the same place may be the serving base station from which the UE receives measurement reports and neighboring base stations where the UE is measuring its reference radio frequency (RF) signal (or simply "reference signal"). Since a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmissions from or receptions at a base station should be understood as references to the specific TRP of that base station.

[0041] In some implementations that support UE positioning, the base station may not support the UE's radio access (e.g., it may not support data, voice, and / or signaling connections regarding the UE), but may instead transmit reference signals to the UE for measurement, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning tower (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0042] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information across the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of individual RF signals through a multipath channel, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same RF signal transmitted on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal,” where the context clearly indicates that the term “signal” refers to a wireless signal or an RF signal.

[0043] Figure 1An exemplary wireless communication system 100 according to various aspects has been described. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. Base station 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, macrocell base stations may include eNBs and / or ng-eNBs (where wireless communication system 100 corresponds to an LTE network), or gNBs (where wireless communication system 100 corresponds to an NR network), or a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

[0044] Each base station 102 can collectively form a RAN and interface with the core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) via a backhaul link 122, and connect to one or more location servers 172 (which may be part of the core network 170 or external to it) via the core network 170. Among other functions, the base station 102 can also perform functions related to one or more of the following: transmitting user data, radio channel cryptography and decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of alarm messages. The base stations 102 can communicate with each other directly or indirectly (e.g., via EPC / 5GC) via a backhaul link 134 (which may be wired or wireless).

[0045] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographical coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each coverage area 110. A “cell” is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI)) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access to different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or others). Since cells are supported by specific base stations, the term “cell” can refer to either or both of the logical communication entity and the base station supporting that logical communication entity, depending on the context. Additionally, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" are used interchangeably. In some cases, the term "cell" can also refer to the geographical coverage area (e.g., sector) of a base station, in the sense that the carrier frequency can be detected and used for communication within a portion of a geographical coverage area 110.

[0046] While the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in handover areas), some geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that provide service to a restricted group known as a Closed Subscriber Group (CSG).

[0047] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may use one or more carrier frequencies. Carrier allocation may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink).

[0048] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 communicating with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a clear channel assessment (CCA) or listen-before-speak (LBT) procedure to determine channel availability before communication.

[0049] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as used by WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can enhance access network coverage and / or increase access network capacity. NR in unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0050] The wireless communication system 100 may further include a millimeter-wave (mmW) base station 180, which can operate in mmW and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to a 3 GHz frequency with a 100 mm wavelength. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW RF bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be appreciated that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Accordingly, it will be understood that the foregoing explanations are merely illustrative and should not be construed as limiting the aspects disclosed herein.

[0051] Transmit beamforming is a technique for focusing RF signals in a specific direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing the receiving device with a faster (in terms of data rate) and stronger RF signal. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (referred to as a "phased array" or "antenna array") that generates a beam of RF waves, which can be "guided" to different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to the individual antennas with the correct phase relationship so that radio waves from the separate antennas add together in the desired direction to increase radiation, while canceling each other out in the undesired direction to suppress radiation.

[0052] Transmit beams can be quasi-co-located, meaning they appear to the receiver (e.g., the UE) to have the same parameters regardless of whether the transmit antennas of network nodes are physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters of the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of the second reference RF signal transmitted on the same channel.

[0053] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array and / or adjust the phase setting of the antenna array in a specific direction to amplify the RF signal received from that direction (e.g., increase its gain level). Thus, when a receiver is referred to as beamforming in a certain direction, it means that the beam gain in that direction is higher than the beam gain in other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal strength (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), etc.) of the RF signal received from that direction.

[0054] The receive beam can be spatially dependent. Spatial dependency means that the parameters of the transmit beam used for the second reference signal can be derived from information about the receive beam of the first reference signal. For example, the UE can use a specific receive beam to receive one or more reference downlink reference signals (e.g., Position Reference Signal (PRS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell-Specific Reference Signal (CRS), Channel State Information Reference Signal (CSI-RS), Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Synchronization Block (SSB), etc.) from the base station. The UE can then form a transmit beam based on the parameters of the receive beam to transmit one or more uplink reference signals (e.g., Uplink Position Reference Signal (UL-PRS), Detection Reference Signal (SRS), Demodulation Reference Signal (DMRS), PTRS, etc.) to the base station.

[0055] Note that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, then the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, then the downlink beam is a receive beam for receiving downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if a base station is forming an uplink beam, then the uplink beam is an uplink receive beam, while if a UE is forming an uplink beam, then the uplink beam is an uplink transmit beam.

[0056] In 5G, the spectrum in which radio nodes (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems (such as 5G), one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCell.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182 and on the cell in which UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all shared control channels as well as UE-specific control channels, and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured once an RRC connection is established between UE 104 and the anchor carrier, and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals; for example, UE-specific signaling information and signals may not be present on the secondary carrier, since both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Since a “serving cell” (whether PCell or SCell) corresponds to the carrier frequency / component carrier that a base station is using for communication, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc., can be used interchangeably.

[0057] For example, still refer to Figure 1 One of the frequencies utilized by the macrocell base station 102 can be an anchor carrier (or "PCell"), and other frequencies utilized by the macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20MHz aggregated carriers in a multi-carrier system would theoretically result in twice the data rate (i.e., 40MHz) compared to the data rate obtained from a single 20MHz carrier.

[0058] The wireless communication system 100 may further include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In the example, UE 190 has a D2D P2P link 192 with a UE 104 connected to a base station 102 (e.g., UE 190 can indirectly obtain cellular connectivity from this link), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity from this link). In one example, D2D P2P links 192 and 194 can use any known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D)). (etc.) to support.

[0059] The wireless communication system 100 may further include a UE 164, which can communicate with a macrocell base station 102 on a communication link 120 and / or with an mmW base station 180 on an mmW communication link 184. For example, the macrocell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0060] Figure 2A An example wireless network architecture 200 is explained according to various aspects. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally considered as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which operate collaboratively to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, specifically to the control plane functions 214 and user plane functions 212. In an additional configuration, the ng-eNB 224 can also connect to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNB 222s, while other configurations include both one or more ng-eNB 224s and one or more gNB 222s. The gNB 222 or ng-eNB 224 can be used with UE 204 (e.g., Figure 1The UE 204 can communicate with any UE depicted herein. Another optional aspect may include a location server 230, which can communicate with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extending across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, which can connect to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not described). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be external to the core network.

[0061] Figure 2B Another example wireless network architecture 250, based on various aspects, is explained. For example, 5GC 260 can be functionally considered as a control plane function (provided by Access and Mobility Management Function (AMF) 264) and a user plane function (provided by User Plane Function (UPF) 262), which operate cooperatively to form the core network (i.e., 5GC 260). User plane interface 263 and control plane interface 265 connect ng-eNB 224 to 5GC 260, specifically to UPF 262 and AMF 264, respectively. In an additional configuration, gNB 222 can also connect to 5GC 260 via control plane interface 265 to AMF 264 and user plane interface 263 to UPF 262. Furthermore, ng-eNB 224 can communicate directly with gNB 222 via backhaul connection 223, with or without gNB direct connectivity to 5GC 260. In some configurations, the new RAN 220 may have only one or more gNB 222s, while other configurations include both one or more ng-eNB 224s and one or more gNB 222s. The gNB 222 or ng-eNB 224 can be used with UE 204 (e.g., Figure 1 The base station of the new RAN 220 communicates with the AMF 264 via the N2 interface and with the UPF 262 via the N3 interface.

[0062] The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transmission of Session Management (SM) messages between UE 204 and Session Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of Short Message Service (SMS) messages between UE 204 and Short Message Service Function (SMSF) (not shown), and Security Anchor Functionality (SEAF). AMF 264 also interacts with Authentication Server Function (AUSF) (not shown) and UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), AMF 264 retrieves security material from the AUSSF. The functions of AMF 264 also include Security Context Management (SCM). The SCM receives a key from the SEAF, which is used by the SCM to derive a key that varies depending on the access network. The functionality of AMF 264 also includes: location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between the new RAN 220 and LMF 270, allocation of EPS bearer identifiers for interoperability with Evolved Packet Systems (EPS), and UE 204 mobility event notification. Furthermore, AMF 264 also supports functionality for non-3GPP access networks.

[0063] The functions of UPF 262 include: acting as an anchor point for intra / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., strobing, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS Flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. UPF 262 may also support the transmission of location service messages on the user plane between UE 204 and a location server (such as Secure User Plane Positioning (SUPL) Location Platform (SLP) 272).

[0064] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic bootstrapping configuration at UPF 262 for routing traffic to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface used by SMF 266 to communicate with AMF 264 is called the N11 interface.

[0065] Another optional aspect may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extending across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not explained). SLP 272 supports similar functionality to LMF 270, but while LMF 270 can communicate with AMF 264, the new RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols designed to convey signaling messages rather than voice or data), SLP 272 can communicate with UE 204 and external clients on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP). Figure 2B (Not shown in the image) communicates.

[0066] On one hand, the LMF 270 and / or SLP 272 can be integrated into base stations (such as gNB 222 and / or ng-eNB 224). When integrated into gNB 222 and / or ng-eNB 224, the LMF 270 and / or SLP 272 can be referred to as a Location Management Component (LMC). However, as used herein, references to LMF 270 and SLP 272 include both cases where LMF 270 and SLP 272 are components of the core network (e.g., 5GC 260) and cases where LMF 270 and SLP 272 are components of the base station.

[0067] Figure 3A , 3BThe document describes several exemplary components (represented by corresponding boxes) that can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270) to support file transfer operations as taught herein. It will be appreciated that these components can be implemented in different types of devices (e.g., in ASICs, in system-on-chips (SoCs), etc.) in different implementations. The described components can also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Furthermore, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0068] UE 302 and base station 304 each include a wireless wide area network (WWAN) transceiver 310 and 350 configured to communicate via one or more wireless communication networks (not shown) (such as NR networks, LTE networks, GSM networks, etc.). WWAN transceivers 310 and 350 may be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB)) over a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum) via at least one designated RAT (e.g., NR, LTE, GSM, etc.). WWAN transceivers 310 and 350 may be configured, in various ways, to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the designated RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, transceivers 310 and 350 each include one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and each includes one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0069] In at least some cases, UE 302 and base station 304 also include wireless local area network (WLAN) transceivers 320 and 360, respectively. WLAN transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, for use via at least one designated RAT (e.g., WiFi, LTE-D, etc.). The WLAN transceivers 320 and 360 can be configured, according to a specified RAT, in various ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, transceivers 320 and 360 each include one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively.

[0070] A transceiver circuit system including at least one transmitter and at least one receiver may, in some implementations, include integrated devices (e.g., transmitter and receiver circuitry implemented as a single communication device), in some implementations, include separate transmitter and receiver devices, or in other implementations, may be implemented in a different manner. In one aspect, the transmitter may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device to perform transmit "beamforming," as described herein. Similarly, the receiver may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device to perform receive beamforming, as described herein. In another aspect, the transmitter and receiver may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) such that the corresponding device can only receive or transmit at a given time, rather than both simultaneously. The wireless communication equipment of UE 302 and / or base station 304 (e.g., one or both of transceivers 310 and 320 and / or one or both of transceivers 350 and 360) may also include a network eavesdropping module (NLM) for performing various measurements, etc.

[0071] In at least some cases, UE 302 and base station 304 also include Satellite Positioning System (SPS) receivers 330 and 370. SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, to receive SPS signals 338 and 378 (such as Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc.). SPS receivers 330 and 370 may each include any suitable hardware and / or software for receiving and processing SPS signals 338 and 378. SPS receivers 330 and 370 request information and operations from other systems as appropriate and perform necessary calculations to determine the positioning of UE 302 and base station 304 using measurements obtained by any suitable SPS algorithm.

[0072] Base station 304 and network entity 306 each include at least one network interface for communicating with other network entities. For example, the network interface (e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wired or wireless backhaul connection. In some aspects, the network interface may be implemented as a transceiver configured to support wired or wireless signal communication. This communication may involve, for example, sending and receiving messages, parameters, and / or other types of information.

[0073] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with operations disclosed herein. UE 302 includes a processor circuitry that implements a processing system 332 for providing, for example, functionality related to wireless positioning, and for providing other processing functionality. Base station 304 includes a processing system 384 for providing, for example, functionality related to wireless positioning as disclosed herein, and for providing other processing functionality. Network entity 306 includes a processing system 394 for providing, for example, functionality related to wireless positioning as disclosed herein, and for providing other processing functionality. In one aspect, processing systems 332, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), or other programmable logic devices or processing circuitry.

[0074] UE 302, base station 304, and network entity 306 include memory circuitry that implements memory components 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398 may be hardware circuitry that is part of or coupled to processing systems 332, 384, and 394, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, positioning components 342, 388, and 398 may be external to processing systems 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, positioning components 342, 388, and 398 may be memory modules stored in memory components 340, 386, and 396, respectively, which, when executed by processing systems 332, 384, and 394 (or modem processing systems, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A The possible locations of the positioning component 342 are described. The positioning component 342 may be part of the WWAN transceiver 310, the memory component 340, the processing system 332, or any combination thereof, or it may be a self-contained component. Figure 3B The possible locations of the positioning component 388 are described. The positioning component 388 may be part of a WWAN transceiver 350, a memory component 386, a processing system 384, or any combination thereof, or it may be a self-contained component. Figure 3C The possible locations of the positioning component 398 are described. The positioning component 398 may be part of (a) network interface 390, memory component 396, processing system 394, or any combination thereof, or may be a self-contained component.

[0075] UE 302 may include one or more sensors 344 coupled to processing system 332 to provide motion and / or orientation information independent of motion data derived from signals received by WWAN transceiver 310, WLAN transceiver 320, and / or SPS receiver 330. As an example, sensors 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensors 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensors 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in 2D and / or 3D coordinate systems.

[0076] In addition, UE 302 includes a user interface 346 for providing instructions to the user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device (such as a keypad, touchscreen, microphone, etc.)). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0077] Referring more specifically to processing system 384, in the downlink, IP packets from network entity 306 can be provided to processing system 384. Processing system 384 can implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The processing system 384 can provide RRC layer functionality associated with system information (e.g., Master Information Block (MIB), System Information Block (SIB)) broadcasting, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (cryptography, cryptographic decoding, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer packet data unit (PDU) delivery, error correction via Automatic Repeat Request (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, scheduling information reporting, error correction, priority handling, and logical channel priority ordering.

[0078] Transmitter 354 and receiver 352 implement Layer-1 functionality associated with various signal processing functions. Layer-1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from reference signals transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. Transmitter 354 can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0079] At UE 302, receiver 312 receives signals via its respective antenna(s) 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to processing system 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on this information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. Symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base station 304. These soft decisions can be based on a channel estimate calculated by a channel estimator. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by base station 304 over the physical channel. These data and control signals are then provided to processing system 332, which implements layer 3 and layer 2 functionality.

[0080] In the uplink, processing system 332 provides demultiplexing, packet reassembly, cipher decoding, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the core network. Processing system 332 is also responsible for error detection.

[0081] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, processing system 332 provides RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (cryptography, cryptographic decoding, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via 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 MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel priority ordering.

[0082] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0083] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its respective antenna(s) 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to processing system 384.

[0084] In the uplink, processing system 384 provides demultiplexing, packet reassembly, cipher decoding, header decompression, and control signal processing between the transport and logical channels to recover IP packets from UE 302. IP packets from processing system 384 can then be provided to the core network. Processing system 384 is also responsible for error detection.

[0085] For convenience, UE 302, base station 304 and / or network entity 306 are in Figures 3A-3C The box is shown as including various components that can be configured according to the various examples described herein. However, it will be understood that the illustrated box may have different functionalities in different designs.

[0086] Various components of UE 302, base station 304 and network entity 306 can communicate with each other on data buses 334, 382 and 392 respectively. Figures 3A-3C The components can be implemented in various ways. In some implementations, Figures 3A-3CThe components can be implemented in one or more circuits (for example, such as one or more processors and / or one or more ASICs (which may include one or more processors)). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by that circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by the processor and / or memory components of UE 302 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). Furthermore, some or all of the functionality represented by blocks 390 to 398 may be implemented by the processor and / or memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the positioning entity," etc. However, as will be appreciated, such operations, actions, and / or functions may actually be performed by specific components or combinations of components of the UE, base station, positioning entity, etc., such as processing systems 332, 384, 394, transceivers 310, 320, 350, and 360, memory components 340, 386, and 396, positioning components 342, 388, and 398, etc.

[0087] NR supports several cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. In OTDOA or DL-TDOA positioning procedures, the UE measures the difference between the times of arrival (ToA) of reference signals (e.g., PRS, TRS, NRS, CSI-RS, SSB, etc.) received from paired base stations (referred to as Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurements) and reports these differences to the positioning entity. More specifically, the UE receives identifiers of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the base stations involved and the RSTD measurements, the positioning entity can estimate the UE's location. For DL-AoD positioning, UE measurements are used to estimate the location of the UE by taking the angle of the downlink transmit beam used to communicate with the UE and other channel properties (e.g., signal strength).

[0088] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but it is based on uplink reference signals (e.g., SRS) transmitted by the UE. For UL-AoA positioning, the base station measures the angle of the uplink received beam used to communicate with the UE and other channel properties (e.g., gain level) to estimate the UE's location.

[0089] Downlink and uplink-based positioning methods include Enhanced Cellular ID (E-CID) positioning and Multiple Round Trip (RTT) positioning (also known as "Multi-Cell RTT"). In an RTT procedure, the initiator (base station or UE) transmits an RTT measurement signal (e.g., PRS or SRS) to the responder (UE or base station), which then transmits an RTT response signal (e.g., SRS or PRS) back to the initiator. The RTT response signal includes the difference between the ToA of the RTT measurement signal and the transmission time of the RTT response signal (referred to as the receive-to-transmit (Rx-Tx) measurement). The initiator calculates the difference between the transmission time of the RTT measurement signal and the ToA of the RTT response signal (referred to as the "Tx-Rx" measurement). The propagation time between the initiator and the responder (also known as "time of flight") can be calculated from the Tx-Rx and Rx-Tx measurements. Based on the propagation time and the known speed of light, the distance between the initiator and the responder can be determined. For multi-RTT positioning, the UE executes RTT procedures with multiple base stations to triangulate the UE's location based on the known locations of each base station. RTT and multi-RTT methods can be combined with other positioning technologies, such as UL-AoA and DL-AoD, to improve location accuracy.

[0090] The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timings, and signal strengths of detected neighboring base stations. The UE's location is then estimated based on this information and the known locations of the base stations.

[0091] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide auxiliary data to the UE. For example, auxiliary data may include: the identifier of the base station (or the cell / TRP of the base station) from which the measured reference signal originates, reference signal configuration parameters (e.g., the number of consecutive positioning slots, the periodicity of the positioning slots, the silence sequence, the frequency hopping sequence, the reference signal identifier (ID), the reference signal bandwidth, the slot offset, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, auxiliary data may originate directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes without using auxiliary data.

[0092] Location estimation can be referred to by other names, such as location estimation, location, positioning, location locking, locking, etc. Location estimation can be geodetic and include coordinates (e.g., latitude, longitude, and possible elevation), or it can be municipal and include street addresses, postal addresses, or some other verbal description of location. Location estimation can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible elevation). Location estimation can include expected errors or uncertainties (e.g., by including the area or volume that the location is expected to be included with a specified or default confidence level).

[0093] Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs).

[0094] Figure 4A Figure 400 illustrates an example of a downlink frame structure according to various aspects of this disclosure.

[0095] Figure 4B Figure 430 illustrates an example of a channel within a downlink frame structure according to various aspects of this disclosure. Other wireless communication technologies may have different frame structures and / or different channels.

[0096] LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as frequency modulation, frequency slots, etc. Each subcarrier can be modulated with data. Generally, modulation symbols are transmitted in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal FFT size can be equal to 128, 256, 504, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.8MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0097] LTE supports a single set of parameters (subcarrier spacing, symbol length, etc.). In contrast, NR can support multiple sets of parameters (μ), for example, subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz or greater may be available. Table 1 provided below lists some of the various parameters used for different NR parameter sets.

[0098]

[0099] Table 1

[0100] exist Figure 4A and Figure 4B In the example, a parameter set of 15kHz is used. Therefore, in the time domain, a 10-millisecond (ms) frame is divided into 10 equal-sized subframes, each 1ms, and each subframe includes one time slot. Figure 4A and 4B In this context, time is represented horizontally (e.g., on the X-axis), where time increases from left to right, while frequency is represented vertically (e.g., on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0101] A resource grid is used to represent time slots, each time slot comprising one or more concurrent resource blocks (RBs) in the frequency domain (also known as physical RBs (PRBs)). The resource grid is further divided into multiple resource elements (REs). An RE corresponds to one symbol length in the time domain and one subcarrier in the frequency domain. In NR, a subframe is 1 ms in duration, a time slot is 14 symbols in the time domain, and an RB contains 12 consecutive subcarriers in the frequency domain and 14 consecutive symbols in the time domain. Therefore, in NR, there is one RB per time slot. Depending on the SCS, an NR subframe can have 14 symbols, 28 symbols, or more symbols, and therefore can have one, two, or more time slots. The number of bits carried by each RE depends on the modulation scheme.

[0102] Some REs carry downlink reference (pilot) signals (DL-RS). DL-RS may include PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, etc. Figure 4A An exemplary location (labeled "R") of the RE carrying the PRS is explained.

[0103] A “PRS instance” or “PRS timing” is an instance of a periodically repeating time window in which a PRS is expected to be transmitted (e.g., a group of one or more consecutive time slots). A PRS timing may also be referred to as a “PRS positioning timing,” “PRS positioning instance,” “positioning timing,” “positioning instance,” “positioning repetition,” or simply “timing,” “instance,” or “repetition.”

[0104] The set of resource elements (REs) used for PRS transmission is called a "PRS resource". This set of resource elements can span multiple PRBs in the frequency domain and can span "N" (e.g., one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol in the time domain, the PRS resource occupies a consecutive PRB in the frequency domain.

[0105] The transmission of PRS resources within a given PRB has a specific comb size (also known as "comb density"). The comb size 'N' represents the subcarrier spacing (or frequency / frequency modulation spacing) within each symbol of the PRS resource configuration. Specifically, for a comb size 'N', the PRS is transmitted in every Nth subcarrier of a symbol in the PRB. For example, for comb-4, for each of the 4th symbols of the PRS resource configuration, the RE corresponding to each 4th subcarrier (e.g., subcarriers 0, 4, 8) is used to transmit the PRS resource. Currently, comb sizes 2, 4, 6, and 12 are supported for DL ​​PRS. Figure 4AAn exemplary PRS resource configuration for comb tooth 6 (which spans six symbols) is explained. That is, the location of the shaded RE (marked as "R") indicates the PRS resource configuration for comb tooth 6.

[0106] A “PRS resource set” is a group of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by the TRP ID). Additionally, PRS resources in a PRS resource set share the same periodicity, a shared silent mode configuration, and the same cross-slot repetition factor (e.g., PRS-ResourceRepetitionFactor). Periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. Periodicity can have a length selected from the following: 2 μ • {4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5040,10240} time slots, where μ = 0,1,2,3. The repetition factor can have a length selected from {1,2,4,6,8,16,32} time slots.

[0107] In a PRS resource set, a PRS resource ID is associated with a single beam (and / or beam ID) transmitted from a single TRP (where a TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can be transmitted on a different beam, and thus, a "PRS resource" (or simply "resource") can also be referred to as a "beam". Note that this does not imply whether the UE is aware of the TRP and beam transmitting the PRS.

[0108] A “positioning frequency layer” (also simply “frequency layer”) is a collection of one or more PRS resource sets with identical values ​​for certain parameters across one or more TRPs. Specifically, the collection of PRS resource sets has the same subcarrier spacing (SCS) and cyclic prefix (CP) type (meaning all parameter sets supported by PDSCH are also supported by PRS), the same point A, the same downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter uses the value of the parameter ARFCN-ValueNR (where “ARFCN” stands for “Absolute Radio Channel Number”) and is an identifier / code specifying the physical radio channel pair used for transmission and reception. The downlink PRS bandwidth can have a granularity of 4 PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per frequency layer per TRP.

[0109] The concept of a frequency layer is somewhat similar to that of component carriers and bandwidth portions (BWPs), but the difference is that component carriers and BWPs are used by a single base station (or macrocell base station and small cell base station) to transmit data channels, while a frequency layer is used by several (often three or more) base stations to transmit PRS (Positioning Signals). A UE can indicate the number of frequency layers it can support when sending its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, a UE can indicate whether it can support one or four positioning frequency layers.

[0110] Figure 4B Examples of various channels within the downlink time slot of a radio frame are explained. In NR, the channel bandwidth, or system bandwidth, is divided into multiple BWPs. A BWP is a set of adjacent PRBs selected from a subset of shared RBs for a given set of parameters for a given carrier. Generally, a maximum of four BWPs can be specified in both the downlink and uplink. That is, a UE can be configured to have up to four BWPs in the downlink and up to four BWPs in the uplink. Only one BWP (uplink or downlink) can be active at a given time, meaning that the UE can only receive or transmit on one BWP at a time. In the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain an SSB.

[0111] Reference Figure 4BThe Primary Synchronization Signal (PSS) is used by the UE to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (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 physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The Physical Broadcast Channel (PBCH) carrying the MIB can be logically grouped with the PSS and SSS to form the SSB (also known as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) not transmitted through the PBCH, and paging messages.

[0112] The Physical Downlink Control Channel (PDCCH) carries downlink control information (DCI) within one or more Control Channel Elements (CCEs). Each CCE includes one or more RE Group (REG) bundles (which can span multiple symbols in the time domain). Each REG bundle includes one or more REGs, and each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The physical resource set used to carry the PDCCH / DCI is called the Control Resource Set (CORESET) in NR. In NR, the PDCCH is confined to a single CORESET and transmitted along with its own DMRS. This enables UE-specific beamforming for the PDCCH.

[0113] exist Figure 4B In the example, each BWP has one CORESET, and this CORESET spans three symbols in the time domain (although it can be only one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region in the frequency domain (i.e., the CORESET). Therefore, Figure 4B The frequency components of the PDCCH shown are interpreted in the frequency domain as fewer than a single BWP. Note that although the interpreted CORESETs are contiguous in the frequency domain, they do not need to be contiguous. Additionally, a CORESET can span fewer than three symbols in the time domain.

[0114] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and a description of the downlink data transmitted to the UE. Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, different DCI formats exist for uplink scheduling, non-MIMO downlink scheduling, MIMO downlink scheduling, and uplink power control. The PDCCH can be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or coding rates.

[0115] Figure 5 This is a diagram illustrating an exemplary PRS configuration 500 for PRS transmission at a given base station according to various aspects of this disclosure. Figure 5 In the middle, time is represented horizontally, increasing from left to right. Each long rectangle represents a time slot, while each short (shaded) rectangle represents an OFDM symbol. PRS configuration 500 defines resource set 502 by identifying PRS resources 504 and 506 for base station transmission of PRS. PRS resource set 504 has a timing length N for two (2) time slots. PRS and periodic T PRS (For example, 160 subframes or 160ms). Thus, PRS resources 504 and 506 are two consecutive time slots in length, and every T starts from the time slot where the first symbol of the corresponding PRS resource appears. PRS Repeated subframes.

[0116] exist Figure 5 In the example, PRS resource set 502 includes two PRS resources—the first PRS resource 504 ( Figure 5 The middle one is marked as "PRS Resource 1") and the second PRS Resource 506 ( Figure 5 (marked as "PRS Resource 2"). PRS Resource 504 and PRS Resource 506 can be transmitted on separate beams of the same base station. PRS Resource 504 has a symbol length N of two (2) symbols. symb Furthermore, PRS resource 506 has a symbol length N of four (4) symbols. symb .

[0117] Each instance of PRS resource set 502 (described as instances 508a, 508b, and 508c) includes a length of '2' (i.e., N) for each PRS resource 504, 506 in that PRS resource set. PRS =2) timing. PRS resources 504 and 506 per T PRS The subframes repeat until the silent sequence periodically T. REP Therefore, a length of T will be required. REPThe bitmap is used to indicate when instances 508a, 508b, and 508c are silenced.

[0118] On the one hand, there may be configurations for PRS (such as...) Figure 5 Additional constraints for PRS configuration 500 as explained in the text. For example, for all PRS resources (e.g., PRS resources 504, 506) in a PRS resource set (e.g., PRS resource set 502), the base station can configure the following parameters to be the same: (a) timing length (e.g., T PRS (b) Number of symbols (e.g., N) symb (c) Comb type, and / or (d) Bandwidth. Additionally, for all PRS resources in all PRS resource sets, the subcarrier spacing and cyclic prefix can be configured the same for one base station or for all base stations. Whether it's for one base station or all base stations depends on the UE's ability to support the first and / or second options. There is a type of measurement gap in NR, meaning that the same type of measurement gap will be used for both Radio Resource Management (RRM) measurements (i.e., measurements required for RRM reporting) and PRS measurements. A measurement gap is a configured time period during which the serving cell suppresses transmissions to the UE so that the UE can receive transmissions (e.g., downlink reference signals) from other cells. Transmissions from other cells may or may not be on the same frequency as the serving cell. In addition to downlink reception, measurement gaps can also be used for uplink transmissions, including uplink reference signals such as SRS. This depends on the UE implementation to prioritize PRS measurements over RRM measurements, as RRM measurements will have higher priority by default, and the UE may not be able to perform both simultaneously.

[0119] Figure 6Figure 600 illustrates how parameters in the measurement gap configuration according to various aspects of this disclosure specify the mode of the measurement gap. The Measurement Gap Repetition Period (MGRP) defines the periodicity (in milliseconds) of the measurement gap repetition. It can have values ​​of 20, 40, 80, or 160 ms, but values ​​of 320 and 640 ms are also considered. The Measurement Gap Length (MGL) is the measurement gap length in milliseconds. This measurement gap length can have values ​​of 1.5, 3, 3.5, 4, 5.5, or 6 ms, but values ​​of 10, 18, 20, 34, 40, and 50 ms are also considered. The Measurement Gap Offset (MGO) is the offset between the start of the gap mode and the start of a time slot or subframe within the Measurement Gap Repetition Period (MGRP). Currently, approximately 160 offset values ​​exist, but not all of these values ​​are applicable to all periodicities. More specifically, the offset value ranges from "0" to 1 less than the MGRP. Therefore, for example, if MGRP is 20ms, then the offset can range from "0" to "19". Although Figure 6 Not shown, but the measurement gap configuration may also include a Measurement Gap Timing Advance (MGTA) parameter. If configured, the MGTA indicates the amount of time the measurement gap is configured to precede the occurrence of the time slot or subframe in which it begins. Currently, the MGTA can be 0.25 ms for FR2 or 0.5 ms for FR1. The measurement gap is configured using the RRC protocol.

[0120] For positioning purposes, a UE or other entity (referred to herein as the target device) may determine that it needs PRS resources for measurement and may issue a request to configure such PRS resources. This is referred to herein as "on-demand PRS". On-demand PRS resources that a UE may request include, but are not limited to, subsets of TRPs, specific directions or beams, periodicity, and PRS configuration. Positioning procedures in Next-Generation (NG) RAN can be modeled as transactions of the LPP protocol, which include a single operation of one of the following types: positioning capability exchange, delivery of auxiliary data (AD), delivery of location information (e.g., positioning measurements and / or estimated positioning), error handling, or abort. An example of an on-demand PRS request is... Figure 7 As shown in the image.

[0121] Figure 7 This is a signaling message passing diagram, which shows how UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270) can communicate so that UE 302 obtains PRS configuration from network entity 306 and measurement gap (MG) configuration from base station 304.

[0122] exist Figure 7 In the explained process 700, at 702, network entity 306 sends a request to UE 302 requesting UE 302 to provide its capability list to network entity 306. In response, at 704, UE 302 provides the requested capability list to network entity 306. At 706, UE 302 sends a request to network entity 306 for ancillary data, which in this example includes an on-demand PRS request. At 708, network entity 306 provides UE 302 with PRS scheduling information (e.g., information defining PRS timing).

[0123] At 710, network entity 306 sends a request for location information to UE 302. Figure 7 In the illustrated example, at 712, UE 302 sends a request for measurement gap configuration information to serving base station 304, which may be based on the PRS scheduling information received by UE 302 at 708. At 714, base station 304 responds to UE 302 with one or more MG configurations, each MG configuration may include parameters such as MG00, MG10, MG20, MG20, etc. At 716, UE 302 performs PRS measurements, but only within the MGs configured by base station 304. At 718, UE 302 provides the requested location information to network entity 306.

[0124] Figure 7 The explanation explains the points where network entity 306 and base station 304 may not communicate with each other in some respects (although communication is possible): accordingly, in some respects, network entity 306 may not know the MG configuration provided to UE 302 by base station 304, and base station 304 may not know the PRS configuration provided to UE 302 by network entity 306. Figure 7 The conventional method shown has at least two problems or weaknesses. These problems are... Figure 8 Chinese explanation.

[0125] Figure 8 It explained some issues with conventional networks. Figure 8 In the example, time is represented horizontally, and the boxes labeled "PRS" indicate the temporal location of the corresponding resources that can be used for PRS measurements. For example, for a PRS, these resources could be REs carrying the PRS, PRS resources, PRS resource sets, PRS timings, etc. Figure 8 In the example, network entity 306 has provided UE 302 with configuration 800, which has four PRS instances: PRS 802, PRS 804, PRS 806, and PRS 808. Base station 304 has provided UE 302 with MG configuration 810, which has values ​​for MG0, MGRP, and MGL, resulting in measurement gaps 812 and 814. The additional repetition of measurement gap 812 (not in...) Figure 8 (As shown in the image) It can also exist as part of the MG configuration 810.

[0126] Figure 8 One issue explained is that network entity 306 might configure PRS timings that UE 302 cannot use because all or part of those PRS timings fall outside the measurement gaps defined by base station 304. This situation may occur due to a lack of coordination between base station 304 and network entity 306, or it may occur because base station 304 is unable to provide sufficient measurement gaps for UE 302 due to other limitations, such as the existence of many UEs currently supported by base station 304 and measurement gaps having to be allocated among them. Figure 8 In the example shown, UE 302 cannot use PRS 804 because PRS 804 is not within the first instance of measurement gap 812. UE 302 cannot use PRS 808 because PRS 808 is not fully within the second instance of measurement gap 812. In a typical network, UE 302 lacks a mechanism to notify network entity 306 that UE 302 cannot use those PRS instances.

[0127] Figure 8 Another issue explained is that network entity 306 may configure a large number of TRPs for PRS instances. This is likely because network entity 306 is unaware of UE 302's current location, and by providing more PRS opportunities in the auxiliary data sent to UE 302, network entity 306 can help ensure that UE 302 obtains a large number of and / or high-quality location estimates. After each PRS opportunity measurement, UE 302 will have a rough estimate of its location based on the reference TRPs. Some TRP signals will be very strong, some will be weak, and some will be too weak for UE 302 to decode.

[0128] exist Figure 8 As shown in the details of PRS 802, network entity 306 has configured each PRS timing with 16 TRPs, labeled 1 to 16, where each TRP repeats four times per PRS timing. In the example details, the shaded squares represent TRPs that UE 302 cannot receive, can only receive weakly, and / or TRPs with relatively low connection priority for UE 302. However, UE 302 must attempt to decode the PRS signal from all 16 TRPs. In a conventional network, UE 302 has no mechanism to notify network entity 306 that certain TRPs have low quality or low priority.

[0129] Figure 9 The methods according to some aspects of this disclosure have been explained. Figure 9 In this process, UE 302 can notify network entity 306 that UE 302 wants to modify certain aspects of the PRS configuration previously received by UE 302 from network entity 306. For example, in Figure 9 In this context, UE 302 can notify network entity 306 that PRS instances PRS 804 and PRS 808 should be completely cancelled because they are outside the MG and therefore cannot be used by UE 302. Similarly, UE 302 can notify network entity 306 that TRPs 2, 5, 6, 12, 15, and 16 have low quality or low priority and should be ignored for all PRS instances. In some respects, UE 302 can include this information in the PRS modification information sent by UE 302 to network entity 306. Figure 9 In this case, TRPs 2, 5, 6, 12, 15, and 16 are not measured in the modified PRS instance 900. Similarly, UE 302 can indicate to network entity 306 that some TRPs do not need to be measured at every PRS instance. For example, in Figure 9 In the modified PRS instance 900, TRPs 4, 10, 11, and 14 were measured, but not in the modified PRS instance 902.

[0130] Accordingly, this disclosure provides techniques that UE 302 can use to modify the PRS configuration provided to it by network entity 306. According to some aspects, UE 302 can send a specific request to network entity 306 to modify the PRS configuration in a specific manner. The request to modify the PRS configuration may include a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, and / or one or more duplicates of the PRS instances, or a request to reduce their overhead. The request to modify the PRS configuration may include a request to cancel or remove PRS resources in one or more frequency layers, one or more transmit / receive points of the frequency layer, one or more frequency layers of the one or more transmit / receive points, and / or PRS resources associated with a specific duplicate of the above. The request to modify the PRS configuration may indicate a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration. The request may be associated with time T or a specific timer.

[0131] Depending on other aspects, UE 302 will send information related to PRS measurements to network entity 306, and network entity 306 may take action based on one or more measured values. Depending on some aspects, UE 302 will send the measured values ​​and additional information from UE 302 to network entity 306 for each configured PRS event. This additional information, which UE 302 may send along with the results of the PRS measurements, is referred to herein as "PRS modification information" and may include a specific request to modify the PRS configuration, information that network entity 306 can use to determine modifications to the PRS configuration, or a combination of the above.

[0132] Figure 10 This is a signal message passing diagram illustrating a method 1000 for modifying PRS resources according to some aspects of this disclosure. Figure 10 In this context, UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270) may communicate such that UE 302 requests the cancellation of PRS resources previously provided to UE 302 in response to an on-demand PRS request.

[0133] exist Figure 10 In the simplified process described, at 1002, UE 302 receives PRS configuration from network entity 306. At 1004, UE 302 receives measurement gap (MG) configuration from base station 304. Note that 1002 and 1004 can appear in any order.

[0134] In some respects, in 1006, UE 302 performs PRS measurements. In these respects, in 1008, UE 302 can determine, based on PRS measurements, the desired modification of the PRS configuration, such as when UE 302 determines that some PRS resources are of low quality or have low values. (Reference) Figure 9 For example, UE 302 may determine that signals from some TRPs and / or in some frequency layers are too weak or too noisy to be successfully decoded. In these respects, UE 302 may wish to cancel those TRPs or frequency layers, i.e., remove them from the PRS configuration. In some respects, UE 302 may send the PRS measurement results along with PRS modification information after each PRS measurement. In some respects, as UE 302 becomes more confident in its current location, UE 302 may not need as many PRS resources as initially provided in the PRS configuration from network entity 306. Therefore, the PRS resources used by UE 302 can be dynamically adjusted by UE 302, for example.

[0135] In other respects, the PRS measurement step at 1006 can be omitted. For example, at 1008, UE 302 can determine the desired modification of the PRS configuration based solely on the received PRS configuration and MG configuration, such as when UE 302 can determine that some PRS instances defined by the PRS configuration are not in the MG defined by the MG configuration. In these respects, UE 302 may want to cancel those PRS instances, i.e., remove them from the PRS configuration. (Similarly, UE 302 can also make such a determination after performing the PRS measurement step at 1006, i.e., in respects where 1006 is not omitted.)

[0136] exist Figure 10 In this context, once UE 302 determines that certain PRS resources should be modified, in some aspects, at 1010, UE 302 can use the LPP protocol to directly send PRS modification information to network entity 306. Alternatively, at 1010, UE 302 can send PRS modification information to base station 304 via RRC and Media Access Control (MAC) control element (MAC-CE). In these aspects, base station 304 can send PRS modification information to network entity 306 via New Radio Positioning Protocol Type A (NRPPa) signaling at 1012 and 1014.

[0137] Depending on the context, modifications to the PRS configuration that UE 302 may request can include canceling, removing one or more PRS resource sets, one or more PRS resources within those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of a PRS instance, or reducing its overhead. See again Figure 9 For example, PRS modification information can request the cancellation of specific PRS, such as PRS 804 and PRS 808, and can request the cancellation of specific RPS that is not within the measurement gap.

[0138] Within a specific PRS instance, modifications to the PRS configuration that UE 302 can request may include canceling or removing PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above. See again Figure 9For example, a PRS modification message may request the removal of TRPs 2, 5, 6, 12, 15, and 16 from the first PRS instance 900, and the removal of additional TRPs 4, 10, 11, and 14 from PRS instance 902 and subsequent instances. In some aspects, the PRS modification message may result in the cancellation of previously configured PRS instances and / or duplicate PRS resources within PRS instances. In some aspects, the PRS modification message may identify TRPs with low signal strength or low usefulness to a particular UE 302, in which case network entity 306 may decide to modify the PRS configuration to remove those identified TRPs. The PRS modification message may indicate a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration. The request may be associated with time T or a specific timer.

[0139] Reference Figure 10 At 1016, upon receiving PRS modification information, network entity 306 may modify the PRS configuration for UE 302 or other UEs, and at 1018, network entity 306 may send the updated PRS configuration to UE 302. Depending on some aspects, the actions that network entity 306 may take include, but are not limited to, the following: Network entity 306 may disable certain PRS elements that UE 302 has reported as unused by UE 302. As used herein, the term "PRS element" may refer to one or more of the following: TRP, PRS resource, PRS resource set, frequency layer, and / or higher duplication. Network entity 306 may redesign or update auxiliary data, including but not limited to deleting some existing PRS elements, adding some PRS elements, and / or changing the order or priority of existing PRS elements. In some aspects, the updated PRS configuration may replace the original PRS configuration until further notification from network entity 306. In other respects, an updated PRS configuration can temporarily override the original PRS configuration for a specified time period T, from a specified start time to a specified end time, for a specified number of PRS events N, until some other triggering event, or a combination of the above. In some respects, modifications to the PRS configuration can be canceled upon detection of a change in the serving cell. PRS modification information can be sent as a periodic report from UE 302, as a one-time / unsolicited report, or as required by UE 302.

[0140] The technology described in this paper has various technical advantages over existing technologies, such as: by providing a mechanism to cancel, remove, or reduce the overhead of PRS elements, UE 302 will have a reduced search space for subsequent PRS timing measurements, which will benefit UE 302 by reducing its power consumption and increasing its battery life, and will benefit the network by improving network efficiency.

[0141] Figure 11 An exemplary wireless communication method 1100 according to various aspects of this disclosure has been described. In one aspect, method 1100 can be performed by a UE (e.g., any UE described herein). Figure 11 In step 1102, the UE receives PRS configuration from a location server (e.g., network entity 306). The PRS configuration defines the PRS instance, TRP, frequency layer, repetition, and other PRS resources, collectively referred to as "PRS elements." In one aspect, 1102 can be performed by a WWAN transceiver 310, a processing system 332, a memory component 340, and / or a positioning component 342, wherein any or all of these components can be considered as means for performing this operation.

[0142] At 1104, the UE receives MG configuration from the serving base station (e.g., base station 304). MG configuration defines the measurement gap and may include values ​​for MG0, MGL, MGRP, etc. This MG configuration can be received via higher-layer signaling (e.g., RRC signaling). In one aspect, 1104 may be performed by WWAN transceiver 310, processing system 332, memory component 340, and / or positioning component 342, wherein any or all of these components can be considered as means for performing this operation.

[0143] Optionally, at 1106, the UE may perform PRS measurements on one or more non-serving base stations during a measurement gap specified by the first measurement gap configuration. In one aspect, 1106 may be performed by WWAN transceiver 310, processing system 332, memory component 340, and / or positioning component 342, wherein any or all of the components may be considered as means for performing the operation.

[0144] At 1108, the UE determines that one or more transmission attributes of one or more resources should be modified; for example, one or more PRS elements or their duplicates should be canceled, removed, or have their overhead reduced. In one aspect, 1108 can be performed by WWAN transceiver 310, processing system 332, memory component 340, and / or positioning component 342, wherein any or all of these components can be considered as means for performing this operation.

[0145] At 1110, the UE sends PRS modification information to the location server. In the execution of 1106, the result of the PRS measurement can also be sent to the location server. In one aspect, the PRS modification information can be sent using LPP. In another aspect, the PRS modification information can be sent to the serving base station using RRC / MAC-CE, and the serving base station forwards the information to the location server via NRPPa. In one aspect, 1108 can be performed by the WWAN transceiver 310, the processing system 332, the memory component 340, and / or the positioning component 342, wherein any or all of these components can be considered as means for performing this operation.

[0146] At 1112, the UE receives the updated PRS configuration from the location server. Alternatively, the process returns to 1106. Alternatively, 1108 can be performed by the WWAN transceiver 310, processing system 332, memory component 340, and / or positioning component 342, wherein any or all of these components can be considered as means for performing the operation.

[0147] Figure 12 An exemplary wireless communication method 1200 according to various aspects of this disclosure has been described. In one aspect, method 1200 may be performed by a location server (e.g., any base station described herein) such as network entity 306. In 1202, the location server transmits PRS configuration to the UE. In another aspect, 1202 may be performed by a network interface 390, a processing system 394, a memory component 396, and / or a positioning component 398, wherein any or all of these components may be considered as means for performing the operation.

[0148] At 1204, the location server receives PRS modification information from the UE, which may or may not include the results of the UE's PRS measurement operation. In one aspect, 1204 may be performed by network interface 390, processing system 394, memory component 396, and / or positioning component 398, wherein any or all of these components can be considered as means for performing the operation.

[0149] At 1206, the location server updates the PRS configuration for the UE based on the received PRS modification information. In one aspect, 1206 can be performed by the network interface 390, the processing system 394, the memory component 396, and / or the positioning component 398, wherein any or all of these components can be considered as means for performing this operation.

[0150] At 1208, the location server transmits the updated PRS configuration for the UE to the UE. On one hand, 1206 can be performed by the network interface 390, the processing system 394, the memory component 396, and / or the positioning component 398, wherein any or all of these components can be considered as means for performing this operation.

[0151] Figure 13 An exemplary wireless communication method 1300 according to various aspects of this disclosure has been described. In one aspect, method 1300 may be performed by a serving base station (e.g., any base station described herein).

[0152] At 1302, the base station receives PRS modification information from the UE. In another aspect, the base station also receives the results of PRS measurements from the UE. In yet another aspect, operation 1302 can be performed by a WWAN transceiver 350, a processing system 384, a memory component 386, and / or a positioning component 388, wherein any or all of these components can be considered as means for performing the operation.

[0153] At 1304, the base station transmits PRS modification information to the network entity associated with the UE. In some aspects, this network entity is a location server or LMF. The base station may also transmit this information to the network entity if it has also received the UE's PRS measurement results. In one aspect, the base station may transmit the information to the network entity via NRPPa. In another aspect, operation 1304 may be performed by WWAN transceiver 350, processing system 384, memory component 386, and / or positioning component 388, wherein any or all of these components can be considered as means for performing the operation.

[0154] Those skilled in the art will appreciate that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0155] Furthermore, those skilled in the art will appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in a generalized manner in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure.

[0156] The various illustrative logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, it may be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0157] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read and write information from / to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). In an alternative, the processor and storage medium may reside as discrete components in the user terminal.

[0158] In one or more exemplary aspects, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or transmitted as one or more instructions or codes on or through a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Similarly, any connection is also legitimately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then such coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of a medium. As used in this article, disks and discs include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0159] In the detailed description above, it can be seen that different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to have more features than those explicitly mentioned in each clause. Rather, aspects of this disclosure may include fewer features than those of the individual example clauses disclosed. Therefore, the appended clauses should thus be considered as incorporated into this description, where each clause may be a separate example. Although each dependent clause may refer in its respective clause to a specific combination with one of the other clauses, the aspects of that dependent clause are not limited to that specific combination. It will be appreciated that other example clauses may also include combinations of aspects of the dependent clause with the subject matter of any other dependent or independent clause, or any feature combined with other dependent and independent clauses. The aspects disclosed herein expressly include these combinations unless explicitly stated or readily inferred that a particular combination is not intended (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is intended that aspects of a clause may be included in any other independent clause, even if that clause is not directly subordinate to that independent clause.

[0160] Examples of implementations are described in the following numbered clauses.

[0161] Clause 1. A wireless communication method performed by a user equipment (UE), the method comprising: receiving a positioning reference signal (PRS) configuration from a network entity; receiving a measurement gap (MG) configuration from a serving base station; determining that one or more transmission attributes of one or more PRS resources should be modified; and transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0162] Clause 2. The method of Clause 1, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

[0163] Clause 3. The method of any of Clauses 1 to 2 further includes: performing a PRS measurement on the one or more PRS resources before determining that one or more transport attributes of the one or more PRS resources should be modified.

[0164] Clause 4. The method of Clause 3, wherein performing the PRS measurement includes performing a PRS measurement on one or more transmit / receive points (TRPs) during the measurement interval specified by the MG configuration.

[0165] Clause 5. The method of any of Clauses 1 to 4, wherein transmitting PRS modification information to the network entity includes transmitting PRS measurement results.

[0166] Clause 6. The method of Clause 5, wherein the transmitted PRS measurement results include the transmitted reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0167] Clause 7. The method of any of Clauses 1 to 6 further includes: receiving an updated PRS configuration from a network entity; and using the updated PRS configuration to perform PRS measurements.

[0168] Clause 8. The method of any of Clauses 1 to 7, wherein transmitting PRS modification information includes transmitting PRS modification information via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0169] Clause 9. The method of any of Clauses 1 to 8, wherein transmitting PRS modification information includes transmitting a request to modify the PRS configuration.

[0170] Clause 10. The method of Clause 9, wherein transmitting a request to modify the PRS configuration includes transmitting a request to cancel or remove a PRS instance that is not in the measurement interval.

[0171] Clause 11. The method of any of Clauses 9 to 10, wherein transmitting a request to modify the PRS configuration includes transmitting a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

[0172] Clause 12. The method of any of Clauses 9 to 11, wherein transmitting a request to modify the PRS configuration includes transmitting a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the foregoing, or a combination thereof.

[0173] Clause 13. The method of any of Clauses 9 to 12, wherein transmitting PRS modification information includes transmitting information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration.

[0174] Clause 14. A wireless communication method performed by a network entity, the method comprising: transmitting a Positioning Reference Signal (PRS) configuration to a user equipment (UE); receiving PRS modification information from the UE; updating the PRS configuration for the UE based on the PRS modification information; and transmitting the updated PRS configuration to the UE.

[0175] Clause 15. The method of Clause 14, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

[0176] Clause 16. The method of any of Clauses 14 to 15, wherein the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0177] Clause 17. The method of any of Clauses 14 to 16, wherein receiving PRS modification information includes receiving a request to modify the PRS configuration.

[0178] Clause 18. The method of Clause 17, wherein receiving PRS modification information includes receiving PRS measurement results.

[0179] Clause 19. The method of Clause 18, wherein the received PRS measurement results include the received reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0180] Clause 20. The method of any of Clauses 17 to 19, wherein receiving a request to modify the PRS configuration includes receiving a request to cancel or remove a PRS instance that is not in the measurement interval.

[0181] Clause 21. The method of any of Clauses 17 to 20, wherein receiving a request to modify the PRS configuration includes receiving a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

[0182] Clause 22. The method of any of Clauses 17 to 21, wherein receiving a request to modify the PRS configuration includes receiving a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the foregoing, or a combination thereof.

[0183] Clause 23. The method of any of Clauses 17 to 22, wherein receiving PRS modification information includes receiving information indicating the start time, stop time, duration, or a combination thereof for modifying the PRS configuration.

[0184] Clause 24. The method of any of Clauses 14 to 23 further includes: receiving a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

[0185] Clause 25. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a Position Reference Signal (PRS) configuration from a network entity; receive a Measurement Gauge (MG) configuration from a serving base station; determine that one or more transmission attributes of one or more PRS resources should be modified; and cause the at least one transceiver to transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0186] Clause 26. As in Clause 25, the network entity includes a location server, a location management function, or a transmission / reception point.

[0187] Clause 27. The UE of any of Clauses 25 to 26, wherein the at least one processor is further configured to perform PRS measurements before determining that one or more transport attributes of one or more resources should be modified.

[0188] Clause 28. The UE as in Clause 27, wherein performing the PRS measurement includes performing PRS measurements of one or more non-serving base stations performed by the UE during the measurement interval specified by the MG configuration.

[0189] Clause 29. For any UE of Clauses 25 to 28, wherein the PRS modification information includes PRS measurement results.

[0190] Clause 30. The UE as in Clause 29, wherein the PRS measurement result includes the Reference Signal Received Power (RSRP) value, the Reference Signal Time Difference (RSTD) value, the Receive to Transmit (Rx-Tx) value, or a combination thereof.

[0191] Clause 31. The UE of any of Clauses 25 to 30, wherein the at least one processor is further configured to: receive an updated PRS configuration from a network entity; and use the updated PRS configuration to perform PRS measurements.

[0192] Clause 32. For any UE of Clauses 25 to 31, wherein the PRS modification information is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0193] Clause 33. For any UE of Clauses 25 to 32, wherein the PRS modification information includes a request to modify the PRS configuration.

[0194] Clause 34. For the UE as described in Clause 33, a request to modify the PRS configuration includes a request to cancel or remove a PRS instance that is not within the measurement interval.

[0195] Clause 35. For any UE of Clauses 33 to 34, a request to modify the PRS configuration includes a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or a request to reduce its overhead.

[0196] Clause 36. For any UE of Clauses 33 to 35, a request to modify the PRS configuration includes a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the above, or a combination thereof.

[0197] Clause 37. For any UE of Clauses 33 to 36, wherein the PRS modification information indicates the start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration.

[0198] Clause 38. A network entity comprising: a memory; at least one network interface; and at least one processor communicatively coupled to the memory and the at least one network interface, the at least one processor being configured to: cause the at least one network interface to transmit a Position Reference Signal (PRS) configuration to a user equipment (UE); receive PRS modification information from the UE; update a PRS configuration for the UE based on the PRS modification information; and cause the at least one network interface to transmit the updated PRS configuration to the UE.

[0199] Clause 39. Network entities as described in Clause 38, including location servers, location management functions, or transmission / reception points.

[0200] Clause 40. A network entity as described in any of Clauses 38 to 39, wherein the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0201] Clause 41. A network entity as described in any of Clauses 38 to 40, wherein the PRS modification information includes a request to modify the PRS configuration.

[0202] Clause 42. As in Clause 41, the network entity where the PRS modification information includes PRS measurement results.

[0203] Clause 43. A network entity as described in Clause 42, wherein the PRS measurement results include the Reference Signal Received Power (RSRP) value, the Reference Signal Time Difference (RSTD) value, the Receive to Transmit (Rx-Tx) value, or a combination thereof.

[0204] Clause 44. A network entity as described in any of Clauses 41 to 43, wherein a request to modify the PRS configuration includes a request to cancel or remove a PRS instance that is not within a measurement interval.

[0205] Clause 45. A network entity as described in any of Clauses 41 to 44, wherein a request to modify the PRS configuration includes a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or a request to reduce its overhead.

[0206] Clause 46. A network entity as described in any of Clauses 41 to 45, wherein a request to modify the PRS configuration includes a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the foregoing, or a combination thereof.

[0207] Clause 47. A network entity as described in any of Clauses 41 to 46, wherein the PRS modification information indicates the start time, stop time, duration, or a combination thereof for modifying the PRS configuration.

[0208] Clause 48. A network entity as described in any of Clauses 38 to 47, wherein the at least one processor is further configured to: receive a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

[0209] Clause 49. A user equipment (UE) comprising: means for receiving a positioning reference signal (PRS) configuration from a network entity; means for receiving a measurement gap (MG) configuration from a serving base station; means for determining that one or more transmission attributes of one or more PRS resources should be modified; and means for transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0210] Clause 50. As in Clause 49, the network entity includes a location server, a location management function, or a transmission / reception point.

[0211] Clause 51. For any UE of Clauses 49 to 50, the UE further includes: performing a PRS measurement on the one or more PRS resources before determining that one or more transport attributes of the one or more PRS resources should be modified.

[0212] Clause 52. The UE as in Clause 51, wherein the means for performing the PRS measurement includes means for performing PRS measurements on one or more transmit / receive points (TRPs) during a measurement gap specified by the MG configuration.

[0213] Clause 53. For any UE of Clauses 49 to 52, the means for transmitting PRS modification information to the network entity includes means for transmitting PRS measurement results.

[0214] Clause 54. The UE as described in Clause 53, wherein the means for transmitting PRS measurement results includes means for transmitting reference signal received power (RSRP) values, reference signal time difference (RSTD) values, receive-to-transmit (Rx-Tx) values, or combinations thereof.

[0215] Clause 55. The UE of any of Clauses 49 to 54 further includes: means for receiving an updated PRS configuration from a network entity; and means for performing PRS measurements using the updated PRS configuration.

[0216] Clause 56. For any UE of Clauses 49 to 55, the means for transmitting PRS modification information includes means for transmitting PRS modification information via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0217] Clause 57. For any UE of Clauses 49 to 56, the means for transmitting PRS modification information includes means for transmitting a request to modify the PRS configuration.

[0218] Clause 58. The UE as described in Clause 57, wherein the means for transmitting a request to modify the PRS configuration includes means for transmitting a request to cancel or remove a PRS instance that is not in the measurement gap.

[0219] Clause 59. For any UE of Clauses 57 to 58, the means for transmitting a request to modify the PRS configuration includes means for transmitting a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

[0220] Clause 60. For any UE of Clauses 57 to 59, the means for transmitting a request to modify the PRS configuration includes means for transmitting a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the above, or a combination thereof.

[0221] Clause 61. For any UE of Clauses 57 to 60, the means for transmitting PRS modification information includes means for transmitting information indicating a start time, stop time, duration, or a combination thereof associated with the modification of the PRS configuration.

[0222] Clause 62. A network entity comprising: means for transmitting a Position Reference Signal (PRS) configuration to a user equipment (UE); means for receiving PRS modification information from the UE; means for updating the PRS configuration for the UE based on the PRS modification information; and means for transmitting the updated PRS configuration to the UE.

[0223] Clause 63. A network entity as described in Clause 62, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

[0224] Clause 64. A network entity as described in any of Clauses 62 to 63, wherein the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0225] Clause 65. A network entity as described in any of Clauses 62 to 64, wherein the means for receiving PRS modification information includes means for receiving a request to modify the PRS configuration.

[0226] Clause 66. A network entity as described in Clause 65, wherein the means for receiving PRS modification information includes means for receiving PRS measurement results.

[0227] Clause 67. A network entity as described in Clause 66, wherein the means for receiving PRS measurement results includes means for receiving a reference signal received power (RSRP) value, a reference signal time difference (RSTD) value, a receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0228] Clause 68. A network entity as described in any of Clauses 65 to 67, wherein the means for receiving a request to modify the PRS configuration includes means for receiving a request to cancel or remove a PRS instance that is not within the measurement interval.

[0229] Clause 69. A network entity as described in any of Clauses 65 to 68, wherein the means for receiving a request to modify a PRS configuration includes means for receiving a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

[0230] Clause 70. A network entity as described in any of Clauses 65 to 69, wherein the means for receiving a request to modify the PRS configuration includes means for receiving a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the foregoing, or a combination thereof.

[0231] Clause 71. A network entity as described in any of Clauses 65 to 70, wherein the means for receiving PRS modification information includes means for receiving information indicating a start time, stop time, duration, or a combination thereof for modifying the PRS configuration.

[0232] Clause 72. A network entity as described in any of Clauses 62 to 71 further includes: means for receiving a report from a UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

[0233] Clause 73. A non-transient computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a Position Reference Signal (PRS) configuration from a network entity; receive a Measurement Gauge (MG) configuration from a serving base station; determine that one or more transmission attributes of one or more PRS resources should be modified; and transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0234] Clause 74. A non-transient computer-readable medium as described in Clause 73, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

[0235] Clause 75. A non-transient computer-readable medium such as any of Clauses 73 to 74, wherein one or more instructions further cause the UE to: perform a PRS measurement on the one or more PRS resources before determining that one or more transport attributes of the one or more PRS resources should be modified.

[0236] Clause 76. A non-transient computer-readable medium as described in Clause 75, wherein computer-executable instructions that, when executed, cause the UE to perform PRS measurements include computer-executable instructions that, when executed, cause the UE to perform PRS measurements on one or more transmit / receive points (TRPs) during a measurement gap specified by the MG configuration.

[0237] Clause 77. A non-transient computer-readable medium such as any of Clauses 73 to 76, wherein the computer-executable instructions that, when executed, cause the UE to transmit PRS modification information to a network entity include computer-executable instructions that, when executed, cause the UE to transmit PRS measurement results.

[0238] Clause 78. A non-transient computer-readable medium as described in Clause 77, wherein computer-executable instructions which, when executed, cause the UE to transmit PRS measurement results include computer-executable instructions which, when executed, cause the UE to transmit a reference signal received power (RSRP) value, a reference signal time difference (RSTD) value, a receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0239] Clause 79. A non-transient computer-readable medium such as any of Clauses 73 to 78, wherein one or more instructions further cause the UE to: receive an updated PRS configuration from a network entity; and use the updated PRS configuration to perform PRS measurements.

[0240] Clause 80. A non-transient computer-readable medium such as any of Clauses 73 to 79, wherein a computer-executable instruction that, when executed, causes the UE to transmit PRS modification information includes a computer-executable instruction that, when executed, causes the UE to transmit PRS modification information via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0241] Clause 81. A non-transient computer-readable medium such as any of Clauses 73 to 80, wherein the computer-executable instructions that cause the UE to transmit PRS modification information when executed include computer-executable instructions that cause the UE to transmit a request to modify the PRS configuration when executed.

[0242] Clause 82. A non-transient computer-readable medium as described in Clause 81, wherein a computer-executable instruction that, when executed, causes the UE to transmit a request to modify the PRS configuration includes a computer-executable instruction that, when executed, causes the UE to transmit a request to cancel or remove a PRS instance that is not within the measurement gap.

[0243] Clause 83. A non-transient computer-readable medium such as those in Clauses 81 to 82, wherein a computer-executable instruction that, when executed, causes the UE to transmit a request to modify the PRS configuration includes, when executed, a computer-executable instruction that, when executed, causes the UE to transmit a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

[0244] Clause 84. A non-transient computer-readable medium such as any of Clauses 81 to 83, wherein a computer-executable instruction that, when executed, causes the UE to transmit a request to modify the PRS configuration includes, when executed, a computer-executable instruction that, when executed, causes the UE to transmit a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the foregoing, or a combination thereof.

[0245] Clause 85. A non-transient computer-readable medium such as any of Clauses 81 to 84, wherein computer-executable instructions that, when executed, cause the UE to transmit PRS modification information include computer-executable instructions that, when executed, cause the UE to transmit information indicating a start time, stop time, duration, or a combination thereof associated with the modification of the PRS configuration.

[0246] Clause 86. A non-transient computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: transmit a Positioning Reference Signal (PRS) configuration to a user equipment (UE); receive PRS modification information from the UE; update the PRS configuration for the UE based on the PRS modification information; and transmit the updated PRS configuration to the UE.

[0247] Clause 87. A non-transient computer-readable medium as described in Clause 86, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

[0248] Clause 88. A non-transient computer-readable medium such as that in any of Clauses 86 to 87, wherein the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0249] Clause 89. A non-transient computer-readable medium such as any of Clauses 86 to 88, wherein computer-executable instructions that, when executed, cause the network entity to receive PRS modification information include computer-executable instructions that, when executed, cause the network entity to receive a request to modify the PRS configuration.

[0250] Clause 90. A non-transient computer-readable medium as described in Clause 89, wherein computer-executable instructions that, when executed, cause the network entity to receive PRS modification information include computer-executable instructions that, when executed, cause the network entity to receive PRS measurement results.

[0251] Clause 91. A non-transient computer-readable medium as described in Clause 90, wherein computer-executable instructions which, upon execution, cause the network entity to receive PRS measurement results include computer-executable instructions which, upon execution, cause the network entity to receive a reference signal received power (RSRP) value, a reference signal time difference (RSTD) value, a receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0252] Clause 92. A non-transient computer-readable medium such as any of Clauses 89 to 91, wherein computer-executable instructions that, upon execution, cause the network entity to receive a request to modify the PRS configuration include computer-executable instructions that, upon execution, cause the network entity to receive a request to cancel or remove a PRS instance that is not within the measurement gap.

[0253] Clause 93. A non-transient computer-readable medium such as any of Clauses 89 to 92, wherein computer-executable instructions that, when executed, cause the network entity to receive a request to modify the PRS configuration include computer-executable instructions that, when executed, cause the network entity to receive a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

[0254] Clause 94. A non-transient computer-readable medium such as any of Clauses 89 to 93, wherein computer-executable instructions that, when executed, cause the network entity to receive a request to modify the PRS configuration include, when executed, computer-executable instructions that, when executed, cause the network entity to receive a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources associated with a particular repetition of the foregoing, or a combination thereof.

[0255] Clause 95. A non-transient computer-readable medium such as any of Clauses 89 to 94, wherein computer-executable instructions that, when executed, cause the network entity to receive PRS modification information include computer-executable instructions that, when executed, cause the network entity to receive information indicating a start time, stop time, duration, or combination thereof for modifying the PRS configuration.

[0256] Clause 96. A non-transient computer-readable medium such as any of Clauses 86 to 95, wherein one or more instructions further cause the network entity to: receive a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement gap specified by the MG configuration.

[0257] Clause 97. An apparatus comprising: a memory, a transceiver, and a processor communicatively coupled to the memory and the transceiver, the memory, the transceiver, and the processor being configured to perform a method pursuant to any one of Clauses 1 to 24.

[0258] Clause 98. An apparatus comprising means for performing the method according to any one of Clauses 1 to 24.

[0259] Clause 99. A non-transient computer-readable medium storing computer-executable instructions, the computer-executable instructions including at least one instruction for causing a computer or processor to perform a method according to any one of Clauses 1 to 24.

[0260] The following are additional aspects:

[0261] In one aspect, a wireless communication method performed by a user equipment (UE) includes: receiving a positioning reference signal (PRS) configuration from a network entity; receiving a measurement gap (MG) configuration from a serving base station; determining that one or more transmission attributes of one or more PRS resources should be modified; and transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0262] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0263] In some aspects, the method further includes performing a PRS measurement on the one or more PRS resources before determining that one or more transmission attributes of one or more resources should be modified. In some aspects, performing the PRS measurement includes performing a PRS measurement on one or more transmit / receive points (TRPs) during a measurement interval specified by the MG configuration.

[0264] In some aspects, transmitting PRS modification information to the network entity includes transmitting PRS measurement results. In some aspects, the method includes: receiving an updated PRS configuration from the network entity; and performing a PRS measurement using the updated PRS configuration.

[0265] In some respects, the PRS modification information is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

[0266] In some respects, the PRS modification information includes a request to modify the PRS configuration.

[0267] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0268] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0269] In one aspect, a wireless communication method performed by a network entity includes: transmitting a Positioning Reference Signal (PRS) configuration to a user equipment (UE); receiving PRS modification information from the UE; updating the PRS configuration for the UE based on the PRS modification information; and transmitting the updated PRS configuration to the UE.

[0270] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0271] In some respects, the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

[0272] In some respects, the PRS modification information includes requests to modify the PRS configuration.

[0273] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0274] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0275] In some aspects, the method includes receiving a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

[0276] In one aspect, a wireless communication method performed by a base station includes: receiving Position Reference Signal (PRS) modification information from a User Equipment (UE); and transmitting the PRS modification information to a network entity.

[0277] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0278] In some respects, the PRS modification information is received or transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

[0279] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a Position Reference Signal (PRS) configuration from a network entity; receive a Measurement Gauge (MG) configuration from a serving base station; determine that one or more transmission attributes of one or more PRS resources should be modified; and cause the at least one transceiver to transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0280] In some respects, the at least one processor is further configured to perform PRS measurements before determining that one or more transport attributes of one or more resources should be modified.

[0281] In some respects, performing PRS measurements includes performing PRS measurements by the UE on one or more non-serving base stations during the measurement interval specified by the MG configuration.

[0282] In some respects, transmitting PRS modification information to the network entity includes transmitting PRS measurement results.

[0283] In some respects, the at least one processor is further configured to: receive an updated PRS configuration from a network entity; and use the updated PRS configuration to perform PRS measurements.

[0284] In some respects, the PRS modification information is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

[0285] In some respects, the PRS modification information includes a request to modify the PRS configuration.

[0286] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0287] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0288] In one aspect, a network entity includes: a memory; at least one network interface; and at least one processor communicatively coupled to the memory and the at least one network interface, the at least one processor being configured to: cause the at least one network interface to transmit a Position Reference Signal (PRS) configuration to a user equipment (UE); receive PRS modification information from the UE; update the PRS configuration for the UE based on the PRS modification information; and cause the at least one network interface to transmit the updated PRS configuration to the UE.

[0289] In some aspects, the network includes location servers, location management functions, or transmission / reception points.

[0290] In some respects, the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

[0291] In some respects, the PRS modification information includes requests to modify the PRS configuration.

[0292] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0293] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0294] In some respects, the at least one processor is further configured to receive a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

[0295] In one aspect, a base station includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive Position Reference Signal (PRS) modification information from a User Equipment (UE); and transmit the PRS modification information to a network entity.

[0296] In some respects, the PRS modification information is received or transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

[0297] In one aspect, a user equipment (UE) includes: means for receiving a positioning reference signal (PRS) configuration from a network entity; means for receiving a measurement gap (MG) configuration from a serving base station; means for determining that one or more transmission attributes of one or more resources should be modified; and means for transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0298] In one aspect, a network entity includes: means for transmitting a Position Reference Signal (PRS) configuration to a user equipment (UE); means for receiving PRS modification information from the UE; means for updating the PRS configuration for the UE based on the PRS modification information; and means for transmitting the updated PRS configuration to the UE.

[0299] In one aspect, a base station includes: means for receiving Position Reference Signal (PRS) modification information from a User Equipment (UE); and means for transmitting the PRS modification information to a network entity.

[0300] In one aspect, a non-transient computer-readable medium storing computer-executable instructions includes: at least one instruction instructing a user equipment (UE) to receive a positioning reference signal (PRS) configuration from a network entity; at least one instruction instructing the UE to receive a measurement gap (MG) configuration from a serving base station; at least one instruction instructing the UE to determine that one or more transmission attributes of one or more resources should be modified; and at least one instruction instructing the UE to transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0301] In one aspect, a non-transient computer-readable medium storing computer-executable instructions includes: an instruction network entity transmitting at least one instruction to a user equipment (UE) for a positioning reference signal (PRS) configuration; an instruction network entity receiving at least one instruction from the UE for PRS modification information; an instruction network entity updating at least one instruction for the UE based on the PRS modification information; and an instruction network entity transmitting at least one instruction to the UE for an updated PRS configuration.

[0302] In one aspect, a non-transient computer-readable medium storing computer-executable instructions includes: at least one instruction instructing a base station (BS) to receive positioning reference signal (PRS) modification information from a user equipment (UE); and at least one instruction instructing the BS to transmit the PRS modification information to a network entity.

[0303] The following are additional aspects:

[0304] In one aspect, a wireless communication method performed by a user equipment (UE) includes: receiving a positioning reference signal (PRS) configuration from a network entity; receiving a measurement gap (MG) configuration from a serving base station; determining that one or more transmission attributes of one or more PRS resources should be modified; and transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0305] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0306] In some aspects, the method further includes performing a PRS measurement on the one or more PRS resources before determining that one or more transport attributes of the one or more resources should be modified.

[0307] In some respects, performing PRS measurements includes performing PRS measurements on one or more transmit / receive points (TRPs) during the measurement interval specified by the MG configuration.

[0308] In some respects, transmitting PRS modification information to the network entity includes transmitting PRS measurement results.

[0309] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0310] In some aspects, the method includes: receiving an updated PRS configuration from a network entity; and using the updated PRS configuration to perform PRS measurements.

[0311] In some respects, the PRS modification information is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0312] In some respects, the PRS modification information includes a request to modify the PRS configuration.

[0313] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0314] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0315] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0316] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration.

[0317] In one aspect, a wireless communication method performed by a network entity includes: transmitting a Positioning Reference Signal (PRS) configuration to a user equipment (UE); receiving PRS modification information from the UE; updating the PRS configuration for the UE based on the PRS modification information; and transmitting the updated PRS configuration to the UE.

[0318] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0319] In some respects, the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0320] In some respects, the PRS modification information includes requests to modify the PRS configuration.

[0321] In some respects, receiving PRS modification information includes receiving PRS measurement results.

[0322] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0323] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0324] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0325] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0326] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof for modifying the PRS configuration.

[0327] In some aspects, the method includes receiving a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

[0328] In one aspect, a wireless communication method performed by a base station includes: receiving Position Reference Signal (PRS) modification information from a User Equipment (UE); and transmitting the PRS modification information to a network entity.

[0329] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0330] In some respects, the PRS modification information is received or transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0331] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a Position Reference Signal (PRS) configuration from a network entity; receive a Measurement Gauge (MG) configuration from a serving base station; determine that one or more transmission attributes of one or more PRS resources should be modified; and cause the at least one transceiver to transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0332] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0333] In some respects, the at least one processor is further configured to perform PRS measurements before determining that one or more transport attributes of one or more resources should be modified.

[0334] In some respects, performing PRS measurements includes performing PRS measurements by the UE on one or more non-serving base stations during the measurement interval specified by the MG configuration.

[0335] In some respects, transmitting PRS modification information to the network entity includes transmitting PRS measurement results.

[0336] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0337] In some respects, the at least one processor is further configured to: receive an updated PRS configuration from a network entity; and use the updated PRS configuration to perform PRS measurements.

[0338] In some respects, the PRS modification information is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0339] In some respects, the PRS modification information includes a request to modify the PRS configuration.

[0340] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0341] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0342] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0343] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration.

[0344] In one aspect, a network entity includes: a memory; at least one network interface; and at least one processor communicatively coupled to the memory and the at least one network interface, the at least one processor being configured to: cause the at least one network interface to transmit a Position Reference Signal (PRS) configuration to a user equipment (UE); receive PRS modification information from the UE; update the PRS configuration for the UE based on the PRS modification information; and cause the at least one network interface to transmit the updated PRS configuration to the UE.

[0345] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0346] In some respects, the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0347] In some respects, the PRS modification information includes requests to modify the PRS configuration.

[0348] In some respects, receiving PRS modification information includes receiving PRS measurement results.

[0349] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0350] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0351] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0352] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0353] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof for modifying the PRS configuration.

[0354] In some respects, the at least one processor is further configured to receive a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

[0355] In one aspect, a base station includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive Position Reference Signal (PRS) modification information from a User Equipment (UE); and transmit the PRS modification information to a network entity.

[0356] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0357] In some respects, the PRS modification information is received or transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

[0358] In one aspect, a user equipment (UE) includes: means for receiving a positioning reference signal (PRS) configuration from a network entity; means for receiving a measurement gap (MG) configuration from a serving base station; means for determining that one or more transmission attributes of one or more PRS resources should be modified; and means for transmitting PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0359] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0360] In some aspects, the method further includes performing a PRS measurement on the one or more PRS resources before determining that one or more transport attributes of the one or more resources should be modified.

[0361] In some aspects, the apparatus for performing PRS measurements includes means for performing PRS measurements on one or more transmit / receive points (TRPs) during a measurement gap specified by the MG configuration.

[0362] In some respects, the means for transmitting PRS modification information to the network entity includes means for transmitting PRS measurement results.

[0363] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0364] In some aspects, the method includes: means for receiving an updated PRS configuration from a network entity; and means for performing PRS measurements using the updated PRS configuration.

[0365] In some respects, the PRS modification information is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0366] In some respects, the PRS modification information includes a request to modify the PRS configuration.

[0367] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0368] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0369] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0370] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration.

[0371] In one aspect, a network entity includes: means for transmitting a Position Reference Signal (PRS) configuration to a user equipment (UE); means for receiving PRS modification information from the UE; means for updating the PRS configuration for the UE based on the PRS modification information; and means for transmitting the updated PRS configuration to the UE.

[0372] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0373] In some respects, the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0374] In some respects, the PRS modification information includes requests to modify the PRS configuration.

[0375] In some aspects, the apparatus for receiving PRS modification information includes apparatus for receiving PRS measurement results.

[0376] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0377] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0378] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0379] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0380] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof for modifying the PRS configuration.

[0381] In one aspect, a base station (BS) includes: means for receiving positioning reference signal (PRS) modification information from user equipment (UE); and means for transmitting the PRS modification information to a network entity.

[0382] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0383] In some respects, the PRS modification information is received or transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0384] In one aspect, a non-transient computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a Position Reference Signal (PRS) configuration from a network entity; receive a Measurement Gauge (MG) configuration from a serving base station; determine that one or more transmission attributes of one or more PRS resources should be modified; and transmit PRS modification information to the network entity based on one or more transmission attributes of the one or more PRS resources to be modified.

[0385] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0386] In some aspects, the method further includes performing a PRS measurement on the one or more PRS resources before determining that one or more transport attributes of the one or more resources should be modified.

[0387] In some respects, computer-executable instructions that cause the UE to perform PRS measurements at execution include computer-executable instructions that cause the UE to perform PRS measurements on one or more transmit / receive points (TRPs) during the measurement gap specified by the MG configuration at execution.

[0388] In some respects, computer-executable instructions that cause the UE to transmit PRS modification information to a network entity at execution include computer-executable instructions that cause the UE to transmit PRS measurement results at execution.

[0389] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0390] In some respects, one or more instructions further enable the UE to: receive an updated PRS configuration from a network entity; and use the updated PRS configuration to perform PRS measurements.

[0391] In some respects, the PRS modification information is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0392] In some respects, the PRS modification information includes a request to modify the PRS configuration.

[0393] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0394] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0395] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0396] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration.

[0397] In one aspect, a non-transient computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: transmit a Positioning Reference Signal (PRS) configuration to a user equipment (UE); receive PRS modification information from the UE; update the PRS configuration for the UE based on the PRS modification information; and transmit the updated PRS configuration to the UE.

[0398] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0399] In some respects, the PRS modification information is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0400] In some respects, the PRS modification information includes requests to modify the PRS configuration.

[0401] In some respects, computer-executable instructions that cause the network entity to receive PRS modification information at execution include computer-executable instructions that cause the network entity to receive PRS measurement results at execution.

[0402] In some respects, the PRS measurement results include the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

[0403] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS instances that are not within the measurement interval.

[0404] In some respects, requests to modify PRS configurations include requests to cancel or remove one or more PRS resource sets, one or more PRS resources in those PRS resource sets, one or more PRS instances of those PRS resources, and / or one or more duplicates of PRS instances, or to reduce their overhead.

[0405] In some respects, requests to modify PRS configurations include requests to cancel or remove PRS resources for one or more frequency layers, one or more transmit / receive points for a frequency layer, one or more frequency layers for one or more transmit / receive points, and / or PRS resources associated with a specific repetition of the above.

[0406] In some respects, the PRS modification information indicates the start time, stop time, duration, or a combination thereof for modifying the PRS configuration.

[0407] In one aspect, a non-transient computer-readable medium storing computer-executable instructions that, when executed by a base station (BS), cause the BS to: receive Position Reference Signal (PRS) modification information from a user equipment (UE); and transmit the PRS modification information to a network entity.

[0408] In some respects, the network entity includes a location server, location management functions, or a transmission / reception point.

[0409] In some respects, the PRS modification information is received or transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

[0410] Other objectives and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.

[0411] Although the foregoing disclosure illustrates illustrative aspects of this disclosure, it should be noted that various changes and modifications may be made therein without departing from the scope of this disclosure as defined by the appended claims. The functions, steps, and / or actions in the method claims according to the aspects of this disclosure described herein need not be performed in any particular order. Furthermore, although elements of this disclosure may be described or claimed in the singular, pluralism is also contemplated unless explicitly stated to be limited to the singular.

Claims

1. A wireless communication method performed by a user equipment (UE), the method comprising: Receive location reference signals (PRS) from network entities that indicate one or more PRS resources; Determine that one or more transport attributes of the one or more PRS resources should be modified; A request to modify the PRS configuration is transmitted to the network entity based on one or more transport attributes of the one or more PRS resources to be modified, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; Receive the updated PRS configuration from the network entity; and Use the updated PRS configuration to perform PRS measurements.

2. The method of claim 1, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

3. The method of claim 1, further comprising: Before determining that one or more transport attributes of the one or more PRS resources should be modified, a PRS measurement is performed on the one or more PRS resources.

4. The method of claim 3, wherein performing the PRS measurement includes performing a PRS measurement on one or more transmit / receive points TRP during a measurement gap specified by the measurement gap MG configuration.

5. The method of claim 1, wherein transmitting the request to modify the PRS configuration to the network entity includes transmitting PRS measurement results.

6. The method of claim 5, wherein transmitting the PRS measurement result includes the received power of the transmitted reference signal (RSRP), the time difference of the reference signal (RSTD), the received-to-transmit Rx-Tx value, or a combination thereof.

7. The method of claim 1, wherein transmitting the request to modify the PRS configuration comprises transmitting the request to modify the PRS configuration via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

8. The method of claim 1, wherein transmitting the request to modify the PRS configuration includes transmitting a request to cancel or remove a PRS instance that is not in the measurement gap.

9. The method of claim 1, wherein transmitting the request to modify the PRS configuration includes transmitting a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

10. The method of claim 1, wherein transmitting the request to modify the PRS configuration includes transmitting a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or a combination thereof.

11. A wireless communication method performed by a network entity, the method comprising: Transmit Positioning Reference Signal (PRS) configuration to the user equipment (UE); The UE receives a request to modify the PRS configuration, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; The PRS configuration for the UE is updated based on the request to modify the PRS configuration; as well as The updated PRS configuration is transmitted to the UE.

12. The method of claim 11, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

13. The method of claim 11, wherein the request to modify the PRS configuration is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

14. The method of claim 11, wherein receiving the request to modify the PRS configuration includes receiving PRS measurement results.

15. The method of claim 14, wherein receiving the PRS measurement result includes receiving reference signal received power (RSRP), reference signal time difference (RSTD), received-to-transmit (Rx-Tx) value, or a combination thereof.

16. The method of claim 11, wherein receiving the request to modify the PRS configuration includes receiving a request to cancel or remove a PRS instance that is not within the measurement interval.

17. The method of claim 11, wherein receiving the request to modify the PRS configuration includes receiving a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

18. The method of claim 11, wherein receiving the request to modify the PRS configuration includes receiving a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or a combination thereof.

19. The method of claim 11, further comprising: The UE receives a report comprising one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

20. A user equipment (UE), comprising: Memory; At least one transceiver; as well as At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: Receive location reference signals (PRS) from network entities that indicate one or more PRS resources; Determine that one or more transport attributes of the one or more PRS resources should be modified; The at least one transceiver transmits a request to the network entity to modify the PRS configuration based on one or more transport attributes of the one or more PRS resources to be modified, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; Receive the updated PRS configuration from the network entity; and Use the updated PRS configuration to perform PRS measurements.

21. The UE of claim 20, wherein the network entity includes a location server, a location management function, or a transmit / receive point.

22. The UE of claim 20, wherein the at least one processor is further configured to perform a PRS measurement before determining that one or more transport attributes of one or more resources should be modified.

23. The UE of claim 22, wherein performing the PRS measurement includes performing PRS measurements on one or more non-serving base stations performed by the UE during a measurement gap specified by the measurement gap MG configuration.

24. The UE of claim 20, wherein the request to modify the PRS configuration includes PRS measurement results.

25. The UE of claim 24, wherein the PRS measurement result includes the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

26. The UE of claim 20, wherein the request to modify the PRS configuration is transmitted via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

27. The UE of claim 20, wherein the request to modify the PRS configuration includes a request to cancel or remove a PRS instance that is not within the measurement interval.

28. The UE of claim 20, wherein the request to modify the PRS configuration includes a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

29. The UE of claim 20, wherein the request to modify the PRS configuration includes a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or a combination thereof.

30. A network entity, comprising: Memory; At least one network interface; as well as At least one processor communicatively coupled to the memory and the at least one network interface, the at least one processor being configured to: This enables the at least one network interface to transmit a Position Reference Signal (PRS) configuration to the User Equipment (UE); The UE receives a request to modify the PRS configuration, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; The PRS configuration for the UE is updated based on the request to modify the PRS configuration; as well as This causes the at least one network interface to transmit the updated PRS configuration to the UE.

31. The network entity of claim 30, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

32. The network entity of claim 30, wherein the request to modify the PRS configuration is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

33. The network entity of claim 30, wherein the request to modify the PRS configuration includes PRS measurement results.

34. The network entity of claim 33, wherein the PRS measurement result includes the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the receive-to-transmit (Rx-Tx) value, or a combination thereof.

35. The network entity of claim 30, wherein the request to modify the PRS configuration includes a request to cancel or remove a PRS instance that is not within the measurement interval.

36. The network entity of claim 30, wherein the request to modify the PRS configuration includes a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

37. The network entity of claim 30, wherein the request to modify the PRS configuration includes a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or a combination thereof.

38. The network entity of claim 30, wherein the at least one processor is further configured to: The UE receives a report comprising one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

39. A user equipment (UE), comprising: A means for receiving a location reference signal (PRS) configuration indicating one or more PRS resources from a network entity; A means for determining one or more transport attributes of the one or more PRS resources that should be modified; A means for transmitting a request to modify the PRS configuration to a network entity based on one or more transport attributes of the one or more PRS resources to be modified, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; A means for receiving an updated PRS configuration from the network entity; as well as A means for performing PRS measurements using the updated PRS configuration.

40. The UE of claim 39, wherein the network entity includes a location server, a location management function, or a transmit / receive point.

41. The UE of claim 39, further comprising: Before determining that one or more transport attributes of the one or more PRS resources should be modified, a PRS measurement is performed on the one or more PRS resources.

42. The UE of claim 41, wherein the means for performing the PRS measurement includes means for performing a PRS measurement of one or more transmit / receive points TRP during a measurement gap specified by the measurement gap MG configuration.

43. The UE of claim 39, wherein the means for transmitting the request to modify the PRS configuration to the network entity includes means for transmitting PRS measurement results.

44. The UE of claim 43, wherein the means for transmitting PRS measurement results includes means for transmitting the reference signal received power (RSRP) value, the reference signal time difference (RSTD) value, the received-to-transmit Rx-Tx value, or a combination thereof.

45. The UE of claim 39, wherein the means for transmitting the request to modify the PRS configuration includes means for transmitting the request to modify the PRS configuration via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

46. ​​The UE of claim 39, wherein the means for transmitting the request to modify the PRS configuration includes means for transmitting a request to cancel or remove a PRS instance that is not in the measurement gap.

47. The UE of claim 39, wherein the means for transmitting the request to modify the PRS configuration includes means for transmitting a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

48. The UE of claim 39, wherein the means for transmitting the request to modify the PRS configuration includes means for transmitting a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or a combination thereof.

49. A network entity, comprising: A device for transmitting Positioning Reference Signal (PRS) configuration to user equipment (UE); A means for receiving from the UE a request to modify the PRS configuration, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; A means for updating the PRS configuration for the UE based on the request to modify the PRS configuration; as well as A means for transmitting the updated PRS configuration to the UE.

50. The network entity of claim 49, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

51. The network entity of claim 49, wherein the request to modify the PRS configuration is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

52. The network entity of claim 49, wherein the means for receiving the request to modify the PRS configuration includes means for receiving PRS measurement results.

53. The network entity of claim 52, wherein the means for receiving PRS measurement results includes means for receiving a reference signal received power (RSRP) value, a reference signal time difference (RSTD) value, a received-to-transmit (Rx-Tx) value, or a combination thereof.

54. The network entity of claim 49, wherein the means for receiving the request to modify the PRS configuration includes means for receiving a request to cancel or remove a PRS instance that is not in the measurement interval.

55. The network entity of claim 49, wherein the means for receiving the request to modify the PRS configuration includes means for receiving a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

56. The network entity of claim 49, wherein the means for receiving the request to modify the PRS configuration includes means for receiving a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or a combination thereof.

57. The network entity as described in claim 49, further comprising: A means for receiving a report from the UE, the report including one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

58. A non-transient computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: Receive location reference signals (PRS) from network entities that indicate one or more PRS resources; Determine that one or more transport attributes of the one or more PRS resources should be modified; A request to modify the PRS configuration is transmitted to the network entity based on one or more transport attributes of the one or more PRS resources to be modified, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; Receive the updated PRS configuration from the network entity; and Use the updated PRS configuration to perform PRS measurements.

59. The non-transient computer-readable medium of claim 58, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

60. The non-transient computer-readable medium of claim 58, wherein one or more instructions further cause the UE to: Before determining that one or more transport attributes of the one or more PRS resources should be modified, a PRS measurement is performed on the one or more PRS resources.

61. The non-transient computer-readable medium of claim 60, wherein the computer-executable instructions that cause the UE to perform the PRS measurement when executed include computer-executable instructions that cause the UE to perform a PRS measurement of one or more transmit / receive points TRPs during a measurement gap specified by the measurement gap MG configuration when executed.

62. The non-transient computer-readable medium of claim 58, wherein the computer-executable instructions that, when executed, cause the UE to transmit the request to modify the PRS configuration to the network entity include computer-executable instructions that, when executed, cause the UE to transmit PRS measurement results.

63. The non-transient computer-readable medium of claim 62, wherein the computer-executable instructions that cause the UE to transmit PRS measurement results when executed include computer-executable instructions that cause the UE to transmit a reference signal received power RSRP value, a reference signal time difference RSTD value, a received to transmit Rx-Tx value, or a combination thereof when executed.

64. The non-transient computer-readable medium of claim 58, wherein the computer-executable instructions causing the UE to transmit the request to modify the PRS configuration when executed include causing the UE to transmit the computer-executable instructions to modify the PRS configuration via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

65. The non-transient computer-readable medium of claim 58, wherein the computer-executable instructions that cause the UE to transmit the request to modify the PRS configuration when executed include computer-executable instructions that cause the UE to transmit a request to cancel or remove a PRS instance that is not in the measurement gap when executed.

66. The non-transient computer-readable medium of claim 58, wherein the computer-executable instructions that, when executed, cause the UE to transmit the request to modify the PRS configuration include, when executed, causing the UE to transmit computer-executable instructions that, when executed, cause the UE to transmit a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

67. The non-transient computer-readable medium of claim 58, wherein the computer-executable instructions that, when executed, cause the UE to transmit the request to modify the PRS configuration include, when executed, causing the UE to transmit the computer-executable instructions that, when executed, cause the UE to transmit a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or a combination thereof.

68. A non-transitory computer-readable medium storing computer-executable instructions, said instructions causing the network entity, when executed by the network entity, to: Transmit Positioning Reference Signal (PRS) configuration to the user equipment (UE); The UE receives a request to modify the PRS configuration, wherein the request to modify the PRS configuration includes information indicating a start time, stop time, duration, or a combination thereof associated with modifying the PRS configuration; The PRS configuration for the UE is updated based on the request to modify the PRS configuration; and The updated PRS configuration is transmitted to the UE.

69. The non-transient computer-readable medium of claim 68, wherein the network entity includes a location server, a location management function, or a transmission / reception point.

70. The non-transient computer-readable medium of claim 68, wherein the request to modify the PRS configuration is received via Radio Resource Control (RRC), Long Term Evolution (LTE) Positioning Protocol (LPP), Media Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI), or a combination thereof.

71. The non-transient computer-readable medium of claim 68, wherein the computer-executable instructions that, when executed, cause the network entity to receive the request to modify the PRS configuration include computer-executable instructions that, when executed, cause the network entity to receive PRS measurement results.

72. The non-transient computer-readable medium of claim 71, wherein the computer-executable instructions that cause the network entity to receive PRS measurement results when executed include computer-executable instructions that cause the network entity to receive a reference signal power RSRP value, a reference signal time difference RSTD value, a received transmission Rx-Tx value, or a combination thereof when executed.

73. The non-transient computer-readable medium of claim 68, wherein the computer-executable instructions that, when executed, cause the network entity to receive the request to modify the PRS configuration include computer-executable instructions that, when executed, cause the network entity to receive a request to cancel or remove a PRS instance that is not within the measurement interval.

74. The non-transient computer-readable medium of claim 68, wherein the computer-executable instructions that, when executed, cause the network entity to receive the request to modify the PRS configuration include, when executed, computer-executable instructions that cause the network entity to receive a request to cancel or remove one or more PRS resource sets, one or more PRS resources in the one or more PRS resource sets, one or more PRS instances of the one or more PRS resources, one or more duplicates of the PRS instances or a combination thereof, or to reduce their overhead.

75. The non-transient computer-readable medium of claim 68, wherein the computer-executable instructions that, when executed, cause the network entity to receive the request to modify the PRS configuration include, when executed, computer-executable instructions that cause the network entity to receive a request to cancel or remove PRS resources of one or more frequency layers, one or more transmit / receive points of a frequency layer, one or more frequency layers of one or more transmit / receive points, PRS resources repeatedly associated with the foregoing, or combinations thereof.

76. The non-transient computer-readable medium of claim 68, wherein one or more instructions further cause the network entity to: The UE receives a report comprising one or more measurements performed by the UE on one or more non-serving base stations during a measurement interval specified by the MG configuration.

Images