Storing positioning-related capabilities in the network

Abstract

The present invention discloses a technique for wireless communication. In one aspect, a user equipment (UE) sends one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

Description

Technical Field

[0001] This patent application claims priority to Greek patent application No. 20210100010 entitled “STORING POSITIONING-RELATED CAPABILITIES IN THE NETWORK”, filed on January 7, 2021, which has been assigned to the assignee of this application and is hereby expressly incorporated herein by reference in its entirety.

[0002] In summary, all aspects of this disclosure relate to wireless communications. Prior Technology

[0003] Wireless communication systems have evolved through several generations, including first-generation analog wireless telephony (1G), second-generation (2G) digital wireless telephony (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, internet-enabled wireless services, and fourth-generation (4G) services (e.g., LTE or WiMax). Currently, many different types of wireless communication systems are used, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include Advanced Cellular Analog Telephone 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.

[0004] The fifth-generation (5G) wireless standard (known as New Radio (NR)) delivers higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on Location Reference Signals (RS-P), such as downlink, uplink, or sidelink Location Reference Signals (PRS)), and other technological enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advancements in PRS procedures and technology, and the high-density deployment of 5G, enable highly accurate 5G-based positioning. Summary of the Invention

[0005] The following is a simplified overview relating to one or more aspects disclosed herein. Therefore, this overview should not be considered an exhaustive review relating to all anticipated aspects, nor should it be considered to identify key or important elements relating to all anticipated aspects, nor 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 involving the mechanisms disclosed herein, as a prelude to the detailed description that follows.

[0006] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: sending one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0007] In one aspect, a method of wireless communication performed by a network entity includes: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0008] In one aspect, a method of wireless communication performed by a first network entity includes: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and transmitting the set of values ​​to a second network entity via one or more capability transmission messages to enable the second network entity to store the set of values ​​for use in subsequent location dialogues involving the UE.

[0009] In one aspect, a method of wireless communication performed by a second network entity includes: receiving, via one or more capability transmission messages, a set of values ​​for a set of positioning capability parameters from a user equipment (UE) in one or more positioning capability reports, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE.

[0010] 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: transmit one or more positioning capability reports to a location server via the at least one transceiver, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0011] In one aspect, a network entity 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 one or more location capability reports from a user equipment (UE) via the at least one transceiver, the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0012] In one aspect, a first network entity 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 one or more location capability reports from a user equipment (UE) via the at least one transceiver, the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and transmit the set of values ​​to a second network entity via one or more capability transmission messages via the at least one transceiver, such that the second network entity can store the set of values ​​for subsequent location dialogues involving the UE.

[0013] In one aspect, a second network entity 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, via the at least one transceiver, a set of values ​​for a set of positioning capability parameters from a user equipment (UE) via one or more capability transmission messages from the first network entity, wherein the set of values ​​is invariant for subsequent positioning dialogues involving the UE.

[0014] In one aspect, a user equipment (UE) includes: means for sending one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0015] In one aspect, a network entity includes: means for receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0016] In one aspect, a first network entity includes: means for receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and means for transmitting the set of values ​​to a second network entity via one or more capability transmission messages to enable the second network entity to store the set of values ​​for subsequent location dialogues involving the UE.

[0017] In one aspect, a second network entity includes: a single component for receiving a set of values ​​of a set of positioning capability parameters from a first network entity via one or more capability transmission messages, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE.

[0018] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: send one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0019] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network entity, cause the network entity to perform the following operations: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0020] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a first network entity, cause the first network entity to: receive one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and transmit the set of values ​​to a second network entity via one or more capability transmission messages, such that the second network entity can store the set of values ​​for use in subsequent location dialogues involving the UE.

[0021] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a second network entity, cause the second network entity to: receive a set of values ​​for a set of positioning capability parameters from a user equipment (UE) via one or more capability transmission messages, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE.

[0022] Based on the diagrams and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Simple Explanation of the Diagram

[0023] Diagrams are provided to aid in the description of various aspects of this disclosure, and are provided solely for illustrative purposes and not for limitation.

[0024] Figure 1 illustrates an example wireless communication system according to various aspects of this disclosure.

[0025] Figures 2A and 2B illustrate example wireless network architectures according to various aspects of this disclosure.

[0026] Figures 3A to 3C are simplified block diagrams of several example aspects of components that can be adopted in user equipment (UE), base stations, and network entities and configured to support communications as taught herein.

[0027] Figure 4 illustrates example positioning operations based on various aspects of this disclosure.

[0028] Figure 5 illustrates an example Long Term Evolution Positioning Protocol (LPP) capability transfer procedure according to various aspects of this disclosure.

[0029] Figure 6 illustrates an example LPP capability instruction procedure based on various aspects of this disclosure.

[0030] Figure 7 illustrates an example capability storage program based on various aspects of this disclosure.

[0031] Figure 8 illustrates an example capability storage procedure when the UE's location server changes due to mobility, according to various aspects of this disclosure.

[0032] Figures 9 to 14 illustrate example methods of wireless communication according to various aspects of this disclosure. Implementation

[0033] Aspects of this disclosure are provided in the following description and related figures, which relate to various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of this disclosure. Furthermore, well-known elements of this disclosure will not be described in detail or will be omitted to avoid obscuring relevant details of this disclosure.

[0034] 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” should not be construed as preferred or advantageous over other aspects. 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.

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

[0036] Furthermore, many aspects are described as a sequence of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by a specific circuit (e.g., an application-specific integrated circuit (ASIC)), program instructions executed by one or more processors, or a combination of both. Additionally, the sequence of actions described herein can be considered to be fully embodied in any form of non-transitory computer-readable storage medium having a corresponding set of computer instructions stored therein, which, when executed, will cause or instruct the associated processor of the device to perform the functions described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, the corresponding form of any such aspect can be described herein as, for example, "logically configured" to perform the described actions.

[0037] As used herein, unless otherwise indicated, 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). 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, consumer asset positioning 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 (e.g., at certain times) 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 device”, “wireless device”, “subscriber equipment”, “subscriber terminal”, “subscriber station”, “user terminal” or “UT”, “mobile device”, “mobile terminal”, “mobile station”, or variations thereof. Typically, a UE can communicate with the core network via the RAN, and can connect to external networks such as the Internet and other UEs via the core network. Of course, other mechanisms for connecting the UE to the core network and / or the Internet are also possible, such as on wired access networks, wireless local area network (WLAN) networks (e.g., based on the IEEE 802.11 standard), etc.

[0038] In communication with the UE, the base station can operate according to one of several RATs, depending on the network in which it is deployed. The base station can be alternatively referred to as an Access Point (AP), network node, Node B, Evolved Node B (eNB), Next Generation eNB (ng-eNB), New Radio (NR) Node B (also known as gNB or gNodeB), etc. The base station primarily supports the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station can provide pure edge node signaling functions, while in others, it can provide additional control and / or network management functions. The communication link through which the UE can send signals to the base station is called an uplink (UL) channel (e.g., reverse flow channel, reverse control channel, access channel, etc.). The communication link through which the base station can send signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward flow channel, etc.). As used in this article, the term Traffic Channel (TCH) can refer to either the uplink / reverse traffic channel or the downlink / forward traffic channel.

[0039] The term "base station" can refer to a single entity transmit / receive point (TRP) or multiple entity TRPs that may or may not be co-located. For example, when the term "base station" refers to a single entity TRP, the entity TRP can be an antenna of the base station corresponding to the base station's cell (or several cell sectors). When the term "base station" refers to multiple co-located entity TRPs, the entity TRP can be the base station's antenna array (e.g., in a multiple-input multiple-output (MIMO) system or in the case where the base station employs beamforming). When the term "base station" refers to multiple non-co-located entity TRPs, the entity TRP can be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common resource via a transmission medium) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located entity TRP can be the serving base station receiving measurement reports from the UE and a neighboring base station where the UE is measuring its reference radio frequency (RF) signal. As used in this article, the TRP is the point from which a base station transmits and receives wireless signals, so a transmission from or a reception at a base station should be understood to refer to the specific TRP of the base station.

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

[0041] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, 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.

[0042] Figure 1 illustrates an exemplary wireless communication system 100. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base stations 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 the wireless communication system 100 corresponds to an LTE network) or gNBs (where the 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.

[0043] Base station 102 can collectively form a RAN and is interface-connected to core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul link 122, and is interface-connected to one or more location servers 172 (e.g., location management function unit (LMF) or secure user plane location (SUPL) positioning platform (SLP)) via core network 170. Location server 172 can be part of core network 170 or external to core network 170. Location server 172 can be integrated with base station 102. UE 104 can communicate with location server 172 directly or indirectly. For example, UE 104 can communicate with location server 172 via base station 102 currently serving UE 104. UE 104 can also communicate with location server 172 via another path, such as via an application server (not shown), via another network (e.g., via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below)), etc. For signaling purposes, communication between UE 104 and location server 172 can be represented as an indirect connection (e.g., via core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), wherein intermediate nodes (if any) are omitted in the signaling diagram for clarity.

[0044] In addition to other functions, base station 102 may also perform functions related to one or more of the following: transmission of user data, encryption and decryption of radio channels, 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 device tracking, RAN information management (RIM), paging, location, and transmission of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) through backhaul link 134 (which may be wired or wireless).

[0045] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage for its respective geographic coverage area 110. In one aspect, base station 102 can support one or more cells in each geographic 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 carrier frequency, component carrier, carrier, frequency band, etc.)) and can be associated with an identifier (e.g., Entity Cell Identifier (PCI), Enhanced Cell Identifier (FCI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI), etc.) used 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 for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, the term "cell" can refer to either or both of the logical communication entity and the base station supporting it, 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., a sector) of a base station, within which a carrier frequency can be detected and used for communication within a portion of the 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 significantly overlap with larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that significantly overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that can provide service to restricted groups referred to as Closed Subscriber Groups (CSGs).

[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 (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be traversed via 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 also include a wireless local area network (WLAN) access point (AP) 150, which communicates 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 an idle channel assessment (CCA) or listen-before-talk (LBT) procedure before communication to determine whether the channel is available.

[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 improve access network coverage and / or increase access network capacity. NR in unlicensed spectrum can be referred to as NR-U. LTE in unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0050] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180 communicating with the UE 182, which may operate in mmW and / or near-mmW frequencies. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum of radio frequency (RF). EHF has a range from 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. 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 may 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 understood 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 description is 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. Traditionally, 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 direction 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 array of antennas (called a "phased array" or "antenna array") that creates beams of RF waves that can be "guided" to points in different directions without actually moving the antennas. Specifically, RF current from the transmitters is fed to individual antennas with the correct phase relationship, such that the radio waves from the individual antennas are added together to increase radiation in the desired direction and cancel each other out in the undesired direction to suppress radiation.

[0052] Transmit beams can be quasi-co-located, meaning they appear to have the same parameters to the receiver (e.g., UE), regardless of whether the transmit antennas of the 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 QCL type 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 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., to increase the gain level of that RF signal). Therefore, when a receiver is described as beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along 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 noise ratio (SINR), etc.) of the RF signal received from that direction.

[0054] Transmit and receive beams can be spatially correlated. Spatial correlation means that the parameters of the second beam (e.g., transmit or receive beam) used for the second reference signal can be derived from information about the first beam (e.g., receive or transmit beam) used for the first reference signal. For example, a UE can use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

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

[0056] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is generally (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes arise with FR2; although it differs from the extremely high frequency (EHF) band (30 GHz – 300 GHz), it is generally (interchangeably) referred to as the “millimeter wave” band in documents and articles, which is recognized as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0057] The frequencies between FR1 and FR2 are generally referred to as intermediate frequencies (IFs). Recent 5G NR studies have identified the operating bands of these IFs as the frequency range name FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to the IF. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4a or FR4–1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0058] In light of the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can be broadly interpreted to mean a frequency that is less than 6 GHz, can be within FR1, or can include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can be broadly interpreted to mean a frequency that can include intermediate frequency band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0059] In multi-carrier systems (such as 5G), one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "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 common and UE-specific control channels and can be a carrier in 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 in an unlicensed frequency. Secondary carriers may contain only necessary signaling information and signals. For example, UE-specific signaling information and signals may not exist in a secondary carrier because both the primary uplink and primary downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. This also applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a “serving cell” (whether PCell or SCell) corresponds to the carrier frequency / component carrier on which a base station is communicating, the terms “cell,” “serving cell,” “component carrier,” and “carrier frequency” can be used interchangeably.

[0060] For example, still referring to Figure 1, one of the frequencies used by the macrocell base station 102 can be an anchor carrier (or "PCell"), and the other frequencies used 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 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) (compared to the data rate achieved by a single 20 MHz carrier).

[0061] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 on the communication link 120 and / or with the mmW base station 180 on the mmW communication link 184. For example, the macro cell 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.

[0062] In some cases, UE 164 and UE 182 may be able to perform sidelink communication. UEs supporting sidelink (SL-UEs) can communicate with base station 102 on communication link 120 using the Uu interface (i.e., an empty intermediary interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other on radio sidelink 160 using the PC5 interface (i.e., an empty intermediary interface between UEs supporting sidelink). Radio sidelink (or simply "sidelink") is an adaptation of core cellular (e.g., LTE, NR) standards that allows direct communication between two or more UEs without going through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X), enhanced V2X (eV2X), etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs using sidelink communication may be within the geographic coverage area 110 of base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of base station 102, or otherwise unable to receive transmissions from base station 102. In some cases, the group of SL-UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each SL-UE transmits to every other SL-UE in the group. In some cases, base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between SL-UEs without the participation of base station 102.

[0063] In one aspect, the side link 160 can operate on a wireless communication medium of interest that can be shared with other wireless communications between other vehicle and / or infrastructure access points and other RATs. The “medium” can consist of one or more time, frequency, and / or space communication resources (e.g., comprising one or more channels spanning one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs. In one aspect, the medium of interest can correspond to at least a portion of an unlicensed frequency band shared among various RATs. While (e.g., government entities such as the Federal Communications Commission (FCC)) have reserved different licensed frequency bands for certain communication systems, these systems (especially those employing small cell access points) have recently expanded their operations into unlicensed frequency bands, such as the unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies, most notably IEEE 802.11x WLAN technology, commonly referred to as “Wi-Fi”). Examples of this type of system include different variants of CDMA, TDMA, FDMA, Orthogonal FDMA (OFDMA), and Single-Carrier FDMA (SC-FDMA) systems.

[0064] It should be noted that although only two UEs in Figure 1 are shown as SL-UEs (i.e., UEs 164 and 182), any UE shown can be an SL-UE. Furthermore, although only UE 182 is described as capable of beamforming, any UE shown (including UE 164) can perform beamforming. When SL-UEs are capable of beamforming, they can beamform towards each other (i.e., towards other SL UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base stations 102, 180, cell 102', access point 150), etc. Therefore, in some cases, UEs 164 and 182 can utilize beamforming on sidelink 160.

[0065] In the example of Figure 1, any UE shown (represented as a single UE 104 in Figure 1 for simplicity) can receive signal 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system, which UE 104 may use as a separate source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its location on or above the Earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such transmitters typically transmit signals marked with repeating virtual random noise (PN) codes using a set number of chips. While the transmitter is typically located in SV 112, it may sometimes be located at a ground-based control station, base station 102, and / or other UE 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 used to derive geographic location information from SV 112.

[0066] In a satellite positioning system, the use of signal 124 can be enhanced by various satellite-based augmentation systems (SBAS), which can be associated with or otherwise enabled to be used with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Satellite Coverage Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted geographic augmentation navigation, or GPS and Geographic Augmentation Navigation System (GAGAN), etc. Therefore, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with one or more such satellite positioning systems.

[0067] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). Within an NTN, SV 112 connects to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as the modified base station 102 (without a ground antenna) or network nodes in the 5GC. This element then provides access to other elements in the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. In this way, instead of receiving communication signals (e.g., signal 124) from or in addition to receiving communication signals from the ground base station 102, UE 104 may receive communication signals from SV 112.

[0068] The wireless communication system 100 may also include one or more UEs (such as UE 190) indirectly connected to one or more communication networks via one or more device-to-device (D2D) point-to-point (P2P) links (referred to as “sidelinks”). In the example of Figure 1, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., through D2D P2P link 192, UE 190 can indirectly obtain cellular connectivity) and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (through D2D P2P link 194, UE 190 can indirectly obtain WLAN-based internet connectivity). In one example, any known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.) can be used to support D2D P2P links 192 and 194.

[0069] Figure 2A illustrates an example wireless network architecture 200. For example, the 5GC 210 (also referred to as the "Next Generation Core (NGC)") can be functionally considered as a control plane (C-plane) functional unit 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) functional unit 212 (e.g., UE gateway functions, access to the data network, IP routing, etc.), with the control plane functional unit 214 and user plane functional unit 212 operating cooperatively to form the core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and more specifically, to the user plane functional unit 212 and the control plane functional unit 214, respectively. In another configuration, an ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane functional unit 214 and the NG-U 213 to the user plane functional unit 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both the ng-eNB 224 and the gNB 222. Either the gNB 222 or the ng-eNB 224 (or both) can communicate with one or more UEs 204 (e.g., any UE described herein).

[0070] 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 distributed 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 may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not shown). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0071] Figure 2B illustrates another example wireless network architecture 250. 5GC 260 (which may correspond to 5GC 210 in Figure 2A) can be functionally considered as a control plane function unit provided by Access and Mobility Management Function Unit (AMF) 264 and a user plane function unit provided by User Plane Function Unit (UPF) 262, which cooperate to form the core network (i.e., 5GC 260). The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transmission of conversation management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and conversation management function unit (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 unit (SMSF) (not shown), and security anchor function (SEAF). AMF 264 also interacts with the Authentication Server Functional Unit (AUSF) (not shown) and UE 204, and receives an intermediate key that is established as a result of the UE 204 authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, AMF 264 obtains security material from the AAUSF. AMF 264's functionality also includes Security Context Management (SCM). The SCM receives a key from the SEAF, which it uses to derive a network-specific key. AMF 264's functionality also includes location service management for management services, transmitting location service messages between UE 204 and the Location Management Functional Unit (LMF) 270 (which acts as a location server 230), transmitting location service messages between NG-RAN 220 and LMF 270, assigning EPS bearer identifiers for interoperability with the Evolved Packet System (EPS), and notifying UE 204 of mobility events. In addition, AMF 264 also supports functions for non-3GPP (3rd Generation Partnership Project) access networks.

[0072] 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) dialogue point interconnected to a data network (not shown), providing packet routing and forwarding, packet verification, user plane policy rule enforcement (e.g., gatening, redirection, traffic steering), lawful interception (user plane collection), traffic utilization reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reactive QoS marking in the downlink), uplink traffic verification (Service Data Stream (SDF) to QoS stream 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 can also support the transmission of location service messages on the user plane between UE 204 and a location server (such as SLP 272).

[0073] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic routing at UPF 262 to route traffic to the correct destination, control of policy implementation and QoS components, and downlink information notification. The interface on which SMF 266 communicates with AMF 264 is called the N11 interface.

[0074] 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 distributed across multiple physical servers, etc.), or alternatively, each can 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 shown). SLP 272 can support similar functions to LMF 270, but LMF 270 can communicate with AMF 264, NG-RAN 220 and UE 204 on the control plane (e.g., using interfaces and protocols designed to transmit signaling messages rather than voice or data), while SLP 272 can communicate with UE 204 and external clients (e.g., third-party server 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0075] Another optional aspect may include a third-party server 274, which can communicate with LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimation) of UE 204. Therefore, in some cases, the third-party server 274 may be referred to as a Location Service (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0076] User plane interface 263 and control plane interface 265 connect 5GC 260 (specifically, UPF 262 and AMF 264) to one or more gNB 222 and / or ng-eNB 224 in NG-RAN 220, respectively. The interface between gNB 222 and / or ng-eNB 224 and AMF 264 is referred to as the "N2" interface, and the interface between gNB 222 and / or ng-eNB 224 and UPF 262 is referred to as the "N3" interface. gNB 222 and / or ng-eNB 224 of NG-RAN 220 can communicate directly with each other via backhaul connection 223, referred to as the "Xn-C" interface. One or more of gNB 222 and / or ng-eNB 224 can communicate with one or more UEs 204 via a radio interface, referred to as the "Uu" interface.

[0077] The functions of the gNB 222 can be partitioned among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions such as transmitting user data, mobility control, radio access network sharing, location, and dialogue management, in addition to those functions specifically allocated to the gNB-DU 228. More specifically, the gNB-CU 226 typically controls the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically controls the Radio Link Control (RLC) and Media Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functions of gNB 222 are typically controlled by one or more independent gNB-RU 229s that perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Therefore, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0078] Figures 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) 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 functional unit described herein, including location server 230 and LMF 270, or alternatively may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in Figures 2A and 2B, such as a private network) to support file transfer operations as taught herein. It should be understood that these components can be implemented in different implementations (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.) in different types of devices. The components shown 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. Additionally, a given device may contain one or more of the components. For example, the apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

[0079] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, which provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for avoiding transmission, etc.) for communication via one or more wireless communication networks (not shown) (such as NR networks, LTE networks, GSM networks, etc.). WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 to communicate with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB)) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a set of time / frequency resources in a specific spectrum). WWAN transceivers 310 and 350 can be configured differently to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0080] In at least some cases, UE 302 and base station 304 each also include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for avoiding transmission, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) over a wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Z-Wave®, PC5, Dedicated Short-Range Communication (DSRC), Wireless Access in Vehicle Environments (WAVE), Near Field Communication (NFC), etc.). Short-range transceivers 320 and 360 can be configured differently to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, short-range transceivers 320 and 360 each include one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively, and each includes one or more receivers 322 and 322 for receiving and decoding signals 328 and 368, respectively. As a specific example, short-range wireless transceivers 320 and 360 can be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0081] In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, and can each provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378. When satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 can be 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. When satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 330 and 370 may each include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and operations from other systems as needed, and in at least some cases, perform calculations using measurements obtained through any suitable satellite positioning system algorithm to determine the positions of UE 302 and base station 304, respectively.

[0082] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide components (e.g., components for transmitting, components for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 can use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, network entity 306 can use one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links, or communicate with other network entities 306 through one or more wired or wireless core network interfaces.

[0083] A transceiver can be configured to communicate over a wired or wireless link. A transceiver (whether wired or wireless) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., the transmitter and receiver circuitry are embodied in a single device), in some implementations it may include separate transmitter and receiver circuitry, or in other implementations it may be embodied in other ways. The transmitter and receiver circuitry of a wired transceiver (e.g., in some implementations, network transceivers 380 and 390) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366) (such as antenna arrays), which allows corresponding devices (e.g., UE 302, base station 304) to perform transmit "beamforming" as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366) (such as antenna arrays), which allows corresponding devices (e.g., UE 302, base station 304) to perform receive beamforming as described herein. In one aspect, transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding devices can only receive or transmit at a given time, rather than simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

[0084] As used herein, various wireless transceivers (e.g., in some implementations, transceivers 310, 320, 350, and 360, and network transceivers 380 and 390) and wired transceivers (e.g., in some implementations, network transceivers 380 and 390) can generally be characterized as “transceiver,” “at least one transceiver,” or “one or more transceivers.” Therefore, it is possible to infer whether a particular transceiver is a wired or wireless transceiver based on the type of communication performed. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) typically involves signaling via a wireless transceiver.

[0085] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394 for providing, for example, wireless communication-related functions and for providing other processing functions. Thus, processors 332, 384, and 394 can provide components for processing, such as components for decision-making, components for calculation, components for receiving, components for transmitting, components for indicating, etc. In one aspect, processors 332, 384, and 394 may include, for example, one or more processors, such as one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0086] UE 302, base station 304, and network entity 306 each include memory circuitry that implements memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, components for retrieval, components for maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may each include positioning components 342, 388, and 398. Positioning components 342, 388, and 398 may be hardware circuitry that is part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functions described herein. In other respects, positioning components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., they may be 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 memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functions described herein. Figure 3A illustrates possible locations for positioning component 342, which may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B illustrates possible locations for positioning component 388, which may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C shows possible locations of the positioning component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394 or any combination thereof, or may be a standalone component.

[0087] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide components for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. For example, sensor 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, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate position in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

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

[0089] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functions targeting the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functions associated with: broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer PDUs, error detection via Automatic Repeat Request (ARQ), reordering, segmentation, and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, scheduling information reporting, error detection, priority handling, and logical channel prioritization.

[0090] Transmitter 354 and receiver 352 can implement Layer 1 (L1) functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) can include error detection on the transport channel, forward error detection (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to signal clusters 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 generate a physical channel for carrying the 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 scheme, as well as for spatial processing. The channel estimate can be derived from the reference signal 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 respective spatial stream to modulate the RF carrier for transmission.

[0091] At UE 302, receiver 312 receives signals through its respective antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides that information to one or more processors 332. Transmitter 314 and receiver 312 implement Layer 1 functions associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, receiver 312 can merge them 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 includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal clustering point transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. This data and control signals are then provided to one or more processors 332, which implement Layer 3 (L3) and Layer 2 (L2) functions.

[0092] In the uplink, one or more processors 332 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0093] Similar to the functions described in conjunction with downlink transmissions performed by base station 304, one or more processors 332 provide: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error detection via ARQ, reordering, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error detection via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel prioritization.

[0094] Transmitter 314 can use a channel estimate derived by a channel estimator based on a reference signal or feedback transmitted by base station 304 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by transmitter 314 can be provided to different antennas 316. Transmitter 314 can utilize its respective spatial stream to modulate the RF carrier for transmission.

[0095] At base station 304, uplink transmissions are handled in a manner similar to that described for the receiver functions integrated at UE 302. Receiver 352 receives signals through its respective antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides that information to one or more processors 384.

[0096] In the uplink, one or more processors 384 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the UE 302. IP packets from one or more processors 384 can be provided to the core network. One or more processors 384 are also responsible for error detection.

[0097] For convenience, UE 302, base station 304, and / or network entity 306 are shown in Figures 3A, 3B, and 3C as including various components that can be configured according to the various examples described herein. However, it will be understood that the components shown may have different functions in different designs. In particular, the various components in Figures 3A through 3C are optional in alternative configurations, and each aspect includes configurations that may vary due to design choices, cost, device usage, or other considerations. For example, in the case of Figure 3A, a particular implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device, tablet, PC, or laptop computer may have Wi-Fi and / or Bluetooth capabilities but not cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., cellular only, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in the case of Figure 3B, a particular implementation of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit short-range wireless transceiver 360 (e.g., cellular only), or may omit satellite receiver 370, and so on. For the sake of brevity, descriptions of various alternative configurations are not provided herein, but those skilled in the art will readily understand.

[0098] The various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form communication interfaces or portions thereof for UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are embodied in the same device (e.g., gNB and location server functions are incorporated into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between them.

[0099] The components of Figures 3A, 3B, and 3C can be implemented in various ways. In some implementations, the components of Figures 3A, 3B, and 3C can be implemented in one or more circuits, 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 the circuit to provide such functionality. For example, some or all of the functions represented by blocks 310 to 346 can be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by properly configuring the processor components). Similarly, some or all of the functions represented by blocks 350 to 388 can be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by properly configuring the processor components). Furthermore, some or all of the functions represented by blocks 390 to 398 can be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by properly configuring the processor components). For simplicity, this document describes various operations, actions, and / or functions as being performed "by the UE," "by the base station," "by the network entity," etc. However, it will be understood that such operations, actions, and / or functions can actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity, etc., such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memory 340, 386, and 396, positioning components 342, 388, and 398, etc.

[0100] In some designs, network entity 306 can be implemented as a core network component. In other designs, network entity 306 can operate differently from the network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, network entity 306 can be a component of a private network that can be configured to communicate with UE 302 via base station 304, or independently of base station 304 (e.g., on a non-cellular communication link such as WiFi).

[0101] NR supports a variety of location services and positioning technologies that have been developed across various versions of the 3GPP standard. In NR version 15, location services are limited to regulated services such as emergency calls and lawful interception. Additionally, version 15 introduces the concept of LMF (which corresponds to Enhanced Service Mobile Location Center (E-SMLC) in LTE). Positioning methods supported in version 15 include RAT-independent methods (such as Assisted Global Navigation Satellite System (A-GNSS), Urban Beacon System (MBS), Terrestrial Beacon System (TBS), motion sensors, WLAN, and Bluetooth) and RAT-related methods (such as LTE Observed Time Difference of Arrival (LTE-OTDOA) and LTE Enhanced Cell Identifier (E-CID)) as well as the NR cell ID method. Except for the NR cell ID, no other NR positioning methods are specified in version 15.

[0102] Version 16 of the NR standard supports location services for roaming and commercial use cases, including Mobile Terminal Location Request (MT-LR), Mobile Initial Location Request (MO-LR), and Delayed Location Request for periodic, triggered, and UE-available events. Version 16 also supports native 5G NR positioning methods, including Downlink Time Difference of Arrival (DL-TDOA), Downlink Transmit Angle (DL-AoD), Uplink Time Difference of Arrival (UL-TDOA), Uplink Angle of Arrival (UL-AoA), Round-Trip Time (RTT) with one or more neighboring base stations, and NR E-CID. Version 16 also introduces new downlink and uplink Positioning Reference Signals (PRS), broadcasting of auxiliary data, and GNSS enhancements (e.g., State Space Representation (SSR) for Precise Point Positioning (PPP) and Real-Time Kinematics (RTK).

[0103] RAT-related positioning methods in versions 15 and 16 are categorized as downlink-based, uplink-based, and downlink-and-uplink-based. Downlink-based positioning methods include LTE-OTDOA (or simply OTDOA), DL-TDOA, and DL-AoD. In an OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the times of arrival (ToA) of a received reference signal (e.g., a positioning reference signal (PRS)) from a base station (referred to as the Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurement) and reports them to the positioning entity. More specifically, the UE receives identifiers (IDs) 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 measurement, the positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.

[0104] For DL-AoD positioning, the positioning entity uses measurement reports from the UE regarding the received signal strength of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the UE's position based on the determined angle and the known location of the transmitting base station.

[0105] 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., sounding reference signals (SRS)) transmitted by the UE to multiple base stations. Specifically, the UE transmits one or more uplink reference signals measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the received-receive (Rx-Rx) time difference between the RTOA reported by the reference base station and the RTOA reported by each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use the TDOA to estimate the UE's location.

[0106] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive beams to determine the angle between the UE and the base stations. Based on the determined angle and the known location of the base stations, the positioning entity can then estimate the UE's location.

[0107] Downlink and uplink-based positioning methods include Enhanced Cell ID (E-CID) positioning and Multiple Round-Trip Time (RTT) positioning (also known as "Multi-Cell RTT" and "Multi-RTT"). In an RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., PRS or SRS) to a second entity (e.g., a UE or base station), and the second entity sends a second RTT-related signal (e.g., SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the receive-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest time slot boundaries of the received and transmitted signals. The two entities can then send their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip time (RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can send its Rx-Tx time difference measurement to another entity, which then calculates the RTT. The distance between the two entities can be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the determination of the first entity's location based on the distance to the second entities and the known location of the second entities (e.g., using multi-point positioning). RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy.

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

[0109] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) can 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 reference signal is measured, reference signal configuration parameters (e.g., including the number of consecutive time slots of the PRS, the period of consecutive time slots of the PRS, silence sequences, frequency hopping sequences, reference signal identifiers, reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, auxiliary data may be derived directly from the base station itself (e.g., in periodically broadcast burden messages, etc.). In some cases, the UE can detect neighboring network nodes itself without using auxiliary data.

[0110] In the case of OTDOA or DL-TDOA positioning procedures, auxiliary data may also include the expected RSTD value and the associated uncertainties or search windows surrounding the expected RSTD. In some cases, the expected RSTD value may range from + / - 500 microseconds (µs). In some cases, when any resources used for positioning measurements are in FR1, the expected RSTD uncertainty may range from + / - 32 µs. In other cases, when all resources used for positioning measurements are in FR2, the expected RSTD uncertainty may range from + / - 8 µs.

[0111] Location estimation can be referred to by other names, such as position estimate, location, position, position fix, fix, etc. A location estimate can be geodetic and include coordinates (e.g., latitude, longitude, and possible altitude), or it can be civil and include street addresses, postal addresses, or other verbal descriptions of the location. A location estimate can also be defined relative to another known location or in absolute terms (e.g., using latitude, longitude, and possible altitude). A location estimate can include anticipated errors or uncertainties (e.g., by including the area or volume within which the location is expected to be included at a specified or preset confidence level).

[0112] Figure 4 illustrates an example UE location operation 400 according to various aspects of this disclosure. The UE location operation 400 can be performed by UE 204, NG-RAN node 402 in NG-RAN 220 (e.g., gNB 222, gNB-CU 226, ng-eNB 224, or other nodes in NG-RAN 220), AMF 264, LMF 270, and 5GC Location Services (LCS) entity 480 (e.g., any third-party application requesting the location of UE 204, Public Service Access Point (PSAP), E-911 server, etc.).

[0113] A location service request to obtain the location of a target (i.e., UE 204) can be initiated by 5GC LCS entity 480, AMF 264 serving UE 204, or UE 204 itself. Figure 4 illustrates these options as stages 410a, 410b, and 410c, respectively. Specifically, at stage 410a, 5GC LCS entity 480 sends a location service request to AMF 264. Alternatively, at stage 410b, AMF 264 generates the location service request itself. Alternatively, at stage 410c, UE 204 sends a location service request to AMF 264.

[0114] Once AMF 264 has received (or generated) a location service request, it forwards the request to LMF 270 at stage 420. LMF 270 then performs an NG-RAN location procedure with NG-RAN node 402 at stage 430a and a UE location procedure with UE 204 at stage 430b. The specific NG-RAN and UE location procedures may depend on the type of location method used to locate UE 204, which may depend on the capabilities of UE 204. As mentioned above, the location method may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, DL-AoD, etc.), uplink-based (e.g., UL-TDOA, UL-AoA, etc.), and / or downlink and uplink-based (e.g., LTE / NR e-CID, multiple RTT, etc.). The corresponding location procedures are described in detail in 3GPP Technical Specification (TS) 38.305 (which is publicly available and incorporated herein by reference in its entirety).

[0115] NG-RAN and UE location procedures can utilize LTE Location Protocol (LPP) signaling between UE 204 and LMF 270, and LPP Type A (LPPa) or New Radio Location Protocol Type A (NRPPa) signaling between NG-RAN node 402 and LMF 270. LPP is used point-to-point between the location server (e.g., LMF 270) and the UE (e.g., UE 204) to obtain location-related measurements or location estimates, or to transmit ancillary data. A single LPP session is used to support a single location request (e.g., for a single Mobile Terminal Location Request (MT-LR), Mobile Initial Location Request (MO-LR), or Network-Induced Location Request (NI-LR)). Multiple LPP sessions can be used between the same endpoints to support multiple different location requests. Each LPP session includes one or more LPP transactions, where each LPP transaction performs a single operation (e.g., capability exchange, ancillary data transmission, location information transmission). An LPP transaction is called an LPP procedure.

[0116] The prerequisite for Phase 430 is that the LCS-related identifier (ID) and AMF ID have been passed to LMF 270 by the serving AMF 264. Both the LCS-related ID and AMF ID can be represented as strings chosen by AMF 264. AMF 264 provides the LCS-related ID and AMF ID to LMF 270 in the location service request at Phase 420. When LMF 270 then initiates Phase 430, LMF 270 also includes the LCS-related ID used for this location dialogue along with the AMF ID indicating the AMF instance serving UE 204. The LCS-related ID is used to ensure that during the location dialogue between LMF 270 and UE 204, location response messages from UE 204 are returned by AMF 264 to the correct LMF 270, carrying an indication (LCS-related ID) that can be recognized by LMF 270.

[0117] It should be noted that, as described in more detail in 3GPP TS 23.273 (which is publicly available and is incorporated herein by reference in its entirety), the LCS-related ID is used as a location dialogue identifier, which can be used to identify messages exchanged between AMF 264 and LMF 270 for a specific location dialogue for UE 204. As mentioned above and shown in phase 420, the location dialogue between AMF 264 and LMF 270 for a specific UE 204 is initiated by AMF 264, and the LCS-related ID can be used to identify the location dialogue (e.g., it can be used by AMF 264 to identify status information, etc., for that location dialogue).

[0118] The LPP positioning method and associated signaling content are defined in the 3GPP LPP standard (3GPP TS 37.355, which is publicly available and is incorporated herein by reference in its entirety). LPP signaling can be used to request and report measurements associated with the following positioning methods: LTE-OTDOA, DL-TDOA, A-GNSS, E-CID, sensors, TBS, WLAN, Bluetooth, DL-AoD, UL-AoA, and multiple RTT. Currently, LPP measurement reports may include the following measurements: (1) one or more ToA, TDOA, RSTD, or Rx-Tx time difference measurements, (2) one or more AoA and / or AoD measurements (currently only used by base stations to report UL-AoA and DL-AoD to LMF 270), (3) one or more multipath measurements (ToA, RSRP, AoA / AoD per path), (4) one or more motion states (e.g., walking, driving, etc.) and trajectories (currently only used by UE 204), and (5) one or more report quality indicators.

[0119] As part of the NG-RAN node localization procedure (phase 430a) and the UE localization procedure (phase 430b), LMF 270 can provide NG-RAN node 402 and UE 204 with LPP auxiliary information in the form of downlink localization reference signal (DL-PRS) configuration information for the selected localization method. Alternatively or additionally, NG-RAN node 402 can provide DL-PRS and / or uplink PRS (UL-PRS) configuration information to UE 204 for the selected localization method. Note that although Figure 4 shows a single NG-RAN node 402, multiple NG-RAN nodes 402 may be involved in the localization dialogue.

[0120] Once configured with DL-PRS and / or UL-PRS, NG-RAN node 402 and UE 204 send and receive / measure the corresponding PRS at scheduled times. Then, NG-RAN node 402 and UE 204 send their respective measurements to LMF 270. In some cases, NG-RAN node 402 can send its measurements to UE 204, which can then forward them to LMF 270 using LPP signaling. Alternatively, NG-RAN node 402 can send its measurements directly to LMF 270 using LPPa or NRPPa signaling. In some cases, UE 204 can send its measurements to NG-RAN node 402 using RRC, Uplink Control Information (UCI), or MAC Control Element (MAC-CE) signaling, and NG-RAN node 402 can forward the measurements to LMF 270 using LPPa or NRPPa signaling. Alternatively, UE 204 can send its measurements directly to LMF 270 using LPP signaling.

[0121] Once LMF 270 obtains measurements (depending on the type of positioning method) from UE 204 and / or NG-RAN node 402, it uses these measurements to calculate an estimate of UE 204's location. Then, at stage 440, LMF 270 sends a location service response, including the location estimate for UE 204, to AMF 264. AMF 264 then forwards the location service response to the entity that generated the location service request at stage 450. Specifically, if a location service request is received from 5GC LCS entity 480 at stage 410a, AMF 264 sends a location service response to 5GC LCS entity 480 at stage 450a. However, if a location service request is received from UE 204 at stage 410c, AMF 264 sends a location service response to UE 204 at stage 450c. Alternatively, if the AMF 264 generates a location service request at stage 410b, then at stage 450b, the AMF 264 stores / uses the location service response itself.

[0122] It should be noted that although the UE positioning operation 400 has been described for the foregoing as a UE-assisted positioning operation, it can alternatively be a UE-based positioning operation. A UE-assisted positioning operation is one in which the LMF 270 calculates the location of the UE 204, while a UE-based positioning operation is one in which the UE 204 calculates its own location. In the case of a UE-based positioning operation, phases 410c and 450c will be executed. The LMF 270 can still coordinate the transmission / measurement of DL-PRS (and possibly UL-PRS), but the measurements will be forwarded to the UE 204 instead of the LMF 270. Therefore, the location service response at phases 440 and 450c can be a measurement from the involved NG-RAN node 402, rather than a location estimate of the UE 204. Alternatively, if the involved NG-RAN node 402 (e.g., via RRC signaling) forwards its respective measurements directly to the UE 204, the location service response at phase 440 can simply be an acknowledgment that the NG-RAN node and UE positioning procedure at phase 430 has been completed.

[0123] As can be seen from the foregoing, the positioning operation typically includes the following main stages: (a) sending a location request to a location server (e.g., LMF 270), (b) providing DL-PRS and / or UL-PRS information for the positioning method to a UE (e.g., UE 204) and / or a base station (e.g., NG-RAN node 402), (c) scheduling measurements from the UE and / or the base station, (d) waiting for the DL-PRS and / or UL-PRS transmissions to be sent, (e) obtaining the DL-PRS (from the UE) and / or UL-PRS (from the base station) measurements, (f) sending the measurements to a location server (for UE-assisted) or a UE (for UE-based), (g) calculating a location estimate, and (h) sending the location estimate to a client (e.g., UE 204, AMF 264, or 5GC LCS entity 480).

[0124] One of the goals of NR location services is to reduce latency. The time delay before location measurement is completed (phases (a) to (d) above) can be referred to as “component A” latency. The delay in converting the location measurement into a location estimate and delivering the location estimate to the client (phases (e) to (h) above) can be referred to as “component B” latency. The very small latency of component B latency will allow the client to treat the location estimate as “current” because there is almost no time for location degradation due to the mobility of the target UE (e.g., UE 204).

[0125] As briefly noted above regarding stage 430 of Figure 4, a portion of the LPP location procedure is a capability report. Figure 5 illustrates an example LPP capability transfer procedure 500 according to various aspects of this disclosure. The LPP capability transfer procedure 500 is performed between a target 504 (e.g., any UE described herein) and a server 570 (e.g., location server 230, LMF 270, SLP 272). The target 504 and the server 570 communicate via LPP signaling.

[0126] At stage 510, server 570 sends an LPP request capability message to target 504. Server 570 may indicate the type of capability required. At stage 520, target 504 responds using an LPP provide capability message. These capabilities should correspond to any capability types specified in stage 510. The message should also include the LPP “endTransaction” parameter set to TRUE.

[0127] More specifically, upon receiving a capability request message, target 504 should generate an LPP capability provision message as a response. For each location method requested in the capability request message, if target 504 supports that location method, target 504 should include its capability for that supported location method in the LPP capability provision response message. Target 504 should also set the "LPP-TransactionID" parameter in the LPP capability provision response message to the same value as the "LPP-TransactionID" parameter in the received capability request message. Target 504 should then deliver the LPP capability provision response message to a lower layer for transmission to server 570.

[0128] Unlike the example in Figure 5, location capabilities can also be unrequested. Figure 6 illustrates an example LPP capability instruction 600 according to various aspects of this disclosure. The LPP capability instruction 600 is executed between a target 604 (e.g., any UE described herein) and a server 670 (e.g., location server 230, LMF 270, SLP 272). The target 604 and the server 670 communicate via LPP signaling. The LPP capability instruction 600 allows the target 604 to provide unrequested capabilities to the server 670.

[0129] At 610, target 604 sends an LPP provisioning capability message to server 670. This message should include the LPP “endTransaction” parameter set to TRUE. More specifically, when triggered to send the LPP provisioning capability message, target 604 should set the corresponding Information Element (IE) to include its capability for each location method to indicate its capability. If indicating OTDOA capability, target 604 should include the IE “supportedBandListEUTRA”. Target 604 should then deliver the LPP provisioning capability to the lower layer for transmission.

[0130] The location procedure typically begins with LPP capability exchange (such as LPP capability transmission procedure 500 or LPP capability indication procedure 600). Based on current assumptions, such a procedure can take 43 to 89 ms. To reduce latency, the capability exchange procedure can be avoided by storing the UE's location capabilities at the AMF (e.g., AMF 264) and / or location servers (e.g., location server 230, LMF 270, SLP 272). This provides the benefit of reducing initial location time latency, but will only apply to "static" (i.e., non-variable) location functions (i.e., UE functions that do not change over time or mobility).

[0131] Figure 7 illustrates an example capability storage procedure 700 according to various aspects of this disclosure. The capability storage procedure 700 can be executed by a UE 204 (e.g., any UE described herein), a gNB 702 (e.g., any base station described herein), an AMF 264, an LMF 270, and a gateway action location center (GMLC) 780.

[0132] If UE 204's location capabilities are expected to be preserved in the network, UE 204 can provide its capabilities as part of the first connection procedure or in a Tracking Area Update (TAU) message after a timer expires. (A tracking area is a cell group in which a UE in an RRC inactive state is expected to be located when transitioning to an RRC connected state.) Therefore, at 710, UE 204 (via gNB 702) sends a Non-Access Stratum (NAS) TAU message or Attachment Request to AMF 264 including UE 204's location capabilities.

[0133] At 720, AMF 264 stores the location capabilities of UE 204 for future location dialogues. At 730, AMF 264 receives a location service request from GMLC 780 (or other LCS entity), similar to phase 410a in Figure 4. At 740, AMF 264 sends a location service request, including the location capabilities stored by UE 204, to LMF 270, similar to phase 420 in Figure 4.

[0134] A drawback of storing a UE's positioning capabilities in the network (e.g., at the AMF) is that the UE may change its positioning capabilities over time for various reasons. One primary reason for potential changes in UE capabilities is that the UE may report certain capabilities based on its "current / active" configuration. For example, for SRS capabilities, the UE may have different capabilities for different frequency bands or based on configured frequency band combinations; however, the LMF is unaware of the frequency band / band combination the UE is currently utilizing. Another reason for potential changes in UE capabilities is power saving. For example, when a UE wants to save power, it can notify less PRS processing capacity. Yet another reason for potential changes in UE capabilities is due to the UE's carrier aggregation configuration and available hardware / memory resources. For example, if the UE is configured with high carrier aggregation (i.e., the maximum or near-maximum number of carriers the UE can aggregate), the UE may not have sufficient processing resources to perform both communication and positioning tasks. Another reason for potential changes in UE capabilities is due to dual connectivity and shared antennas. A further reason for potential changes in UE capabilities is user interaction. For example, if a user disables location services or a specific set of location services on the UE, the UE may not notify the network of any positioning capabilities.

[0135] This disclosure provides various techniques for storing UE capability information in a network, addressing the problem of variable (i.e., variable) UE capabilities. As a first technique, all reported capabilities can be stored; however, if the capability request is for a capability to be stored in the network (e.g., a non-variable capability to be stored at, for example, the AMF), the UE is allowed to send a different set of capability values. For example, the UE can receive a capability request to locate a capability to be stored in the network (e.g., an LPP request capability message, as shown at stage 510 in FIG5). The capability request can be received during network attachment or TAU procedures (as shown at 710 in FIG7) and may not necessarily be associated with the location procedure. The capability request may include a flag indicating that the location capability will be stored in the network (e.g., is non-variable).

[0136] In an alternative aspect, the capability request for a given location dialogue can instruct (e.g., via a flag) that the capability in the capability response (e.g., LPP provides capability information, as shown at stage 520 in FIG. 5) will be stored at the network (in addition to the capability used for the location dialogue). Alternatively, the UE can assume that any reported capability used for the location dialogue will be stored.

[0137] Regardless of whether the request for location capabilities is associated with a location dialogue, the UE can report two sets of location capabilities in one or more capability reports. One set can be stored in the network (e.g., non-variable capabilities), and the other set includes regular capability values ​​(e.g., variable capabilities). The UE can distinguish between these two sets of location capabilities using flags associated with at least one set of location capabilities. For example, the UE can send two LPP provision capability messages, one with a flag indicating that the reported location capabilities can be stored (e.g., because they are non-variable), and the other without a flag indicating that the reported location capabilities should not be stored (e.g., because they are variable). Alternatively, the LPP provision capability message without a flag can include location capabilities that can be stored.

[0138] In one aspect, the option to report different values ​​for the (non-variable) positioning capabilities to be stored and the regular positioning capabilities (variable) can be available for a feature group or a subset of capabilities. More specifically, NR defines multiple UE "feature groups" for NR-positioned UE "features". For example, there is a "common DL-PRS processing capability" feature group, which indicates the maximum DL PRS bandwidth (in MHz) supported and reported by the UE (FR1 band: {5, 10, 20, 40, 50, 80, 100}; FR2 band: {50, 100, 200, 400}), DL PRS buffering capability (type 1 – sub-slot / symbol level buffering; or type 2 – slot level buffering), and the duration (in ms) of the DL PRS symbol N that the UE can process per T milliseconds (assuming the UE supports and reports the maximum DL PRS bandwidth). PRS bandwidth (in MHz) (T: {8, 16, 20, 30, 40, 80, 160, 320, 640, 1280} ms, N: {0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50} ms), and the maximum number of DL PRS resources that the UE can process in its sub-slots (for each subcarrier spacing (SCS): 15 kHz, 30 kHz, 60 kHz, FR1 band: {1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64}); for each SCS: 60 kHz, 120 kHz, FR2 band: {1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64}). Another feature group is the "DL PRS Resources for DL-TDOA" feature group, which indicates the maximum number of DL PRS resource sets per TRP per frequency layer supported by the UE (value = {1,2}), the maximum number of TRPs spanning all positioning frequency layers for each UE (value = {4,6,12,16,24,32,64,128,256}), and the maximum number of positioning frequency layers supported by the UE (value = {1,2,3,4}). Yet another feature group is the "DL PRS Measurement Report for DL-TDOA" feature group, which indicates the DL RSTD measurement for each TRP pair (value = {1,2,3,4}) and whether the UE supports DL PRS-RSRP measurement (value = {0,1}). These and many other feature groups are defined in the NR, and the UE reports their specific values ​​in the LPP provisioning capability message.

[0139] Therefore, when reporting its capabilities for a specific set of features, the UE can indicate whether the reported values ​​can be stored (e.g., if they are immutable), or it can report two sets of values, one to be stored and the other to be used in the current location conversation (e.g., a variable capability). More specifically, the UE can include a flag for each feature set indicating whether the values ​​of that feature set can be stored. Alternatively, if the UE reports two values ​​(or sets of values) for a feature set, one of these values ​​(or sets of values) can be stored, and the other used in the current location conversation. Which set can be stored and which set can be used can be configured via applicable signaling or indicated in the applicable wireless communication standard. For example, it is possible that a first set of values ​​will be stored (because they are immutable), and a second set of values ​​will be used in the current location conversation (because they are variable).

[0140] In one aspect, when a feature group includes multiple parameters (e.g., in the "Public DL PRS Processing Capability" feature group), the UE can indicate that certain values ​​within the feature group can be stored, but others cannot. Alternatively, the UE can report the pending and normal values ​​for some parameters or all parameters within the feature group.

[0141] In one aspect, the UE can indicate whether location capabilities can be stored at the capability group level. That is, the UE can associate a flag with a capability group, and the flag can indicate whether all capabilities in that group can be stored.

[0142] In one aspect, the option to report different values ​​for stored (non-variable) positioning capabilities and regular (variable) positioning capabilities can be used for non-binary capabilities, while for binary capabilities (i.e., indications of whether the UE supports features), the UE may need to follow the reported capabilities for both types of capabilities. That is, if the UE indicates that it can support a specific set of features in the stored capabilities, then it should always be able to support that set of features. However, as mentioned above, the UE can support different values ​​within a set of features.

[0143] In one aspect, compared to the positioning capabilities that will be used for the current positioning conversation, the UE can report more conservative capability values ​​for positioning capabilities that will be stored in the network. For example, a conservative capability value can indicate the UE's positioning capabilities at any given time (i.e., invariant), while the capability value for the current positioning conversation can indicate the UE's current positioning capabilities (which are generally variable). For example, the UE can report that it can perform fewer PRS processing operations for capabilities to be stored compared to what the UE might report for a regular request for capabilities associated with a positioning conversation.

[0144] Regardless of whether the UE receives a request for stored capabilities as part of the positioning procedure, for subsequent positioning procedures, if the stored capabilities are sufficient for subsequent positioning procedures, no further capability exchange is required. However, if the stored capabilities are insufficient, the UE will need to perform another capability exchange (e.g., as shown in Figures 5 and 6). If the stored capabilities are sufficient and no further capability exchange is required, this technique will reduce the latency of the positioning conversation. However, the stored capabilities may not always be sufficient, as they will likely be more conservative than the UE's actual capabilities at a given time.

[0145] As a second technique for storing UE capability information in the network, the location capabilities to be stored in the network can be associated with time stamps or expiration timers. Such expiration timers can be used for the entire capability structure (i.e., all UE location capabilities), or different expiration timers may exist for different components or feature groups. When the timer expires, the associated capability will be discarded. For any subsequent location procedures that require these capabilities, the network will need to send a new capability request to the UE.

[0146] A timestamp can be any indication of when a capability report was generated, to indicate how recent or outdated the stored capability is. For example, a timestamp could be a system frame number (SFN) or other such timestamp. Alternatively, a timestamp could be an index that increments with each capability update. When a maximum value is reached, the index can wrap back (i.e., return to "0"). The index might be analogous to the packet sequence number used in upper layers to resolve out-of-order deliveries due to HARQ. In one aspect, separate indices could exist for different subsets (feature groups) of the UE's positioning capabilities, just as different timers could exist for different feature groups.

[0147] As a third technology for storing UE capability information in the network, standardized behavior for exchanging stored positioning capabilities between network nodes can exist. Specifically, a capability transfer message protocol can be defined for this purpose. Such capability transfer message transmission can be similar to LPP signaling, provided there are specific messages sent between the UE and the location server, between base stations and the location server, between base stations, etc. Then, appropriate capability transfer messages can be used to move the UE's positioning capabilities from one network node (e.g., gNB, AMF, LMF, LMF in the RAN, etc.) to another network node. In one aspect, if all positioning capabilities are stored at the location server (e.g., LMF), the procedure will be transparent to AMF changes (due to UE mobility). Alternatively, for UE mobility scenarios, all capabilities will be transferred from the UE's old LMF to its new LMF.

[0148] Figure 8 illustrates an example capability storage procedure 800 when the LMF of a UE changes due to mobility, according to various aspects of this disclosure. The capability storage procedure 800 can be executed by UE 204 (e.g., any UE described herein), gNB 802 (e.g., any base station described herein), AMF 264, first LMF 270-1 (e.g., LMF 270), second LMF 270-2 (e.g., LMF 270), and GMLC 880.

[0149] Operations 810 to 840 are the same as operations 710 to 740 in Figure 7. Specifically, if it is expected that the positioning capabilities of UE 204 will be preserved in the network (because they are invariant), UE 204 can provide its capabilities as part of the first connection procedure or in a TAU message after the timer expires. Therefore, at 810, UE 204 (via gNB 802) sends a NAS TAU message or attach request to AMF 264 including the (invariant) positioning capabilities of UE 204.

[0150] At 820, AMF 264 stores the location capabilities of UE 204 for future location sessions. At 830, AMF 264 receives a location service request from GMLC 880 (or other LCS entity), similar to phase 410a in Figure 4. At 850, AMF 264 sends a location service request, including the stored location capabilities of UE 204, to LMF 270-1, similar to phase 420 in Figure 4. At some point, during or after a location session, UE 204's LMF changes from LMF 270-1 to LMF 270-2. Therefore, AMF 264 sends a location service request, including the stored location capabilities of UE 204, to LMF 270-2.

[0151] As a fourth technology for storing UE capability information in the network, subsequent capability reports only report changes to capabilities. As a first option, the UE can send a regular capability report including location capabilities that are not allowed to be stored (i.e., a capability report including the UE's current or momentary / variable location capabilities). Subsequently, for location capabilities to be stored in the network (non-variable capabilities), the UE can send the difference between the reported capability value and the value of the capability to be stored. In one aspect, the UE can report these incremental values ​​for each feature group.

[0152] As a second option, the UE can send a regular capability report that includes location capabilities that are allowed to be stored in the network (i.e., non-variable capabilities). These will be the UE's long-term capabilities, which may be more conservative than its current or transient / variable capabilities. Subsequently, for the location capabilities that will be used for location dialogue, the UE can send the difference between the reported capability value and the value of the (variable) capability that will be used for location. In one aspect, the UE can report these incremental values ​​for each feature group.

[0153] Figure 9 illustrates an example method 900 of wireless communication according to various aspects of this disclosure. In one aspect, method 900 may be performed by a UE (e.g., any UE described herein).

[0154] At point 910, the UE sends one or more location capability reports to a location server (e.g., LMF 470, LMF 770, etc.), as shown at points 520 in Figure 5, 610 in Figure 6, and 710 in Figure 7. The one or more location capability reports may include a first set of values ​​for a set of location capability parameters and a second set of values ​​for the same set of location capability parameters. The first set of values ​​indicates the UE's variable location capabilities (e.g., network-stored capabilities, legacy capabilities, current capabilities, or capabilities for a single location session) as represented by the location capability parameter set, and the second set of values ​​indicates the UE's non-variable location capabilities as represented by the location capability parameter set. In one aspect, operation 910 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or location components 342, any one or all of which may be considered as components for performing the operation.

[0155] Figure 10 illustrates an example method 1000 for wireless communication according to various aspects of this disclosure. In one aspect, method 1000 may be performed by a network entity (e.g., base station, AMF, LMF, etc.).

[0156] At point 1010, the network entity receives one or more positioning capability reports from a UE (e.g., any UE described herein), as shown at points 520 in FIG5, 610 in FIG6, and 710 in FIG7. The one or more positioning capability reports may include a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the same set of positioning capability parameters, wherein the first set of values ​​indicates the UE's variable positioning capability as represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates the UE's non-variable positioning capability as represented by the set of positioning capability parameters. In one aspect, when the network entity is a base station, operation 1010 may be performed by one or more WWAN transceivers 350, one or more short-range wireless transceivers 360, one or more processors 384, memory 386, and / or positioning components 388, any one or all of which may be considered as components for performing the operation. Alternatively, operation 1010 may be performed by one or more network interfaces 390, one or more processors 394, memory 396, and / or positioning components 398, any one or all of which may be considered as components for performing the operation.

[0157] Figure 11 illustrates an example method 1100 for wireless communication according to various aspects of this disclosure. In one aspect, method 1100 may be performed by a first network entity (e.g., base station, AMF, LMF, etc.).

[0158] At 1110, the first network entity receives one or more positioning capability reports from a UE (e.g., any UE described herein), the one or more positioning capability reports including a set of values ​​for a set of positioning capability parameters, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE. In one aspect, where the first network entity is a base station, operation 1110 may be performed by one or more WWAN transceivers 350, one or more short-range wireless transceivers 360, one or more processors 384, memory 386, and / or positioning components 388, any one or all of which may be considered as components for performing the operation. Alternatively, operation 1110 may be performed by one or more network interfaces 390, one or more processors 394, memory 396, and / or positioning components 398, any one or all of which may be considered as components for performing the operation.

[0159] At 1120, the first network entity sends a set of values ​​to the second network entity (e.g., base station, AMF, LMF, etc.) via one or more capability transmission messages, enabling the second network entity to store the set of values ​​for subsequent positioning dialogue involving the UE. In one aspect, when the first network entity is a base station, operation 1120 may be performed by one or more WWAN transceivers 350, one or more short-range wireless transceivers 360, one or more processors 384, memory 386, and / or positioning components 388, any one or all of which may be considered as components for performing the operation. Alternatively, operation 1120 may be performed by one or more network interfaces 390, one or more processors 394, memory 396, and / or positioning components 398, any one or all of which may be considered as components for performing the operation.

[0160] Figure 12 illustrates an example method 1200 for wireless communication according to various aspects of this disclosure. In one aspect, method 1200 may be performed by a second network entity (e.g., base station, AMF, LMF, etc.).

[0161] In 1210, the second network entity receives a set of values ​​for a set of positioning capability parameters from one or more positioning capability reports from a user equipment (UE) via one or more capability transmission messages, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE. In one aspect, when the second network entity is a base station, operation 1210 may be performed by one or more WWAN transceivers 350, one or more short-range wireless transceivers 360, one or more processors 384, memory 386, and / or positioning components 388, any one or all of which may be considered as components for performing the operation. Alternatively, operation 1210 may be performed by one or more network interfaces 390, one or more processors 394, memory 396, and / or positioning components 398, any one or all of which may be considered as components for performing the operation.

[0162] Figure 13 illustrates an example method 1300 of wireless communication according to various aspects of this disclosure. In one aspect, method 1300 may be performed by a UE (e.g., any UE described herein).

[0163] At 1310, the UE sends one or more location capability reports to a location server (e.g., LMF 470, LMF 770, etc.), as shown at 520 in Figure 5, 610 in Figure 6, and 710 in Figure 7. The one or more location capability reports may include a set of values ​​for a set of location capability parameters, a set of values ​​stored by the network entity for subsequent location dialogues, and a set of values ​​associated with at least one time tag, at least one expiration timer, or both. In one aspect, operation 1310 may be performed by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, one or more processors 332, memory 340, and / or location components 342, any one or all of which may be considered as components for performing the operation.

[0164] Figure 14 illustrates an example method 1400 for wireless communication according to various aspects of this disclosure. In one aspect, method 1400 may be performed by a network entity (e.g., base station, AMF, LMF, etc.).

[0165] At 1410, the network entity receives one or more positioning capability reports from the UE (e.g., any UE described herein), as shown at 520 in FIG5, 610 in FIG6, and 710 in FIG7. The one or more positioning capability reports may include a set of values ​​for a set of positioning capability parameters, a set of values ​​stored by the network entity for subsequent positioning dialogues, and a set of values ​​associated with at least one timestamp, at least one expiration timer, or both. In one aspect, where the network entity is a base station, operation 1010 may be performed by one or more WWAN transceivers 350, one or more short-range wireless transceivers 360, one or more processors 384, memory 386, and / or positioning components 388, any one or all of which may be considered as components for performing the operation. Alternatively, operation 1010 may be performed by one or more network interfaces 390, one or more processors 394, memory 396, and / or positioning components 398, any one or all of which may be considered as components for performing the operation.

[0166] As will be understood, the technical advantage of methods 900 to 1400 is reduced positioning latency (due to the network storage of UE capability parameters) while allowing the UE to remain flexible in adapting its positioning capabilities across time.

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

[0168] Implementation examples are described in the following numbered clauses:

[0169] Clause 1. A method of wireless communication performed by a user equipment (UE), comprising: sending one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a first positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a positioning capability of the UE represented by the set of positioning capability parameters to be stored by a network entity for subsequent positioning dialogue.

[0170] Clause 2. The method according to Clause 1 further includes: receiving a positioning capability request from the location server, the positioning capability request indicating the set of positioning capability parameters.

[0171] Clause 3. The method according to Clause 2, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by the network entity.

[0172] Clause 4. The method according to Clause 3, wherein the UE, in response to the positioning capability request including the flag, sends one or more positioning capability reports including the first set of values ​​and the second set of values.

[0173] Clause 5. The method according to any one of Clauses 1 to 4, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by the network entity for subsequent positioning dialogue.

[0174] Clause 6. The method according to any one of Clauses 1 to 5, wherein the second set of values ​​is a subset of the values ​​of the positioning capability parameter set.

[0175] Clause 7. The method according to Clause 6, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by the network entity for subsequent location dialogue.

[0176] Clause 8. The method according to any one of Clauses 6 to 7, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0177] Clause 9. The method according to any one of Clauses 1 to 8, wherein one or more capabilities in the set of positioning capabilities are binary capabilities.

[0178] Clause 10, the method according to Clause 9, wherein the first set of values ​​and the second set of values ​​each include different values ​​of the one or more capabilities.

[0179] Clause 11, the method according to Clause 9, wherein the first set of values ​​and the second set of values ​​each include the same value of the one or more capabilities.

[0180] Clause 12. The method according to any one of Clauses 1 to 11, wherein: the first set of values ​​represents the positioning capability that the UE can only provide for a limited time, and the second set of values ​​represents the positioning capability that the UE can always provide.

[0181] Clause 13. The method according to any one of Clauses 1 to 12, wherein the second set of values ​​is the difference relative to the first set of values.

[0182] Clause 14. The method according to any one of Clauses 1 to 12, wherein the first set of values ​​is the difference relative to the second set of values.

[0183] Clause 15. The method according to any one of Clauses 1 to 14, wherein the network entity is an Access and Mobility Management Function Unit (AMF).

[0184] Clause 16. A method of wireless communication performed by a network entity includes: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a first location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a location capability of the UE represented by the set of location capability parameters to be stored by the network entity for subsequent location dialogue.

[0185] Clause 17. The method according to Clause 16, wherein the network entity is a location server, the method further comprising: sending a location capability request to the UE, the location capability request indicating the location capability parameter set.

[0186] Clause 18. The method according to Clause 17, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by the network entity.

[0187] Clause 19. The method according to any one of Clauses 16 to 18, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by the network entity for subsequent positioning dialogue.

[0188] Clause 20. The method according to any one of Clauses 16 to 19, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0189] Clause 21. The method according to Clause 20, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by the network entity for subsequent location dialogue.

[0190] Clause 22. The method according to any one of Clauses 20 to 21, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0191] Clause 23. The method according to any one of Clauses 20 to 22, wherein one or more capabilities in the set of positioning capabilities are binary capabilities.

[0192] Clause 24. The method according to Clause 23, wherein the first set of values ​​and the second set of values ​​each include different values ​​of the one or more capabilities.

[0193] Clause 25. The method according to Clause 23, wherein the first set of values ​​and the second set of values ​​each include the same value of the one or more capabilities.

[0194] Clause 26. The method according to any one of Clauses 16 to 25, wherein: the first set of values ​​represents the positioning capability that the UE can only provide for a limited time, and the second set of values ​​represents the positioning capability that the UE can always provide.

[0195] Clause 27. The method according to any one of Clauses 16 to 26, wherein the second set of values ​​is the difference relative to the first set of values.

[0196] Clause 28. The method according to any one of Clauses 16 to 26, wherein the first set of values ​​is the difference relative to the second set of values.

[0197] Clause 29. The method according to any one of Clauses 16 to 28, wherein the network entity is an Access and Mobility Management Function Unit (AMF).

[0198] Clause 30. A method of wireless communication performed by a user equipment (UE), comprising: sending one or more location capability reports to a location server, the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​will be stored by a network entity for subsequent location dialogue, and wherein the set of values ​​is associated with at least one time tag, at least one expiration timer, or both.

[0199] Clause 31, the method according to Clause 30, wherein the at least one time tag is at least one index representing the sequence number of the one or more location capability reports.

[0200] Clause 32, the method according to Clause 31, wherein the at least one index increments with each subsequent location capability report transmission.

[0201] Clause 33, the method according to Clause 32, wherein the at least one index returns zero when the maximum value is reached.

[0202] Clause 34. The method according to Clause 30, wherein the at least one timestamp is a timestamp.

[0203] Clause 35. The method according to any one of Clauses 30 to 34, wherein the at least one expiration timer indicates a period of time during which the set of values ​​is valid.

[0204] Clause 36. The method according to any one of Clauses 30 to 35, wherein the at least one time tag, the at least one expiration timer, or both, includes a time tag, an expiration timer, or both for each value in the set of values.

[0205] Clause 37. The method according to any one of Clauses 30 to 36, wherein: the set of values ​​includes multiple sets of values ​​of the set of positioning capability parameters, and the at least one time tag, the at least one expiration timer, or both include a time tag, an expiration timer, or both for each of the multiple sets of values.

[0206] Clause 38. The method according to any one of Clauses 30 to 37, wherein the network entity is an Access and Mobility Management Function Unit (AMF).

[0207] Clause 39. The method according to any one of Clauses 30 to 38 further includes: receiving a positioning capability request from the location server, the positioning capability request indicating the set of positioning capability parameters.

[0208] Clause 40. A method of wireless communication performed by a network entity, comprising: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​will be stored by the network entity for subsequent location dialogue, and wherein the set of values ​​is associated with at least one time tag, at least one expiration timer, or both.

[0209] Clause 41, the method according to Clause 40, wherein the at least one time tag is at least one index representing the sequence number of the one or more location capability reports.

[0210] Clause 42, the method according to Clause 41, wherein the at least one index increments with each subsequent location capability report transmission.

[0211] Clause 43. The method according to Clause 42, wherein the at least one index returns zero when the maximum value is reached.

[0212] Clause 44. The method according to Clause 40, wherein the at least one timestamp is a timestamp.

[0213] Clause 45. The method according to any one of Clauses 40 to 44, wherein the at least one expiration timer indicates a period of time during which the set of values ​​is valid.

[0214] Clause 46. The method according to any one of Clauses 40 to 45, wherein the at least one time tag, the at least one expiration timer, or both comprise a time tag, an expiration timer, or both for each value in the set of values.

[0215] Clause 47. The method according to any one of Clauses 40 to 46, wherein: the set of values ​​includes multiple sets of values ​​of the set of positioning capability parameters, and the at least one time tag, the at least one expiration timer, or both include a time tag, an expiration timer, or both for each of the multiple sets of values.

[0216] Clause 48. The method according to any one of Clauses 40 to 47, wherein the network entity is an Access and Mobility Management Function Unit (AMF).

[0217] Clause 49. The method according to any one of Clauses 40 to 48 further includes: discarding the set of values ​​of the positioning capability parameter set when the at least one expiration timer expires.

[0218] Clause 50, the method according to Clause 49, further includes: sending a location capability request to the UE in response to the expiration of the at least one expiration timer, the location capability request indicating the set of location capability parameters.

[0219] Clause 51. A method of wireless communication performed by a first network entity, comprising: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​will be stored for subsequent location dialogue; and transmitting the set of values ​​to a second network entity via one or more capability transmission messages.

[0220] Clause 52, the method described in Clause 51, wherein the first network entity is the Access and Mobility Management Function Unit (AMF).

[0221] Clause 53, the method described in Clause 52, wherein the second network entity is a first location server.

[0222] Clause 54. The method according to Clause 53 further includes: sending the set of values ​​to the second location server via one or more capability transmission messages based on the UE switching from the first location server to the second location server due to the mobility of the UE.

[0223] Clause 55. The method according to Clause 51, wherein: the first network entity is a first base station, a first AMF, or a first location management function unit (LMF), and the second network entity is a second base station, a second AMF, or a second LMF.

[0224] Clause 56. An apparatus comprising: a memory and at least one processor communicatively coupled to the memory, the memory and the at least one processor being configured to perform a method according to any one of Clauses 1 to 55.

[0225] Clause 57. An apparatus comprising a component for performing the method according to any one of Clauses 1 to 55.

[0226] Clause 58. A non-transitory computer-readable medium storing computer-executable instructions, said 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 55.

[0227] Additional implementation examples are described in the following numbered clauses:

[0228] Clause 1. A method of wireless communication performed by a user equipment (UE), comprising: sending one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0229] Clause 2. The method according to Clause 1 further includes: receiving a positioning capability request from the location server, the positioning capability request indicating the set of positioning capability parameters.

[0230] Clause 3. The method described in Clause 2, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by a network entity.

[0231] Clause 4. The method according to Clause 3, wherein the one or more location capability reports including the first set of values ​​and the second set of values ​​are sent in response to the location capability request including the flag.

[0232] Clause 5. The method according to any one of Clauses 1 to 4, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by the network entity for subsequent positioning dialogue.

[0233] Clause 6. The method according to any one of Clauses 1 to 5, wherein the second set of values ​​is a subset of the values ​​of the positioning capability parameter set.

[0234] Clause 7. The method according to Clause 6, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a network entity for subsequent location dialogue.

[0235] Clause 8. The method according to any one of Clauses 6 to 7, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0236] Clause 9. The method according to any one of Clauses 1 to 8, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability is a positioning capability that the UE can always provide.

[0237] Clause 10. The method according to any one of Clauses 1 to 9, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0238] Clause 11. The method according to any one of Clauses 1 to 10, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0239] Clause 12. A method of wireless communication performed by a network entity includes: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0240] Clause 13. The method according to Clause 12, wherein the network entity is a location server, the method further comprising: sending a location capability request to the UE, the location capability request indicating the location capability parameter set.

[0241] Clause 14. The method according to Clause 13, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by a second network entity.

[0242] Clause 15. The method according to any one of Clauses 12 to 14, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by the second network entity for subsequent positioning dialogue.

[0243] Clause 16. The method according to any one of Clauses 12 to 15, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0244] Clause 17. The method according to Clause 16, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a second network entity for subsequent location dialogue.

[0245] Clause 18. The method according to any one of Clauses 16 to 17, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0246] Clause 19. The method according to any one of Clauses 12 to 18, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability represents a positioning capability that the UE can always provide.

[0247] Clause 20. The method according to any one of Clauses 12 to 19, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0248] Clause 21. The method according to any one of Clauses 12 to 20, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0249] Clause 22. A method of wireless communication performed by a first network entity includes: receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and transmitting the set of values ​​to a second network entity via one or more capability transmission messages to enable the second network entity to store the set of values ​​for use in subsequent location dialogues involving the UE.

[0250] Clause 23, the method according to Clause 22, wherein: the first network entity is an Access and Mobility Management Function (AMF), and the second network entity is a first location server.

[0251] Clause 24. The method according to Clause 23 further includes: sending the set of values ​​to the second location server via one or more capability transmission messages based on the UE switching from the first location server to the second location server due to the mobility of the UE.

[0252] Clause 25. The method described in Clause 22, wherein: the first network entity is a Location Management Function (LMF), and the second network entity is an AMF.

[0253] Clause 26. A method of wireless communication performed by a second network entity includes: receiving, via one or more capability transmission messages, a set of values ​​for a set of positioning capability parameters from a user equipment (UE) in one or more positioning capability reports, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE.

[0254] Clause 27. The method according to Clause 26, wherein: the first network entity is a Location Management Function Unit (LMF), and the second network entity is an Access and Mobility Management Function Unit (AMF).

[0255] Clause 28. 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: transmit one or more positioning capability reports to a location server via the at least one transceiver, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0256] Clause 29. The UE according to Clause 28, wherein the at least one processor is further configured to: receive a location capability request from the location server via the at least one transceiver, the location capability request indicating the set of location capability parameters.

[0257] Clause 30, the UE as described in Clause 29, wherein the positioning capability request includes a flag indicating that the value of the positioning capability parameter set will be stored by a network entity.

[0258] Clause 31, the UE as described in Clause 30, wherein the one or more positioning capability reports including the first set of values ​​and the second set of values ​​are sent in response to the positioning capability request including the flag.

[0259] Clause 32. A UE pursuant to any one of Clauses 28 to 31, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by the network entity for subsequent positioning dialogue.

[0260] Clause 33. A UE pursuant to any one of Clauses 28 to 32, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0261] Clause 34, the UE as described in Clause 33, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a network entity for subsequent location dialogue.

[0262] Clause 35. A UE pursuant to any one of Clauses 33 to 34, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0263] Clause 36. A UE pursuant to any one of Clauses 28 to 35, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability is a positioning capability that the UE can always provide.

[0264] Clause 37. A UE pursuant to any one of Clauses 28 to 36, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0265] Clause 38. A UE pursuant to any one of Clauses 28 to 37, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0266] Clause 39. A network entity 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 one or more location capability reports from a user equipment (UE) via the at least one transceiver, the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0267] Clause 40, the network entity as described in Clause 39, wherein the network entity is a location server, and the at least one processor is further configured to: send a location capability request to the UE via the at least one transceiver, the location capability request indicating the set of location capability parameters.

[0268] Clause 41. The network entity as described in Clause 40, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by a second network entity.

[0269] Clause 42. A network entity pursuant to any one of Clauses 39 to 41, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by the second network entity for subsequent positioning dialogue.

[0270] Clause 43. A network entity pursuant to any one of Clauses 39 to 42, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0271] Clause 44. A network entity as described in Clause 43, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a second network entity for subsequent location dialogue.

[0272] Clause 45. A network entity pursuant to any one of Clauses 43 to 44, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0273] Clause 46. A network entity pursuant to any one of Clauses 39 to 45, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability represents a positioning capability that the UE can always provide.

[0274] Clause 47. A network entity pursuant to any one of Clauses 39 to 46, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0275] Clause 48. A network entity pursuant to any one of Clauses 39 to 47, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0276] Clause 49. A first network entity 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 one or more location capability reports from a user equipment (UE) via the at least one transceiver, the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and transmit the set of values ​​to a second network entity via one or more capability transmission messages via the at least one transceiver, such that the second network entity is able to store the set of values ​​for subsequent location dialogues involving the UE.

[0277] Clause 50, the first network entity as described in Clause 49, wherein: the first network entity is an Access and Mobility Management Function (AMF), and the second network entity is a first location server.

[0278] Clause 51, the first network entity as described in Clause 50, wherein the at least one processor is further configured to: transmit the set of values ​​to the second location server via one or more capabilities, based on the UE switching from the first location server to the second location server due to the mobility of the UE.

[0279] Clause 52, the first network entity as described in Clause 49, wherein: the first network entity is a Location Management Function (LMF), and the second network entity is an AMF.

[0280] Clause 53. A second network entity, 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, via the at least one transceiver, a set of values ​​for a set of positioning capability parameters from a user equipment (UE) via one or more capability transmission messages from the first network entity, wherein the set of values ​​is invariant for subsequent positioning dialogues involving the UE.

[0281] Clause 54. The second network entity as described in Clause 53, wherein: the first network entity is a Location Management Function Unit (LMF), and the second network entity is an Access and Mobility Management Function Unit (AMF).

[0282] Clause 55. A user equipment (UE) includes: means for sending one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0283] Clause 56. The UE according to Clause 55 further includes: a component for receiving a positioning capability request from the location server, the positioning capability request indicating the set of positioning capability parameters.

[0284] Clause 57. The UE as described in Clause 56, wherein the positioning capability request includes a flag indicating that the value of the positioning capability parameter set will be stored by a network entity.

[0285] Clause 58, the UE as described in Clause 57, wherein the one or more positioning capability reports including the first set of values ​​and the second set of values ​​are sent in response to the positioning capability request including the flag.

[0286] Clause 59. A UE pursuant to any one of Clauses 55 to 58, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by a network entity for subsequent positioning dialogue.

[0287] Clause 60. A UE pursuant to any one of Clauses 55 to 59, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0288] Clause 61, the UE as described in Clause 60, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a network entity for subsequent location dialogue.

[0289] Clause 62. The UE according to any one of Clauses 60 to 61, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0290] Clause 63. A UE pursuant to any one of Clauses 55 to 62, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability is a positioning capability that the UE can always provide.

[0291] Clause 64. A UE pursuant to any one of Clauses 55 to 63, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0292] Clause 65. A UE pursuant to any one of Clauses 55 to 64, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0293] Clause 66. A network entity comprising: means for receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0294] Clause 67. A network entity as described in Clause 39, wherein the network entity is a location server, and the network entity further includes: a component for sending a location capability request to the UE, the location capability request indicating the location capability parameter set.

[0295] Clause 68. A network entity as described in Clause 67, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by a second network entity.

[0296] Clause 69. A network entity pursuant to any one of Clauses 66 to 68, wherein the one or more location capability reports include a flag indicating that the second set of values ​​indicates the location capability of the UE, represented by the set of location capability parameters, to be stored by the second network entity for subsequent location dialogue.

[0297] Clause 70. A network entity pursuant to any one of Clauses 66 to 69, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0298] Clause 71, the network entity as described in Clause 70, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a second network entity for subsequent location dialogue.

[0299] Clause 72. A network entity pursuant to any one of Clauses 70 to 71, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0300] Clause 73. A network entity pursuant to any one of Clauses 66 to 72, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability represents a positioning capability that the UE can always provide.

[0301] Clause 74. A network entity pursuant to any one of Clauses 66 to 73, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0302] Clause 75. A network entity pursuant to any one of Clauses 66 to 74, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0303] Clause 76. A first network entity comprising: means for receiving one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and means for transmitting the set of values ​​to a second network entity via one or more capability transmission messages to enable the second network entity to store the set of values ​​for subsequent location dialogues involving the UE.

[0304] Clause 77, the first network entity as described in Clause 76, wherein: the first network entity is an Access and Mobility Management Function (AMF), and the second network entity is a first location server.

[0305] Clause 78. The first network entity as described in Clause 50 further includes: a component for transmitting the set of values ​​to the second location server via one or more capability transmission messages based on the UE switching from the first location server to the second location server due to the mobility of the UE.

[0306] Clause 79. The first network entity as described in Clause 76, wherein: the first network entity is a Location Management Function (LMF), and the second network entity is an AMF.

[0307] Clause 80. A second network entity comprising: a set of values ​​for a set of positioning capability parameters from a user equipment (UE) for receiving, via one or more capability transmission messages, a set of values ​​from a first network entity, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE.

[0308] Clause 81. The second network entity as described in Clause 80, wherein: the first network entity is a Location Management Function Unit (LMF), and the second network entity is an Access and Mobility Management Function Unit (AMF).

[0309] Clause 82. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: send one or more positioning capability reports to a location server, the one or more positioning capability reports including a first set of values ​​for a set of positioning capability parameters and a second set of values ​​for the set of positioning capability parameters, wherein the first set of values ​​indicates a variable positioning capability of the UE represented by the set of positioning capability parameters, and wherein the second set of values ​​indicates a non-variable positioning capability of the UE represented by the set of positioning capability parameters.

[0310] Clause 83. The non-transitory computer-readable medium according to Clause 82 further includes, when executed by the UE, computer-executable instructions that cause the UE to: receive a location capability request from the location server, the location capability request indicating the set of location capability parameters.

[0311] Clause 84. The non-transitory computer-readable medium as described in Clause 83, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by a network entity.

[0312] Clause 85, the non-transitory computer-readable medium as described in Clause 84, wherein the one or more location capability reports including the first set of values ​​and the second set of values ​​are sent in response to the location capability request including the flag.

[0313] Clause 86. A non-transitory computer-readable medium pursuant to any one of Clauses 82 to 85, wherein the one or more location capability reports include a flag indicating that the second set of values ​​indicates the location capability of the UE, represented by the set of location capability parameters, to be stored by a network entity for subsequent location dialogue.

[0314] Clause 87. A non-transitory computer-readable medium pursuant to any one of Clauses 82 to 86, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0315] Clause 88, the non-transitory computer-readable medium as described in Clause 87, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a network entity for subsequent location dialogue.

[0316] Clause 89. A non-transitory computer-readable medium pursuant to any one of Clauses 87 to 88, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0317] Clause 90. A non-transitory computer-readable medium pursuant to any one of Clauses 82 to 89, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability is a positioning capability that the UE can always provide.

[0318] Clause 91. A non-transitory computer-readable medium pursuant to any one of Clauses 82 to 90, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0319] Clause 92. A non-transitory computer-readable medium pursuant to any one of Clauses 82 to 91, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0320] Clause 93. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a network entity, cause the network entity to: receive one or more location capability reports from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates a variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates a non-variable location capability of the UE represented by the set of location capability parameters.

[0321] Clause 94. The non-transitory computer-readable medium according to Clause 93, wherein the network entity is a location server, the non-transitory computer-readable medium further includes, when executed by the first network entity, computer-executable instructions causing the first network entity to perform the following operation: send a location capability request to the UE, the location capability request indicating the set of location capability parameters.

[0322] Clause 95, the non-transitory computer-readable medium as described in Clause 94, wherein the location capability request includes a flag indicating that the value of the location capability parameter set will be stored by a second network entity.

[0323] Clause 96. A non-transitory computer-readable medium pursuant to any one of Clauses 93 to 95, wherein the one or more positioning capability reports include a flag indicating that the second set of values ​​indicates the positioning capability of the UE, represented by the set of positioning capability parameters, to be stored by the second network entity for subsequent positioning dialogue.

[0324] Clause 97. A non-transitory computer-readable medium pursuant to any one of Clauses 93 to 96, wherein the second set of values ​​is a subset of the values ​​of the set of positioning capability parameters.

[0325] Clause 98, the non-transitory computer-readable medium as described in Clause 97, wherein each value in the subset of values ​​is associated with a flag indicating that the value will be stored by a second network entity for subsequent location dialogue.

[0326] Clause 99. A non-transitory computer-readable medium pursuant to any one of Clauses 97 to 98, wherein the first set of values ​​is a distinct set of values ​​of the subset of values ​​of the set of positioning capability parameters.

[0327] Clause 100, a non-transitory computer-readable medium pursuant to any one of Clauses 93 to 99, wherein: the variable positioning capability is a positioning capability that the UE can only provide for a limited time, and the non-variable positioning capability represents a positioning capability that the UE can always provide.

[0328] Clause 101, a non-transitory computer-readable medium pursuant to any one of Clauses 93 to 100, wherein: the second set of values ​​is a difference relative to the first set of values, or the first set of values ​​is a difference relative to the second set of values.

[0329] Clause 102, a non-transitory computer-readable medium according to any one of Clauses 93 to 101, wherein the non-variable positioning capability of the UE, represented by the set of positioning capability parameters, is stored by the Access and Mobility Management Function (AMF).

[0330] Clause 103. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a first network entity, cause the first network entity to: receive one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and transmit the set of values ​​to a second network entity via one or more capability transmission messages, such that the second network entity can store the set of values ​​for use in subsequent location dialogues involving the UE.

[0331] Clause 104, the non-transitory computer-readable medium as described in Clause 103, wherein: the first network entity is an Access and Mobility Management Function (AMF), and the second network entity is a first location server.

[0332] Clause 105, the non-transitory computer-readable medium as described in Clause 104, further includes computer-executable instructions that, when executed by the first network entity, cause the first network entity to: send the set of values ​​to the second location server based on the UE switching from the first location server to the second location server due to the mobility of the UE.

[0333] Clause 106, the non-transitory computer-readable medium as described in Clause 103, wherein: the first network entity is a Location Management Function (LMF), and the second network entity is an AMF.

[0334] Clause 107. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a second network entity, cause the second network entity to: receive a set of values ​​for a set of positioning capability parameters from a user equipment (UE) via one or more capability transmission messages, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE.

[0335] Clause 108, Non-transitory computer-readable media as described in Clause 107, wherein: the first network entity is a Location Management Function (LMF), and the second network entity is an Access and Mobility Management Function (AMF).

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

[0337] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction 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, they have been generally described above in terms of the functionality of the various illustrative components, blocks, modules, circuits, and steps. 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 can implement the described functionality in alternative ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure.

[0338] 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, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0339] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein can be directly embodied in hardware, in a software module executed by a processor, or a combination of both. The software module can reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electronically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage media known in the art. Example storage media can be coupled to a processor so that the processor can read information from and write information to the storage media. Alternatively, the storage media can be a component of the processor. The processor and storage media can reside in an ASIC. The ASIC can reside in a user terminal (e.g., a UE). Alternatively, the processor and storage media can be discrete components within a user equipment.

[0340] In one or more example aspects, the described functionality can be implemented using hardware, software, firmware, or any combination thereof. If implemented in software, the functionality can be stored as one or more instructions or codes on or transmitted through a computer-readable medium. A computer-readable medium can include both computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of computer programs from one place to another. A storage medium can be any available media accessible to a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is delivered from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) are included in the definition of media. As used herein, magnetic disks and optical disks include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks typically copy data magnetically, while optical discs use lasers to optically copy data. Combinations of the above should also be included within the scope of computer-readable media.

[0341] While the foregoing disclosure illustrates aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. The steps and / or actions of the method claims according to the aspects of the 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, plural forms are contemplated unless expressly stated to be limited to the singular.

[0342] 100: Wireless Communication System 102:Base station 102': Small-scale community base station 104: User Equipment (UE) 110: Geographical coverage area 110': Geographical coverage area 112: Space Vehicle (SV) 120: Communication Link 122: Backhaul Link 124: Signal 128: Direct connection 134: Backhaul Link 150: Wireless Local Area Network (WLAN) Access Point (AP) 152: WLAN Station (STA) 154: Communication Link 160: Side Link 164:UE 170: Core Network 172: Location Server 180: Millimeter wave (mmW) base station 182:UE 184:mmW communication link 190:UE 192: Device-to-device (D2D) and peer-to-peer (P2P) links 194: D2D P2P Link 200: Wireless Network Architecture 204:UE 210: 5G core (5GC) 212: User Plane Functional Unit 213: User-defined interface (NG-U) 214: Control Plane Functional Unit 215: Control Plane Interface (NG-C) 220: Next-Generation RAN (NG-RAN) 222: New Radio (NR)B Node (gNB) 223: Return Connection 224: Next-Generation Evolved B-Node (ng-eNB) 226: gNB Central Unit (gNB-CU) 228: gNB Distributed Unit (gNB-DU) 229: gNB Radio Unit (gNB-RU) 230: Location Server 232: Interface 250: Wireless Network Structure 260:5GC 262: User Plane Functional Unit (UPF) 263: User Interface 264: Access and Mobility Management Functional Unit (AMF) 265: Control Plane Interface 266: Dialogue Management Function Unit (SMF) 270: Location Management Function (LMF) 270-1: First LMF 270-2: Second LMF 272: Secure User Plane Positioning (SUPL) Platform (SLP) 274: Third-party servers 302:UE 304:Base station 306: Network Entity 310: Wireless Wide Area Network (WWAN) Transceiver 312: Receiver 314: Transmitter 316: Antenna 318: Signal 320: Short-range wireless transceiver 322: Receiver 324: Transmitter 326: Antenna 328: Signal 330: Satellite signal receiver 332: Processor 334: Data Bus 336: Antenna 338: Satellite positioning / communication signals 340: Memory 342: Positioning component 344: Sensor 346: User Interface 350: WWAN transceiver 352: Receiver 354: Transmitter 356: Antenna 358: Signal 360: Short-range wireless transceiver 362: Receiver 364: Transmitter 366: Antenna 368: Signal 370: Satellite signal receiver 376: Antenna 378: Satellite positioning / communication signals 380: Network transceiver 382: Data Bus 384: Processor 386: Memory 388: Positioning Component 390: Network transceiver 392: Data Bus 394: Processor 396: Memory 398: Positioning Component 400: UE positioning operation 402: NG-RAN Node 410a: Steps 410b: Steps 410c: Steps 420: Steps 430a: Steps 430b: Steps 440: Steps 450a: Steps 450b: Steps 450c: Steps 480:5GC LCS Entities 500: LPP Capability Transmission Procedure 504: Target 510: Steps 520: Steps 570: Server 600: LPP Capability Indication Procedure 604: Target 610: Steps 670: Server 700: Capability Storage Program 702:gNB 710: Operation 720: Operation 730: Operation 740: Operation 780: Gateway Movement Position Center (GMLC) 800: Capability Storage Program 802:gNB 810: Operation 820: Operation 830: Operation 840: Operation 850: Operation 880:GMLC 900: Method 910: Steps 1000: Method 1010: Steps 1100: Method 1110: Steps 1120: Steps 1200: Method 1210: Steps 1300: Method 1310: Steps 1400: Method 1410: Steps

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: One or more location capability reports are sent to a location server, the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates the variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates the non-variable location capability of the UE represented by the set of location capability parameters to be stored by a network entity for subsequent location dialogue.

2. The method according to claim 1 further includes: A location capability request is received from the location server, the location capability request indicating the set of location capability parameters.

3. The method according to claim 2, wherein, The location capability request includes a flag indicating that the values ​​of the location capability parameter set will be stored by the network entity.

4. The method according to request item 3, wherein, The one or more location capability reports, including the first value set and the second value set, are sent in response to the location capability request including the flag.

5. The method according to request item 1, wherein, The one or more location capability reports include a flag indicating that the second set of values ​​indicates the UE's location capability, represented by the set of location capability parameters, to be stored by the network entity for subsequent location dialogue.

6. The method according to request item 1, wherein, The second set of values ​​is a subset of the values ​​of the positioning capability parameter set.

7. The method according to claim 6, wherein, Each value in the subset of values ​​is associated with a flag that indicates that the value will be stored by the network entity for subsequent location dialogue.

8. The method according to claim 6, wherein, The first set of values ​​is a distinct set of values ​​from the subset of values ​​in the set of positioning capability parameters.

9. The method according to request item 1, wherein: The variable positioning capability is the positioning capability that the UE can only provide for a limited time, while the non-variable positioning capability is the positioning capability that the UE can always provide.

10. The method according to request item 1, wherein: The second set of values ​​is the difference relative to the first set of values, or the first set of values ​​is the difference relative to the second set of values.

11. The method according to claim 1, wherein, The non-variable positioning capabilities of the UE, represented by the set of positioning capability parameters, will be stored by the Access and Mobility Management Function (AMF).

12. A method for wireless communication performed by a network entity, comprising: One or more location capability reports are received from a user equipment (UE), the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates the variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates the non-variable location capability of the UE represented by the set of location capability parameters to be stored by a second network entity for subsequent location dialogue.

13. The method according to claim 12, wherein, The network entity is a location server, and the method further includes: sending a location capability request to the UE, wherein the location capability request indicates the location capability parameter set.

14. The method according to claim 13, wherein, The location capability request includes a flag indicating that the values ​​of the location capability parameter set will be stored by the second network entity.

15. The method according to claim 12, wherein, The one or more location capability reports include a flag indicating that the second set of values ​​indicates the UE's location capabilities, represented by the set of location capability parameters, to be stored by the second network entity for subsequent location dialogue.

16. The method according to claim 12, wherein, The second set of values ​​is a subset of the values ​​of the positioning capability parameter set.

17. The method according to claim 16, wherein, Each value in the subset of values ​​is associated with a flag that indicates that the value will be stored by the second network entity for subsequent location dialogue.

18. The method according to claim 16, wherein, The first set of values ​​is a distinct set of values ​​from the subset of values ​​in the set of positioning capability parameters.

19. The method according to request item 12, wherein: The variable positioning capability is the positioning capability that the UE can only provide for a limited time, while the non-variable positioning capability represents the positioning capability that the UE can always provide.

20. The method according to request item 12, wherein: The second set of values ​​is the difference relative to the first set of values, or the first set of values ​​is the difference relative to the second set of values.

21. The method according to claim 12, wherein, The non-variable positioning capabilities of the UE, represented by the set of positioning capability parameters, will be stored by the Access and Mobility Management Function (AMF).

22. A method for wireless communication performed by a first network entity, comprising: Receive one or more location capability reports from a user equipment (UE), the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and send the set of values ​​to a second network entity via one or more capability transmission messages so that the second network entity can store only the set of values ​​for subsequent location dialogues involving the UE.

23. The method according to request item 22, wherein: The first network entity is the Access and Mobility Management Function Unit (AMF), and the second network entity is the first location server.

24. The method according to claim 23 further includes: Based on the UE switching from the first location server to the second location server due to the UE's mobility, the value set is sent to the second location server via one or more capability transmission messages.

25. The method according to request item 22, wherein: The first network entity is a Location Management Function (LMF), and the second network entity is an AMF.

26. A method for wireless communication performed by a second network entity, comprising: A set of values ​​for a set of positioning capability parameters from one or more positioning capability reports received from a user equipment (UE) via one or more capability transmission messages, wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE and is to be stored by the second network entity.

27. The method according to request item 26, wherein: The first network entity is the Location Management Function Unit (LMF), and the second network entity is the Access and Mobility Management Function Unit (AMF).

28. A user equipment (UE), comprising: 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: send one or more location capability reports to a location server via the at least one transceiver, the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates the variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates the non-variable location capability of the UE represented by the set of location capability parameters to be stored by a network entity for subsequent location dialogue.

29. The UE according to request item 28, wherein, The at least one processor is further configured to receive a location capability request from the location server via the at least one transceiver, the location capability request indicating the set of location capability parameters.

30. The UE according to request item 28, wherein, The one or more location capability reports include a flag indicating that the second set of values ​​indicates the UE's location capability, represented by the set of location capability parameters, to be stored by the network entity for subsequent location dialogue.

31. The UE according to request item 28, wherein, The second set of values ​​is a subset of the values ​​of the positioning capability parameter set.

32. The UE according to request item 28, wherein: The second set of values ​​is the difference relative to the first set of values, or the first set of values ​​is the difference relative to the second set of values.

33. A network entity, comprising: 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 one or more location capability reports from a user equipment (UE) via the at least one transceiver, the one or more location capability reports including a first set of values ​​for a set of location capability parameters and a second set of values ​​for the set of location capability parameters, wherein the first set of values ​​indicates the variable location capability of the UE represented by the set of location capability parameters, and wherein the second set of values ​​indicates the non-variable location capability of the UE represented by the set of location capability parameters to be stored by a second network entity for subsequent location dialogue.

34. The network entity as described in claim 33, wherein, The network entity is a location server, and the method further includes: sending a location capability request to the UE via the at least one transceiver, the location capability request indicating the set of location capability parameters.

35. The network entity as described in claim 33, wherein, The one or more location capability reports include a flag indicating that the second set of values ​​indicates the UE's location capabilities, represented by the set of location capability parameters, to be stored by the second network entity for subsequent location dialogue.

36. The network entity as described in claim 33, wherein, The second set of values ​​is a subset of the values ​​of the positioning capability parameter set.

37. The network entity as described in claim 33, wherein: The second set of values ​​is the difference relative to the first set of values, or the first set of values ​​is the difference relative to the second set of values.

38. A first network entity, comprising: 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 one or more location capability reports from a user equipment (UE) via the at least one transceiver, the one or more location capability reports including a set of values ​​for a set of location capability parameters, wherein the set of values ​​is immutable for subsequent location dialogues involving the UE; and transmit the set of values ​​to a second network entity via one or more capability transmission messages via the at least one transceiver, such that the second network entity is able to store only the set of values ​​for subsequent location dialogues involving the UE.

39. The first network entity as described in claim 38, wherein: The first network entity is the Access and Mobility Management Function Unit (AMF), and the second network entity is the first location server.

40. The first network entity according to claim 39, wherein, The at least one processor is further configured to: based on the UE switching from the first location server to the second location server due to the UE's mobility, transmit the set of values ​​to the second location server via one or more capabilities through the at least one transceiver.

41. The first network entity as described in claim 38, wherein: The first network entity is a Location Management Function (LMF), and the second network entity is an AMF.

42. A second network entity, comprising: 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, via the at least one transceiver, a set of values ​​for a set of positioning capability parameters from a first network entity in one or more positioning capability reports from a user equipment (UE), wherein the set of values ​​is immutable for subsequent positioning dialogues involving the UE and is to be stored by the second network entity.

43. The second network entity according to claim 42, wherein: The first network entity is the Location Management Function Unit (LMF), and the second network entity is the Access and Mobility Management Function Unit (AMF).

Images