Integrity information for radio access technology dependent positioning assistance data - Patents.com

Abstract

Techniques for wireless communications are disclosed. In one aspect, a user equipment (UE) receives assistance data for a radio access technology (RAT) dependent positioning procedure from a location server, the assistance data including one or more positioning parameters for enabling the UE to perform the RAT dependent positioning procedure, the assistance data further including one or more integrity parameters related to the one or more positioning parameters, and determines an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

Description

[Technical field]

[0001] Aspects of the present disclosure relate generally to wireless communications. [Background technology]

[0002] 2. Description of Related Art

[0002] Wireless communication systems have evolved through various generations, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including interim 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-enabled wireless service, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (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.

[0003]

[0003] The fifth generation (5G) wireless standard, called New Radio (NR), will enable higher data rates, more connections, and better coverage, among other improvements. The 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on a reference signal for positioning (RS-P), such as a downlink, uplink, or sidelink positioning reference signal (PRS)), and other technical enhancements compared to previous standards, according to the Next Generation Mobile Network Alliance. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technologies, and dense deployment for 5G, will enable highly accurate 5G-based positioning. Summary of the Invention

[0004]

[0004] The following provides a simplified summary of one or more aspects disclosed herein. Therefore, the following summary should not be considered as an extensive overview of all contemplated aspects, nor should it be considered as identifying key or critical elements of all contemplated aspects or as defining the scope of any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts of one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0005]

[0005] In one aspect, a method of wireless communications performed by a user equipment (UE) includes receiving one or more positioning parameters from a location server to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmit / receive point (TRP), where the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; receiving one or more integrity parameters related to the one or more positioning parameters from the location server; and determining an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0006]

[0006] In one aspect, a method of communication implemented by a location server includes transmitting one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmit / receive point (TRP) to a user equipment (UE), where the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line of sight (LOS) information associated with the PRS resource, or any combination thereof, and transmitting one or more integrity parameters related to the one or more positioning parameters to the UE.

[0007]

[0007] In one aspect, a user equipment (UE) comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor receives, via the at least one transceiver, one or more positioning parameters from a location server to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), the one or more positioning parameters including a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, at least one the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; and configured to receive from the location server, via the at least one transceiver, one or more integrity parameters related to the one or more positioning parameters; and determine an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0008]

[0008] In one aspect, a location server comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to transmit, via the at least one transceiver, one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP) to a user equipment (UE), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof, and to transmit, via the at least one transceiver, one or more integrity parameters related to the one or more positioning parameters to the UE.

[0009]

[0009] In one aspect, a user equipment (UE) includes means for receiving one or more positioning parameters from a location server to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmit / receive point (TRP), where the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; means for receiving one or more integrity parameters related to the one or more positioning parameters from the location server; and means for determining an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0010]

[0010] In one aspect, the location server includes means for transmitting one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmit / receive point (TRP) to a user equipment (UE), where the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with the location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof, and means for transmitting one or more integrity parameters related to the one or more positioning parameters to the UE.

[0011]

[0011] 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 receive from a location server one or more positioning parameters to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmit / receive point (TRP), the one or more positioning parameters including a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; receive from the location server one or more integrity parameters related to the one or more positioning parameters; and determine an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0012]

[0012] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to transmit one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmit / receive point (TRP) to a user equipment (UE), the one or more positioning parameters including a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof, and cause the location server to transmit one or more integrity parameters related to the one or more positioning parameters to the UE.

[0013]

[0013] Other objects and advantages associated with the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description. [Brief description of the drawings]

[0014]

[0014] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided only to illustrate the aspects and not to limit the aspects. [Figure 1]

[0015] FIG. 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 2A]

[0016] 1 illustrates an exemplary wireless network structure in accordance with an aspect of the present disclosure. [Figure 2B] 1 illustrates an exemplary wireless network structure in accordance with an aspect of the present disclosure. [Figure 3A]

[0017] 1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communications as taught herein; [Figure 3B] 1 is a simplified block diagram of several sample aspects of components that may be employed in a base station and configured to support communications as taught herein. [Figure 3C] 1 is a simplified block diagram of several sample aspects of components that may be employed in a network entity and configured to support communications as taught herein. [Figure 4]

[0018] FIG. 2 illustrates an example frame structure according to an aspect of the present disclosure. [Diagram 5]

[0019] 1 illustrates examples of various positioning methods supported in New Radio (NR) in accordance with an aspect of the present disclosure. [Figure 6]

[0020] FIG. 2 illustrates an exemplary base station communicating with an exemplary UE, in accordance with an aspect of the present disclosure. [Figure 7]

[0021] 1 illustrates an example Long Term Evolution (LTE) positioning protocol (LPP) call flow between a UE and a location server for performing a positioning operation. [Figure 8]

[0022] FIG. 1 illustrates various integrity parameters and events, according to aspects of the present disclosure. [Figure 9]

[0023] FIG. 1 illustrates different operating conditions in different integrity zones, according to aspects of the present disclosure. [Figure 10]

[0024] 1 is a diagram of a probability distribution of position error according to an aspect of the present disclosure. [Figure 11]

[0025] 1 is a graph of the relationship between tail area probability and k, according to an embodiment of the present disclosure. [Figure 12A]

[0026] 1 is a table illustrating a mapping of an integrity parameter to Global Navigation Satellite System (GNSS) assistance data, according to an aspect of the present disclosure. [Figure 12B] 1 is a table illustrating a mapping of an integrity parameter to Global Navigation Satellite System (GNSS) assistance data, according to an aspect of the present disclosure. [Figure 13]

[0027] 1 illustrates an example “NR-PositionCalculationAssistance” information element (IE) according to an aspect of the present disclosure. [Figure 14]

[0028] 1 illustrates various TRP location information IEs that may be provided to a UE in assistance data, according to an aspect of the disclosure. [Figure 15]

[0029] 1 illustrates an exemplary method of communication according to an aspect of the present disclosure. [Figure 16] 1 illustrates an exemplary method of communication according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015]

[0030] Aspects of the present disclosure are provided in the following description and associated drawings, directed to various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the present disclosure.

[0016]

[0031] The words "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 necessarily be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

[0017]

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

[0018]

[0033] Further, many aspects are described in terms of sequences of actions to be performed, for example, by elements of a computing device. It will be appreciated that various activities described herein may be performed by specific circuitry (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. In addition, the sequence or sequences of actions described herein may be considered to be fully embodied in any form of non-transitory computer-readable storage medium having stored thereon a corresponding set of computer instructions that, when executed, cause or instruct the associated processors of the device to perform the functions described herein. Thus, various aspects of the present disclosure may be embodied in a number of different forms, all of which are contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspect may be described herein, for example, as "logic configured to" perform the described actions.

[0019]

[0034] The terms "user equipment" (UE) and "base station" as used herein are not intended to be specific or limited to any particular radio access technology (RAT) unless otherwise specified. In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer location device, a wearable (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or stationary (e.g., at a given time) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be referred to interchangeably as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station", or variations thereof. In general, a UE may communicate with a core network via a RAN, through which the UE may be connected to external networks such as the Internet, and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specifications, etc.).

[0020]

[0035] A base station may operate according to one of several RATs in communication with UEs depending on the network in which the base station is deployed and may alternatively be 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 referred to as gNB or gNode B), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functionality, while in other systems, a base station may provide additional control and / or network management functionality. The communication links over which a UE may send signals to a base station are referred to as uplink (UL) channels (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0021]

[0036] The term "base station" may refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station, corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple collocated physical TRPs, the physical TRP may be an array of antennas of the base station (e.g., as in the case of a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, non-co-located physical TRPs may be serving base stations that receive measurement reports from the UE and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Since a TRP is a point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station.

[0022]

[0037] In some implementations that support positioning of UEs, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE) but may instead transmit reference signals to the UE to be measured by the UE and / or receive and measure signals transmitted by the UE. Such base stations may be referred to as positioning beacons (e.g., when they transmit signals to the UE) and / or location measurement units (e.g., when they receive and measure signals from the UE).

[0023]

[0038] An "RF signal" includes electromagnetic waves of a given frequency that propagate information through space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same RF signal transmitted over different paths between a transmitter and a receiver may 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" when it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0024]

[0039] 1 illustrates an example wireless communication system 100 according to aspects of the disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. The 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 an aspect, the 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 the small cell base stations may include femtocells, picocells, microcells, etc.

[0025]

[0040] The base stations 102 may collectively form a RAN and may interface with a core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) through the backhaul links 122 and with one or more location servers 172 (e.g., location management function (LMF) or secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server(s) 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as through an application server (not shown), through another network, such as through a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), etc. For purposes of signaling, communication between the UE 104 and the location server 172 may be represented as an indirect connection (e.g., through the core network 170), or a direct connection (e.g., as shown via direct connection 128), with intervening nodes (if any) omitted from the signaling diagrams for clarity.

[0026]

[0041] In addition to other functions, the base stations 102 may perform functions related to one or more of the following: forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, non-access stratum (NAS) message delivery, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and alert message delivery. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) via backhaul links 134, which may be wired or wireless.

[0027]

[0042] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by the base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., over some frequency resources, referred to as a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Since a cell is supported by a particular base station, the term "cell" may refer to one or both of the logical communication entity and the base station that supports it, depending on the context. In addition, since a TRP is typically a physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0028]

[0043] The geographic coverage areas 110 of neighboring macrocell base stations 102 may overlap partially (e.g., in handover regions) and some of the geographic coverage areas 110 may be substantially overlapped by 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 area 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may serve closed groups known as closed subscriber groups (CSGs).

[0029]

[0044] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be through one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

[0030]

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

[0031]

[0046] The small cell base station 102' may operate in licensed and / or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell base station 102' may utilize LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. The small cell base station 102' employing LTE / 5G in the unlicensed frequency spectrum may extend coverage to and / or increase capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0032]

[0047] The wireless communication system 100 may further include a mmW base station 180 that may operate in millimeter wave (mmW) and / or sub-mmW frequencies in communication with the UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Sub-mmW may go down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also referred to as centimeter wave. Communications using the mmW / sub-mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely large path loss and short distances. It will be further understood that in alternative configurations, one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Thus, it will be understood that the above illustrations are merely examples and should not be construed as limiting various aspects disclosed herein.

[0033]

[0048] Transmit beamforming is a technique for concentrating an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts it in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and launches a stronger downlink RF signal in that particular direction, thereby providing a faster and more powerful RF signal (in terms of data rate) to the receiving device(s). To vary the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (also called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, RF currents from a transmitter are supplied to the individual antennas with the proper phase relationship so that the radio waves from the separate antennas are combined together to enhance radiation in desired directions while suppressing and canceling radiation in undesirable directions.

[0034]

[0049] A transmit beam may be quasi-co-located, meaning that the transmit beam appears to a receiver (e.g., UE) to have the same parameters regardless of whether the network node's own transmit antenna is physically co-located or not. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a QCL relationship of a given type means that some parameters for a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, 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 a 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 spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0035]

[0050] In receive beamforming, a receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., increase the gain level) RF signals received from that direction. Thus, when a receiver is said to beamform in some direction, it means that the beam gain in that direction is higher than the beam gains along other directions, or that the beam gain in that direction is highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of RF signals received from that direction.

[0036]

[0051] The transmit beam and the receive beam may be spatially related. The spatial relationship means that the parameters for the second beam (e.g., transmit beam or receive beam) for the second reference signal may be derived from information about the first beam (e.g., receive beam or transmit beam) for the first reference signal. For example, the UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0037]

[0052] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms a downlink beam to transmit a reference signal to the UE, then the downlink beam is a transmit beam. However, if the UE forms a downlink beam, then it is a receive beam to receive a downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms an uplink beam, then it is an uplink receive beam, and if the UE forms an uplink beam, then it is an uplink transmit beam.

[0038]

[0053] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers, although a portion of FR1 is above 6 GHz. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU).

[0039]

[0054] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus, in effect, extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0040]

[0055] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Further, it should be understood that unless otherwise specified, terms such as "mmWave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within the ranges of FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

[0041]

[0056] In a multi-carrier system such as 5G, one of the carrier frequencies is called the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are called the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and on the cell in which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and may (but is not always) be a carrier among licensed frequencies. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier among unlicensed frequencies. Since both the primary uplink carrier and the primary downlink carrier are typically UE specific, the secondary carrier may include only the necessary signaling information and signals, e.g., the signaling information and signals that are UE specific may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network may change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to distribute the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier over which several base stations are communicating, terms such as "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0042]

[0057] For example, still referring to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz carriers aggregated in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0043]

[0058] The wireless communications system 100 may further include a UE 164, which may communicate with the macrocell base station 102 via communications link 120 and / or with the mmW base station 180 via an mmW communications link 184. For example, the macrocell base station 102 may support a PCell 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.

[0044]

[0059] In some cases, the UE 164 and the UE 182 may be capable of sidelink communications. A sidelink-enabled UE (SL-UE) can communicate with the base station 102 over a communication link 120 that uses a Uu interface (i.e., an air interface between the UE and the base station). The SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over a wireless sidelink 160 that uses a PC5 interface (i.e., an air interface between sidelink-enabled UEs). Wireless sidelink (or simply "sidelink") is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication having to go through a base station. Sidelink communications may be unicast or multicast and may be used for device-to-device (D2D) medium sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-everything (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of the groups of SL-UEs utilizing sidelink communications may be within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102 or may not be able to receive transmissions from the base station 102. In some cases, a group of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system in which each SL-UE transmits to all other SL-UEs in the group. In some cases, the base station 102 facilitates scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between SL-UEs without the involvement of the base station 102.

[0045]

[0060] In one aspect, the sidelink 160 may operate on a subject wireless communication medium, which may be shared with other vehicular and / or infrastructure access points, as well as other wireless communications between other RATs. The "medium" may consist of one or more time, frequency, and / or spatial communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs. In one aspect, the subject medium may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for some communication systems (e.g., by government agencies such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended operation to unlicensed frequency bands, such as the Unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies, most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi". Exemplary systems of this type include CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and various variations thereof.

[0046]

[0061] It should be noted that while FIG. 1 illustrates only two of the UEs as SL-UEs (i.e., UE 164 and 182), any of the illustrated UEs may be SL-UEs. Additionally, while only UE 182 has been described as being beamforming capable, any of the illustrated UEs may be beamforming capable, including UE 164. If SL-UEs are beamforming capable, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cell 102′, access point 150), and so forth. Thus, in some cases, UE 164 and UE 182 may utilize beamforming over sidelink 160.

[0047]

[0062] In the example of FIG. 1, any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based at least in part on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located within the SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UE 104 may include one or more dedicated receivers specifically designed to receive the signals 124 from the SV 112 to derive geolocation information.

[0048]

[0063] In a satellite positioning system, the use of the signals 124 may be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, the SBAS may include augmentation systems that provide integrity information, error correction, and the like, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS)-aided Geo-augmented navigation, or the GPS and Geo Augmented Navigation system (GAGAN). Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0049]

[0064] In one aspect, the SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, the SV 112 is connected to an earth station (also called a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5G network. This element will then provide access to other elements in the 5G network and ultimately to entities outside the 5G network, such as Internet web servers and other user devices. In this way, the UE 104 may receive communication signals (e.g., signal 124) from the SV 112 instead of or in addition to communication signals from the terrestrial base station 102.

[0050]

[0065] The wireless communication system 100 may further include one or more UEs, such as UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "sidelinks"). In the example of FIG. 1, the UE 190 has a D2D P2P link 192 (e.g., through which the UE 190 may indirectly obtain cellular connectivity) with one of the UEs 104 connected to one of the base stations 102, and a D2D P2P link 194 (through which the UE 190 may indirectly obtain WLAN-based Internet connectivity) with a WLAN STA 152 connected to a WLAN AP 150. In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth, etc.

[0051]

[0066] 2A illustrates an exemplary wireless network structure 200. For example, the 5GC 210 (also referred to as Next Generation Core (NGC)) may be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.) that operate cooperatively to form a 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, specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 may also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Additionally, the ng-eNB 224 may communicate directly with the gNB 222 via a 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) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0052]

[0067] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance to the UE(s) 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location servers 230 may be configured to support one or more location services for the UEs 204 that may connect 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 components of the core network, or alternatively, may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0053]

[0068] 2B illustrates another exemplary wireless network structure 250. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) may be considered functionally as control plane functions provided by an access and mobility management function (AMF) 264 and user plane functions provided by a user plane function (UPF) 262, which operate cooperatively to form a core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204 to receive intermediate keys established as a result of the UE 204 authentication process. In case of UMTS (universal mobile telecommunications system) subscriber identity module (USIM) based authentication, the AMF 264 retrieves security material from the AUSF. The AMF 264 functionality also includes security context management (SCM). The SCM receives keys from the SEAF that the SCM uses to derive access network specific keys.The functionality of the AMF 264 also includes location service management for regulated services, transport for location service messages between the UE 204 and the Location Management Function (LMF) 270 (acting as the location server 230), transport for location service messages between the NG-RAN 220 and the LMF 270, Evolved Packet System (EPS) bearer identifier allocation for interworking with EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functions for non-3GPP (Third Generation Partnership Project) access networks.

[0054]

[0069] The functions of the UPF 262 include acting as an anchor point for intra / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), routing and forwarding of packets, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, Quality of Service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic validation (Service Data Flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support forwarding of location service messages on the user plane between the UE 204 and a location server such as the SLP 272.

[0055]

[0070] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering in the UPF 262 to route traffic to the appropriate destination, control of policy enforcement and part of QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is called the N11 interface.

[0056]

[0071] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may represent a single server. The LMF 270 may be configured to support one or more location services for UEs 204 that may connect to the LMF 270 via a core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support similar functions as the LMF 270, while the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 via the control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data) and the SLP 272 may communicate with the UE 204 and external clients (e.g., third-party servers 274) via the user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0057]

[0072] Yet another optional aspect may include a third party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third party server 274 may be referred to as a location services (LCS) client or an external client. The third party servers 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or, alternatively, each may correspond to a single server.

[0058]

[0073] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and in particular the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as the “Xn-C” interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a “Uu” interface.

[0059]

[0074] The functionality of the gNB 222 may be divided between a 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 forwarding user data, mobility control, radio access network sharing, positioning, session management, etc., except for those functions exclusively allocated to the gNB-DU(s) 228. More specifically, the gNB-CU 226 typically hosts 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 hosts the Radio Link Control (RLC), Medium 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 multiple cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is generally hosted by one or more standalone gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0060]

[0075] 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated in a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including a location server 230 and an LMF 270, or alternatively may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be understood that these components may be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated in other devices in a communication system. For example, other devices in the system may include components similar to the described components to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may contain multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0061]

[0076] The UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) over one or more wireless communications networks (not shown), such as an NR network, an LTE network, a GSM network, etc. The WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., over at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communications medium of interest (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured to transmit and encode signals 318 and 358 (e.g., messages, instructions, information, etc.), respectively, and conversely, to receive and decode signals 318 and 358 (e.g., messages, instructions, information, pilots, etc.), respectively, in accordance with a designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and include one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0062]

[0077] The UE 302 and base station 304 also each, at least in some cases, 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 may provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth, Zigbee, Z-Wave, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), etc.) over the wireless communication medium. The short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368 (e.g., messages, instructions, information, etc.), respectively, and conversely, to receive and decode signals 328 and 368 (e.g., messages, instructions, information, pilots, etc.), respectively, in accordance with a specified RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, to transmit and encode signals 328 and 368, respectively, and include one or more receivers 322 and 362, respectively, to receive and decode signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may 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.

[0063]

[0078] The UE 302 and the base station 304 also, at least in some cases, include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide a means for receiving and / or measuring satellite positioning / communications signals 338 and 378, respectively. If the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communications signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Navigation Satellite System of India (NAVIC), Quasi-Zenith Satellite System (QZSS) signals, other Global Navigation Satellite System (GNSS) signals. If satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communications signals 338 and 378 may be communication signals (e.g., carrying control data and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communications signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and actions from other systems as appropriate, and may perform calculations, at least in some cases, to determine the location of UE 302 and base station 304, respectively, using measurements obtained according to any suitable satellite positioning system algorithms.

[0064]

[0079] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, that provide a means for communicating (e.g., a means for transmitting, a means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ 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, the network entity 306 may employ 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 with other network entities 306 over one or more wired or wireless core network interfaces.

[0065]

[0080] A transceiver may be configured to communicate over a wired link or a wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The 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 an antenna array that enables the respective device (e.g., UE 302, base station 304) to perform transmit "beamforming" as described herein. Similarly, the 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 an antenna array that enables the respective device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and receiver circuitry may share multiple identical antennas (e.g., antennas 316, 326, 356, 366), such that the respective device can only receive or transmit at a given time, but not both at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short range wireless transceivers 320 and 360) may also include network listen modules (NLMs) and the like for performing various measurements.

[0066]

[0081] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390, in some implementations) and wired transceivers (e.g., network transceivers 380 and 390, in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication being performed. For example, backhaul communications between network devices or servers generally involve signaling via wired transceivers, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally involve signaling via wireless transceivers.

[0067]

[0082] The UE 302, base station 304, and network entity 306 also include other components that may be used in conjunction with operations as disclosed herein. The UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394, for example, to provide functionality related to wireless communications and to provide other processing functionality. Thus, the processors 332, 384, and 394 may comprise processing means, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In one aspect, the processors 332, 384, and 394 may include, for example, 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.

[0068]

[0083] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, the memories 340, 386, and 396 may comprise storage means, retrieval means, maintaining means, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning components 342, 388, and 398, respectively. The positioning components 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functions described herein. In other aspects, the positioning components 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.) cause the UE 302, the base station 304, and the network entity 306 to perform functions described herein. FIG. 3A illustrates possible locations of the positioning component 342, which may be part of, for example, one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a stand-alone component. FIG. 3B shows possible locations of a positioning component 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a stand-alone component.FIG. 3C illustrates possible locations of a 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 stand-alone component.

[0069]

[0084] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of movement data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and / or the satellite signal receiver 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of movement detection sensor. Additionally, the sensor(s) 344 may include multiple different types of devices and combine their outputs to provide movement information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0070]

[0085] Additionally, the UE 302 includes a user interface 346 that provides a means for providing indications to a user (e.g., audio and / or visual indications) and / or receiving user input (e.g., upon user actuation of a sensing device, such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0071]

[0086] Referring more particularly to the one or more processors 384, on the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The one or more processors 384 may provide RRC layer functions associated with broadcast of 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), inter-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 transfer of higher layer PDUs, error correction with automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0072]

[0087] The transmitter 354 and receiver 352 may implement Layer-1 (L1) functions associated with various signal processing functions. Layer-1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles mapping onto signal constellations 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 coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol streams are spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with the individual spatial streams for transmission.

[0073]

[0088] At the UE 302, the receiver 312 receives signals through its respective antenna(s) 316. The receiver 312 recovers the information modulated onto the RF carriers and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 perform layer 1 functions associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 304. The data and control signals are then provided to one or more processors 332 that implement Layer 3 (L3) and Layer 2 (L2) functions.

[0074]

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

[0075]

[0090] Similar to the functionality described in connection with downlink transmissions by the base station 304, the one or more processors 332 provide RRC layer functionality related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with forwarding of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0076]

[0091] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with the individual spatial streams for transmission.

[0077]

[0092] Uplink transmissions are processed at the base station 304 in a manner similar to that described with respect to the receiver function at the UE 302. The receiver 352 receives signals via its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to one or more processors 384.

[0078]

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

[0079]

[0094] For convenience, the UE 302, base station 304, and / or network entity 306 are illustrated in Figures 3A, 3B, and 3C as including various components that may be configured according to various examples described herein. However, it will be understood that the illustrated components may have different functions in different designs. In particular, various components in Figures 3A-3C are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, device use, or other considerations. For example, in the case of Figure 3A, a particular implementation of the UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or may omit the short-range wireless transceiver(s) 320 (e.g., cellular only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor(s) 344, etc. 3B, a particular implementation of base station 304 may omit WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit short-range wireless transceiver(s) 360 (e.g., cellular only), or may omit satellite receiver 370, etc. For brevity, examples of various alternative configurations are not provided herein, but should be readily apparent to one of ordinary skill in the art.

[0080]

[0095] The various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In an aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces of the UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are embodied within the same device (e.g., gNB and location server functionality integrated within the same base station 304), the data buses 334, 382, ​​and 392 may provide communication between them.

[0081]

[0096] The components of Figures 3A, 3B, and 3C may be implemented in a variety of ways. In some implementations, the components of Figures 3A, 3B, and 3C may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310-346 may be implemented by the processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350-388 may be implemented by the processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Also, some or all of the functionality represented by blocks 390-398 may be implemented by the processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it will be understood that such operations, actions, and / or functions may actually be performed by a particular component or combination of components of the UE 302, base station 304, network entity 306, etc., such as the processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, positioning components 342, 388, and 398, etc.

[0082]

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

[0083]

[0098] Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 4 is a diagram 400 illustrating example frame structures according to aspects of the disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0084]

[0099] LTE, and possibly NR, employs orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Generally, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, or the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the subcarrier spacing may be 15 kilohertz (kHz), and the minimum resource allocation (resource block) may be 12 subcarriers (i.e., 180 kHz). Thus, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0085]

[0100] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (μ), e.g., subcarrier spacings of 15 kHz (μ=0), 30 kHz (μ=1), 60 kHz (μ=2), 120 kHz (μ=3), and 240 kHz (μ=4) or more may be available. At each subcarrier spacing, there are 14 symbols per slot. For a 15 kHz SCS (μ=0), there is one slot per subframe, i.e., 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with an FFT size of 4K is 50. For a 30 kHz SCS (μ=1), there are two slots per subframe, i.e., 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 μs, and the maximum nominal system bandwidth (in MHz) for a 4K FFT size is 100. For a 60 kHz SCS (μ=2), there are four slots per subframe, i.e., 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 μs, and the maximum nominal system bandwidth (in MHz) for a 4K FFT size is 200. For a 120 kHz SCS (μ=3), there are eight slots per subframe, i.e., 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 μs, and the maximum nominal system bandwidth (in MHz) for a 4K FFT size is 400. For a 240 kHz SCS (μ=4), there are 16 slots per subframe, i.e., 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 μs, and the maximum nominal system bandwidth (in MHz) with an FFT size of 4K is 800.

[0086]

[0101] In the example of Figure 4, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, with each subframe containing one time slot. In Figure 4, time is represented horizontally (on the X-axis), with time increasing from left to right, and frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0087]

[0102] A resource grid may be used to represent a time slot, with each time slot including one or more time-parallel resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 4, for a normal cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain to obtain a total of 84 REs. For an extended cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain to obtain a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0088]

[0103] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communications. Figure 4 shows example locations of REs carrying reference signals (labeled "R").

[0089]

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

[0090]

[0105] The transmission of PRS resources within a given PRB has a particular comb size (also called "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for comb size "N", a PRS is transmitted in every Nth subcarrier of a symbol of the PRB. For example, for Com 4, for each symbol of the PRS resource configuration, an RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, the following comb sizes are supported for DL-PRS: Com 2, Com 4, Com 6, and Com 12. Figure 4 shows an example PRS resource configuration for Com 4 (spanning four symbols). That is, the location of the shaded RE (labeled "R") indicates the Com 4 PRS resource configuration.

[0091]

[0106] Currently, DL-PRS resources may span 2, 4, 6, or 12 consecutive symbols in a slot with a staggered pattern across the frequency domain. DL-PRS resources may be configured in any higher layer configured downlink or flexible (FL) symbol of a slot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. Below are the symbol-to-symbol frequency offsets for comb sizes 2, 4, 6, and 12 spanning 2, 4, 6, and 12 symbols. 2-symbol-comb2:{0,1}; 4-symbol-comb2:{0,1,0,1}; 6-symbol-comb2:{0,1,0,1,0,1}; 12-symbol-comb2:{0,1,0,1,0,1,0,1,0,1,0,1,0,1} (for the example in Figure 4); 4-symbol-comb4:{0,2,1,3}; 12-symbol-comb4:{0,2,1,3,0,2,1,3,0,2,1,3}; 6-symbol-comb6:{0,3,1,4,2,5}; 12-symbol-comb6:{0,3,1,4,2,5,0,3,1,4,2,5}; and 12-symbol-comb12:{0,6,3,9,1,7,4,10,2,8,5,11}.

[0092]

[0107] A "PRS resource set" is a set of PRS resources used for transmission of a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a particular TRP (identified by a TRP ID). In addition, the PRS resources in a PRS resource set have the same periodicity across slots, a common muting pattern configuration, and the same repetition factor (e.g., "PRS-ResourceRepetitionFactor"). The periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity is μ=0, 1, 2, 3, where μ is a function of 2^μ *The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

[0093]

[0108] A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or multiple beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and thus may also be referred to as a "PRS resource" or simply a "resource", also sometimes referred to as a "beam". Note that this does not have any implication as to whether the TRP and beam on which the PRS is transmitted are known to the UE.

[0094]

[0109] A "PRS instance" or "PRS occasion" is one instance of a periodically repeating time window (e.g., a group of one or more contiguous slots) during which a PRS is expected to be transmitted. A PRS occasion may also be referred to as a "PRS positioning occasion", "PRS positioning instance", "positioning occasion", "positioning instance", "positioning repetition", or simply an "occasion", "instance", or "repetition".

[0095]

[0110] A "positioning frequency layer" (also simply called "frequency layer") is a collection of one or more PRS resource sets across one or more TRPs with the same values ​​for some parameters. In particular, a collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all numerologies supported for the physical downlink shared channel (PDSCH) are also supported for the PRS), the same Point A, the same value of the downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The Point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio-frequency channel number"), which is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth may have a granularity of 4 PRB, with a minimum of 24 PRB and a maximum of 272 PRB. Currently, up to four frequency layers are defined, and up to two PRS resource sets per TRP can be configured per frequency layer.

[0096]

[0111] The concept of frequency layer is somewhat like that of component carrier and bandwidth portion (BWP), but differs in that component carrier and BWP are used by one base station (or macrocell base station and small cell base station) to transmit data channels, whereas frequency layer is used by several (usually three or more) base stations to transmit PRS. A UE may indicate the number of frequency layers that it can support when the UE transmits its positioning capabilities to the network, such as during an LTE Positioning Protocol (LPP) session. For example, the UE may indicate whether it can support one positioning frequency layer or four positioning frequency layers.

[0097]

[0112] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, the terms "positioning reference signal" and "PRS" as used herein may also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. Furthermore, the terms "positioning reference signal" and "PRS" may refer to downlink, uplink, or sidelink positioning reference signals, unless otherwise suggested by the context. If necessary to further distinguish between types of PRS, downlink positioning reference signals may be referred to as "DL-PRS", uplink positioning reference signals (e.g., SRS for positioning, PTRS) may be referred to as "UL-PRS", and sidelink positioning reference signals may be referred to as "SL-PRS". Additionally, for signals that may be transmitted in the downlink, uplink, and / or sidelink (e.g., DMRS), a "DL", "UL", or "SL" may be prepended to the signal to distinguish the direction. For example, "UL-DMRS" is different from "DL-DMRS".

[0098]

[0113] NR supports several cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink- and uplink-based positioning methods. These positioning methods are referred to as "RAT-dependent" positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR (also called downlink azimuth angle of departure (DL-AoD) or zenith angle of departure (DL-ZoD)). Figure 5 illustrates examples of various positioning methods according to aspects of the present disclosure. In an OTDOA or DL-TDOA positioning procedure illustrated by scenario 510, the UE measures the differences between times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, called reference signal time difference (RSTD) measurements or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives an identifier (ID) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in the assistance data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, the positioning entity (e.g., the UE in case of UE-based positioning or a location server in case of UE-assisted positioning) can estimate the location of the UE.

[0099]

[0114] For DL-AoD positioning, illustrated by scenario 520, the positioning entity uses measurement reports from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angles and the known locations of the transmitting base stations.

[0100]

[0115] 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 is based on an uplink reference signal (e.g., sounding reference signal (SRS)) transmitted by the UE to multiple base stations. In particular, the UE transmits one or more uplink reference signals that are measured by a reference base station and multiple non-reference base stations. Each base station then reports the time of reception of the reference signal (called relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the locations and relative timing of the participating base stations. Based on the reception-to-reception (Rx-Rx) time difference between the reported RTOA of the reference base station and that of each non-reference base station, the known locations of the base stations, and their known timing offsets, the positioning entity can estimate the location of the UE using TDOA.

[0101]

[0116] 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 angles of the receive beams to determine an angle between the UE and the base stations. Based on the determined angle and the known locations of the base stations, the positioning entity can then estimate the location of the UE.

[0102]

[0117] Downlink and uplink based positioning methods include Extended Cell ID (E-CID) positioning, and Multiple Round Trip Time (RTT) positioning (also called "Multi-cell RTT" and "Multi-RTT"). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or an SRS) to a second entity (e.g., a UE or a base station), and the second entity transmits a second RTT-related signal (e.g., an SRS or a PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the reception-to-transmission (Rx-Tx) time difference. The Rx-Tx time difference measurement may be made or adjusted to include only the time difference between the nearest slot boundaries for the received and transmitted signals. Both entities may then send their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities from the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may send its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined from the RTT and a known signal speed (e.g., the speed of light). In the case of multi-RTT positioning illustrated by scenario 530, a first entity (e.g., a UE or a base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined based on the distance to the second entity and the known location of the second entity (e.g., using multilateration). As illustrated by scenario 540, RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy.

[0103]

[0118] 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 identities, estimated timing, and signal strength of detected neighboring base stations. The location of the UE is then estimated based on this information and the known locations of the base stations.

[0104]

[0119] To assist the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include an identifier of a base station (or a cell / TRP of a base station) from which to measure a reference signal, reference signal configuration parameters (e.g., the number of consecutive slots containing a PRS, the periodicity of consecutive slots containing a PRS, a muting sequence, a frequency hopping sequence, a reference signal identifier, a reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may be obtained directly from the base station itself (e.g., in periodically broadcasted overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes itself without using the assistance data.

[0105]

[0120] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may further include an expected RSTD value and an associated uncertainty around the expected RSTD, i.e., a search window. In some cases, the value range for the expected RSTD may be + / - 500 microseconds (μs). In some cases, the value range for the expected RSTD uncertainty may be + / - 32 μs when any of the resources used for positioning measurements are in FR1. In other cases, the value range for the expected RSTD uncertainty may be + / - 8 μs when all of the resources used for positioning measurements are in FR2.

[0106]

[0121] A location estimate may be referred to by other names, such as a position estimate, location, position, position fix, fix, etc. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude), or urban and comprise a street address, postal address, or some other linguistic description of the location. A location estimate may also be defined relative to some other known location, or defined absolutely (e.g., using latitude, longitude, and possibly altitude). A location estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be contained with some specified or default level of confidence).

[0107]

[0122] 6 is a diagram 600 illustrating a base station (BS) 602 (which may correspond to any of the base stations described herein) in communication with a UE 604 (which may correspond to any of the UEs described herein). With reference to FIG. 6, the base station 602 may transmit beamformed signals to the UE 604 in one or more transmit beams 612a, 612b, 612c, 612d, 612e, 612f, 612g, 612h (collectively, beams 612), each having a beam identifier that may be used by the UE 604 to identify the respective beam. If the base station 602 is beamforming toward the UE 604 with a single array of antennas (e.g., a single TRP / cell), the base station 602 may perform "beam sweeping" by first transmitting beam 612a, then beam 612b, and so on until finally transmitting beam 612h. Alternatively, the base station 602 may transmit the beams 612 in several patterns, such as beam 612a, then beam 612h, then beam 612b, then beam 612g, etc. If the base station 602 is beamforming towards the UE 604 using multiple arrays of antennas (e.g., multiple TRPs / cells), each antenna array may perform beam sweeping of a subset of the beams 612. Alternatively, each of the beams 612 may correspond to a single antenna or antenna array.

[0108]

[0123] 6 further illustrates paths 622c, 622d, 622e, 622f, and 622g taken by beamformed signals transmitted on beams 612c, 612d, 612e, 612f, and 612g, respectively. Each path 622c, 622d, 622e, 622f, 622g may correspond to a single "multipath" or may be composed of multiple "multipaths" (clusters of "multipaths") due to the propagation characteristics of radio frequency (RF) signals through the environment. Note that while only paths 622c-622g for beams 612c-612g are shown, this is for simplicity and signals transmitted on each of the beams 612 will follow some path. In the illustrated example, paths 622c, 622d, 622e, and 622f are straight lines, and path 622g is reflected off an obstacle 620 (eg, a building, a vehicle, a terrain feature, etc.).

[0109]

[0124] The UE 604 may receive beamformed signals from the base station 602 in one or more receive beams 614a, 614b, 614c, 614d (collectively, beams 614). Note that for simplicity, the beams shown in FIG. 6 represent either transmit or receive beams, depending on which of the base station 602 and the UE 604 is transmitting and which is receiving. Thus, the UE 604 may also transmit beamformed signals to the base station 602 in one or more of the beams 614, and the base station 602 may receive beamformed signals from the UE 604 in one or more of the beams 612.

[0110]

[0125] In one aspect, the base station 602 and the UE 604 may perform beam training to align the transmit and receive beams of the base station 602 and the UE 604. For example, depending on environmental conditions and other factors, the base station 602 and the UE 604 may determine that the best transmit and receive beams are 612d and 614b, respectively, or are beams 612e and 614c, respectively. The direction of the best transmit beam for the base station 602 may or may not be the same as the direction of the best receive beam, and similarly, the direction of the best receive beam for the UE 604 may or may not be the same as the direction of the best transmit beam. However, it should be noted that the transmit and receive beams do not need to be aligned to perform a downlink angle of departure (DL-AoD) or uplink angle of arrival (UL-AoA) positioning procedure.

[0111]

[0126] To perform the DL-AoD positioning procedure, the base station 602 may transmit reference signals (e.g., PRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to the UE 604 on one or more of the beams 612, with each beam having a different transmit angle. The different transmit angles of the beams will result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) at the UE 604. In particular, the received signal strength is less for transmit beams 612 that are farther from the line-of-sight (LOS) path 610 between the base station 602 and the UE 604 than for transmit beams 612 that are closer to the LOS path 610.

[0112]

[0127] 6, if the base station 602 transmits reference signals to the UE 604 on beams 612c, 612d, 612e, 612f, and 612g, the transmit beam 612e is best aligned with the LOS path 610, while the transmit beams 612c, 612d, 612f, and 612g are not. Thus, the beam 612e is likely to have a greater received signal strength at the UE 604 than the beams 612c, 612d, 612f, and 612g. Note that the reference signals transmitted on some beams (e.g., beams 612c and / or 612f) may not reach the UE 604, or the energy reaching the UE 604 from these beams may be too low such that the energy may not be detectable or may at least be ignored.

[0113]

[0128] The UE 604 may report the received signal strength of each measured transmit beam 612c-612g and optionally the associated measurement quality, or the identity of the transmit beam with the highest received signal strength (beam 612e in the example of FIG. 6) to the base station 602. Alternatively or additionally, if the UE 604 is also involved in a round-trip time (RTT) or time difference of arrival (TDOA) positioning session with at least one or multiple base stations 602, respectively, the UE 604 may report reception-to-transmission (Rx-Tx) time difference or reference signal time difference (RSTD) measurements (and optionally associated measurement qualities) to the serving base station 602 or other positioning entity, respectively. In either case, a positioning entity (e.g., base station 602, location server, third party client, UE 604, etc.) can estimate the angle from base station 602 to UE 604 as the AoD of the transmit beam with the highest received signal strength at UE 604, here transmit beam 612e.

[0114]

[0129] In one aspect of DL-AoD based positioning where there is only one participating base station 602, the base station 602 and the UE 604 can perform a round trip time (RTT) procedure to determine the distance between the base station 602 and the UE 604. Thus, the positioning entity can determine both the direction to the UE 604 (using DL-AoD positioning) and the distance to the UE 604 (using RTT positioning) to estimate the location of the UE 604. It should be noted that the AoD of the transmit beam with the highest received signal strength is not necessarily along the LOS path 610 as shown in FIG. 6. However, for DL-AoD based positioning purposes, it is assumed to be the case.

[0115]

[0130] In another aspect of DL-AoD based positioning where there are multiple participating base stations 602, each participating base station 602 may report to the serving base station 602 the determined AoD or RSRP measurements from the respective base station 602 to the UE 604. The serving base station 602 may then report the AoD or RSRP measurements from the other participating base station(s) 612 to the positioning entity (e.g., the UE 604 for UE-based positioning or a location server for UE-assisted positioning). With this information and knowing the geographical locations of the base stations 612, the positioning entity can estimate the location of the UE 604 as the intersection of the determined AoDs. For a two-dimensional (2D) location solution, there should be at least two participating base stations 602, but as will be appreciated, the more base stations 602 involved in the positioning procedure, the more accurate the estimated UE 604 location will be.

[0116]

[0131] To perform the UL-AoA positioning procedure, the UE 604 transmits uplink reference signals (e.g., UL-PRS, SRS, DMRS, etc.) to the base station 602 on one or more of the uplink transmit beams 614. The base station 602 receives the uplink reference signals on one or more of the uplink receive beams 612. The base station 602 determines the angle of the best receive beam 612 used to receive the one or more reference signals from the UE 604 as the AoA from the UE 604 to itself. In particular, each of the receive beams 612 will result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) of the one or more reference signals at the base station 602. Furthermore, the channel impulse response of the one or more reference signals will be smaller for receive beams 612 that are farther away from the actual LOS path 610 between the base station 602 and the UE 604 than for receive beams 612 that are closer to the LOS path 610. Similarly, the received signal strength will be lower for receive beams 612 farther from the LOS path 610 than for receive beams 612 closer to the LOS path 610. Thus, the base station 602 identifies the receive beam 612 that provides the highest received signal strength, and optionally the strongest channel impulse response, and estimates the angle from itself to the UE 604 as the AoA of that receive beam 612. Note that, similar to DL-AoD based positioning, the AoA of the receive beam 612 that provides the highest received signal strength (and strongest channel impulse response, if measured) does not necessarily lie along the LOS path 610. However, for purposes of UL-AoA based positioning in FR2, it may be assumed to lie along the path 610.

[0117]

[0132] It should be noted that although the UE 604 is shown as being capable of beamforming, this is not required for DL-AoD and UL-AoA positioning procedures. Rather, the UE 604 may receive and transmit with an omni-directional antenna.

[0118]

[0133] If the UE 604 is estimating its location (i.e., the UE is a positioning entity), it needs to obtain the geographic location of the base station 602. The UE 604 may obtain the location, for example, from the base station 602 itself or from a location server (e.g., location server 230, LMF 270, SLP 272). Knowing the distance to the base station 602 (based on RTT or timing advance), the angle between the base station 602 and the UE 604 (based on the UL-AoA of the best received beam 612), and the known geographic location of the base station 602, the UE 604 can estimate its location.

[0119]

[0134] Alternatively, if a positioning entity, such as the base station 602 or a location server, is estimating the location of the UE 604, the base station 602 reports the AoA of the receive beam 612 that results in the highest received signal strength (and optionally the strongest channel impulse response) of the reference signal received from the UE 604, or all received signal strengths and channel impulse responses for all receive beams 612 (allowing the positioning entity to determine the best receive beam 612). The base station 602 may additionally report the Rx-Tx time difference to the UE 604. The positioning entity can then estimate the location of the UE 604 based on the distance of the UE 604 to the base station 602, the AoA of the identified receive beams 612, and the known geographic location of the base station 602.

[0120]

[0135] FIG. 7 illustrates an example Long Term Evolution (LTE) Positioning Protocol (LPP) procedure 700 between a UE 704 and a location server (shown as a Location Management Function (LMF) 770) for performing a positioning operation. As shown in FIG. 7, positioning of the UE 704 is supported via an exchange of LPP messages between the UE 704 and the LMF 770. The LPP messages may be exchanged between the UE 704 and the LMF 770 via a serving base station (shown as a serving gNB 702) of the UE 704 and a core network (not shown). The LPP procedure 700 may be used to position the UE 704 to support various location-related services, such as navigation for the UE 704 (or for a user of the UE 704), for routing, or to provide an accurate location to a public safety answering point (PSAP) in connection with an emergency call from the UE 704 to the PSAP, or for some other reason. The LPP procedure 700 may also be referred to as a positioning session, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round trip time (RTT), enhanced cell identity (E-CID), etc.).

[0121]

[0136] Initially, the UE 704 may receive a request for its positioning capabilities (e.g., an LPP Capability Request message) from the LMF 770 at stage 710. At stage 720, the UE 704 provides the LMF 770 with its positioning capabilities for the LPP protocol by sending an LPP Capability Provision message to the LMF 770 indicating the positioning methods and characteristics of these positioning methods supported by the UE 704 using LPP. The capabilities indicated in the LPP Capability Provision message may, in some aspects, indicate the types of positioning that the UE 704 supports (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the UE 704's ability to support those types of positioning.

[0122]

[0137] Upon receipt of the LPP Provide Capabilities message in step 720, the LMF 770 determines to use a particular type of positioning method (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated type(s) of positioning that the UE 704 supports and determines a set of one or more Transmission / Reception Points (TRPs) from which the UE 704 should measure downlink positioning reference signals or to which the UE 704 should transmit uplink positioning reference signals. In step 730, the LMF 770 sends an LPP Provide Assistance Data message to the UE 704 identifying the set of TRPs.

[0123]

[0138] In some implementations, the Provide LPP Assistance Data message in stage 730 may be sent by the LMF 770 to the UE 704 in response to an LPP Request Assistance Data message (not shown in FIG. 7) sent by the UE 704 to the LMF 770. The Request LPP Assistance Data message may include an identifier of the serving TRP of the UE 704 and a request for Positioning Reference Signal (PRS) configuration of neighboring TRPs.

[0124]

[0139] At stage 740, the LMF 770 sends a request for location information to the UE 704. The request may be an LPP Request Location Information message. This message typically includes information elements that specify the location information type, the desired accuracy of the location estimate, and the response time (i.e., the desired latency). Note that a low latency requirement allows for a longer response time, while a high latency requirement requires a shorter response time. However, a long response time is referred to as a high latency, and a short response time is referred to as a low latency.

[0125]

[0140] It should be noted that in some implementations, for example, if the UE 704 sends a request for assistance data to the LMF 770 (e.g., in an LPP Request Assistance Data message not shown in FIG. 7) after receiving a request for location information in stage 740, the LPP Provide Assistance Data message sent in stage 730 may be sent after the LPP Request Location Information message in 740.

[0126]

[0141] In step 750, the UE 704 utilizes the assistance information received in step 730 and any additional data received in step 740 (e.g., desired location accuracy or maximum response time) to perform positioning operations (e.g., measuring DL-PRS, transmitting UL-PRS, etc.) for the selected positioning method.

[0127]

[0142] In stage 760, the UE 704 may send an LPP Provide Location Information message to the LMF 770 conveying the results of the measurements taken in stage 750 and (e.g., time of arrival (ToA), reference signal time difference (RSTD), receive-transmit (Rx-Tx), etc.) before or when any maximum response time (e.g., the maximum response time provided by the LMF 770 in stage 740) expires. The LPP Provide Location Information message in stage 760 may also include the time (or times) at which the positioning measurements were taken and the identity of the TRP(s) from which the positioning measurements were taken. Note that the time between the request for location information in 740 and the response in 760 is the "response time" and indicates the latency of the positioning session.

[0128]

[0143] The LMF 770 calculates an estimated location of the UE 704 using an appropriate positioning technique (e.g., DL-TDOA, RTT, E-CID, etc.) based at least in part on the measurements received in the LPP location information provision message at stage 760.

[0129]

[0144] It has been proposed to provide integrity information for RAT dependent positioning methods similar to how integrity information is provided for RAT independent positioning methods (e.g. GNSS based positioning methods). However, the content and details of such integrity information have not been agreed upon. Below are various definitions related to positioning integrity:

[0130]

[0145] Integrity is a measure of the confidence that can be placed in the accuracy of the information provided by a navigation system. It includes the ability of the system to provide timely warnings when the system should not be used for navigation. Integrity includes four main parameters: Alarm Limit (AL), Time to Alarm (TTA), Integrity Risk (IR), and Protection Level (PL).

[0131]

[0146] The AL is the maximum allowable magnitude of error in user position such that the system is usable for its intended use. If the position error in any dimension or combination of dimensions exceeds the AL, operation is unsafe and the system is declared unusable for its intended use to prevent loss of integrity. The AL is usually divided into the Horizontal Alarm Limit (HAL) and the Vertical Alarm Limit (VAL).

[0132]

[0147] TTA is the maximum allowable time to elapse from the onset of a positioning disturbance until the device issues an alarm.

[0133]

[0148] IR is the probability that the position error will exceed the protection level in the presence of an undetected fault event. It is the probability that a user will experience a position error greater than the protection level without an alarm being raised within the time specified to raise the alarm.

[0134]

[0149] The PL is a statistical error limit (also known as an integrity limit) calculated to ensure that the probability of an absolute position error exceeding a certain number is less than or equal to a target IR. Similar to the definition of AL, the PL is usually defined separately for the horizontal plane (Horizontal protection level (HPL)) and the vertical direction (Vertical protection level (VPL)).

[0135]

[0150] FIG. 8 is a diagram 800 illustrating various integrity parameters and events according to an aspect of the disclosure. As shown in FIG. 8, for example, there is a true position of the UE (i.e., the actual location of the UE) and an estimated position of the UE. The position error (PE) is the deviation of the estimated position from the true position (which is unknown). The area around the true position defined by the protection level (PL) is guaranteed to contain the true position. In normal (i.e., nominal) operation, the PE should be less than the PL (as in the example of FIG. 8). That is, the estimated position should be within the area defined by the PL.

[0136]

[0151] Beyond the area defined by the PL is the area defined by the Alarm Limit (AL). The AL is the maximum allowable error in the system before an alarm is triggered. It can be thought of as the required position accuracy of the system. A position estimate that is outside the PL is called an integrity event. Outside the PL but inside the AL, such an integrity event is called a Misleading Information (MI) event. Thus, an MI event is when PE is greater than the PL and less than the AL. Outside the AL, an integrity event is called a Hazardous Misleading Information (HMI) event. Thus, an HMI event is when PE is greater than the AL.

[0137]

[0152] Figure 9 is a diagram 900 showing different operating states in different integrity zones according to an aspect of the present disclosure. In the lower left quadrant, PL is smaller than AL, and thus the system is available. In the nominal operation (i.e., PE < PL), the location solution is available and operates safely without integrity events. When PE is greater than PL and smaller than AL (i.e., PE > PL and PE < AL), the location solution is available but includes a MI integrity event due to PE being greater than PL. However, since PE does not exceed AL, the system is still operating safely. When PE is greater than both PL and AL (i.e., PE > PL and PE > AL), the location solution is available but includes a HMI integrity event due to PE being greater than AL. The system is still declared to be safe (i.e., PL < AL), but it should not have been safe.

[0138]

[0153] In the upper half of diagram 900, the system is unavailable (i.e., PL > AL). The upper left quadrant represents a false alarm scenario where the system is unavailable (i.e., PE < PL and PE < AL). In such a scenario, the location solution is unavailable, but considering that PE is smaller than AL, it is a false alarm integrity event. In the system unavailable scenario (i.e., PE < PL and PE > AL), the location solution is unavailable, and the system operates as intended without integrity events when a PE greater than AL is properly detected. In the system unavailable and MI scenario (i.e., PE > PL and PE > AL), the location solution is unavailable and includes a MI integrity event (i.e., PE > PL).

[0139]

[0154] Generally, AL is specified by the application and PL is calculated by the user. Since PE is not observable, the determination to issue an alarm is made by comparing the specified AL with the calculated PL. When PL is greater than AL, the alarm is triggered. When PL is smaller than AL, the alarm is not triggered.

[0140]

[0155] 10 is a diagram 1000 of a probability distribution of a position error, according to an embodiment of the present disclosure. The position error probability distribution is assumed to be Gaussian, and the highlighted zone represents a target integrity risk (IR) designated for a particular application. Specifically, the IR is expressed as: P IR =P(|e|>kσ)

[0141]

[0156] For example, about 10 -7 P IR yields k equal to 5.33. FIG. 11 is a graph 1100 of the relationship between tail area probability and k, according to an embodiment of the present disclosure. As shown in FIG. -7 P IR yields k equal to 5.33.

[0142]

[0157] The protection level calculation converts range domain error bounds and failure probabilities into location domain error bounds at the desired integrity probability. The principle is to characterize the distribution of error sources in the observation domain, map the associated statistics to the location domain, and calculate the percentiles required to meet application-dependent integrity requirements.

[0143]

[0158] The basic steps can be summarized as follows: First, obtain a statistical characterization of the possible error (e.g., pseudorange sigma). Second, convert (using the UE's own geometry) the possible error sigma (σ) into the location domain. Sigma depends on the location threat model and can be provided in the assistance data. Third, σ x Calculate the PL of the current location solution based on the integrity risk, e.g.: xPL=k x σ x (x=H or V)

[0144]

number

[0145]

[0159] In addition to integrity events, there are threatening events. "Fault threatening events" are events that are inherent to the positioning system, i.e., caused by a malfunction of one of the elements of the positioning system (e.g., software and / or hardware malfunction). "Non-fault threatening events" are events that are not threatening caused by a malfunction of the positioning system. Non-fault conditions are typically when the positioning system inputs are erroneous, e.g., outside of critical ionosphere and troposphere conditions, or when there is a GNSS satellite failure.

[0146]

[0160] To achieve positioning integrity, it is important to monitor potential events in the positioning system. Integrity monitors are used to detect potential events occurring more frequently than is acceptable to meet a target integrity risk (TIR). Information derived from the integrity monitors is used to mitigate the impact of potential events on the positioning solution, for example, by transmitting integrity parameters to enable the UE to adjust its calculated protection level (PL) or to declare the system unavailable. The resulting integrity messages (e.g., warning flags, error limits, etc.) can be signaled as assistance information between the LMF and the UE.

[0147]

[0161] As an example, an unplanned satellite orbital maneuver may be taking place, causing the true orbit to differ from the broadcast orbit in the GNSS-provided ephemeris. The LMF may provide the UE with a real-time updated estimate of this orbit error (in the GNSS State Space Representation (SSR) Assistance Data Element), and these messages may be used to correct a large portion of the error. To maintain integrity, the remaining orbit error after corrections have been applied should be below some specified integrity limit. If the network determines that it cannot track an orbit error, such that the corrected value is guaranteed to be within the integrity limit (up to some residual risk), it issues a Do Not Use (DNU) flag for that satellite as part of the integrity assistance data message. Depending on the network implementation, the achievable limit on the orbit error may be variable, depending, for example, on how many reference stations track that satellite. For this reason, the limit may be dynamic and is transmitted with the integrity assistance information. The network (by definition) cannot detect orbit errors smaller than the reported limit, and therefore users should assume that such errors may have occurred undetected.

[0148]

[0162] Referring more specifically to the integrity limits, integrity ensures that the system's errors are bounded with a given probability. The integrity limits provide a statistical distribution of the residual errors associated with the GNSS positioning corrections (e.g., real-time kinematic (RTK), SSR, etc.). The integrity limits are used to statistically bound the residual errors after the positioning corrections are applied. Referring again to FIG. 10, diagram 1000 shows the calculated error limits for maximum IR (labeled "Error Limit") and maximum residual risk.

[0149]

[0163] The governing equation for integrity is that the sum of all integrity risks should be less than the TIR. The integrity risk is the probability of an impact on integrity under nominal conditions, P(I nom ), the sum of the probabilities of the effects of each of the threatened events P(I FE) can be thought of as:

[0150]

number

[0151]

[0164] When a DNU flag is not issued, the network is affirmatively asserting that the probability of an unflagged occurrence of an error exceeding the corresponding limit is below a specified threshold, specifically: P(Integrity Event) = P(Error > Limit | NOT DNU) ≤ Threshold

[0152]

[0165] This can be decomposed into the fault and non-fault cases as follows: P(integrity event) = P(error > limit | NOT DNU, failure) + P(error > limit | NOT DNU, no failure).

[0153]

[0166] Each of these cases can be assigned a probability bound as follows: P(error > margin | NOT DNU, failure) ≤ residual risk P(error > limit | NOT DNU, no failures) ≤ IRallocation

[0154]

[0167] For integrity operation, the network (assistance data) ensures that: P(error > limit│NOT DNU) ≦ residual risk + IRallocation

[0155]

[0168] The above formula is for all values ​​of IRallocation in the range IRminimum<=IRallocation<=IRmaximum and for all errors (DNU=false) for which corresponding completeness support data is available. The above formula decomposes the risk into a fixed part (i.e., residual risk) provided in the support data, and a variable component (i.e., IRallocation) that scales with the bounds.

[0156]

[0169] The completeness limit (or error bound) is calculated as follows: Limit=Average+K * stdDev, K=normInv(IRallocation / 2) (i.e., the nominal inversion of (IRallocation / 2)), and IRminimum≦IRallocation≦IRmaximum, where "mean" is the average value for this particular error (i.e. the central number of a finite set of numbers), "stdDev" is the standard deviation for this particular error, and IRminimum and IRmaximum are the minimum and maximum IRs, respectively, for which the assistance data can be used. The UE can choose any value of IRallocation (and therefore K) as long as it is within the specified range. The error is the difference between the true value of the GNSS error and its value estimated and provided in the corresponding assistance data.

[0157]

[0170] Integrity information may be provided and reported via the LPP. For example, an LPP Location Information Request message (as in step 740 of FIG. 7) may include integrity requirements (e.g., TIR, AL, TTA, etc.). The integrity information may be included in common positioning information elements (IEs). In response, an LPP Location Information Provide message (as in step 760 of FIG. 7) may include a determined (i.e., UE-determined) PL, referred to as Mode 1, or an integrity status (e.g., secure, unsecure, etc.), referred to as Mode 2 (also determined by the UE).

[0158]

[0171] There are different categories of integrity assistance data: (1) integrity limit, (2) residual risk, (3) correlation time, (4) alert, and (5) validity time. Integrity limit provides a statistical distribution (i.e., probability distribution) of the residual error associated with the GNSS positioning corrections (e.g., RTK, SSR, etc.). Integrity limit is used to statistically bound the residual error after the positioning corrections are applied. Residual risk provides an additional probability of failure in addition to the probability implied by the limit and selection of IRallocation. Residual risk is decomposed into failure and no-failure cases. In principle, any allocation of risk between residual risk and IRallocation is acceptable as long as P(error > limit) <= residual risk + IRallocation.

[0159]

[0172] The integrity correlation time provides the minimum time interval during which two measurements of the same parameter can be considered independent of each other. This allows the use of time-based estimation techniques (e.g., Kalman filtering, which assumes the dynamics of the error in time) in addition to snapshot-based techniques. With regard to alarms, the DNU flag indicates that the corresponding assistance data is not suitable for the purposes of computing integrity. If no DNU flag is issued, the corresponding assistance data may be used for the purposes of computing integrity. With regard to validity time, the integrity assistance data is valid within [epoch time; epoch time + validity period].

[0160]

[0173] 12A and 12B are table 1200 illustrating a mapping of integrity parameters to GNSS assistance data, according to an aspect of the disclosure. As shown in table 1200, various Assistance Data IEs (e.g., "GNSS-SSR-ClockCorrections") may be provided to the UE for various error sources (e.g., "Clock"). The Assistance Data IEs may include marginal mean and standard deviation ("StdDev"), as well as additional IEs for residual risk and time correlation.

[0161]

[0174] Currently, integrity information may be provided to the UE for RAT-independent positioning methods, such as GNSS-based positioning methods. The present disclosure proposes providing integrity information to the UE for RAT-dependent positioning methods. The parameters may be provided to the UE in assistance data (e.g., at step 730 of FIG. 7).

[0162]

[0175] FIG. 13 illustrates an example "NR-PositionCalculationAssistance" information element (IE) 1300 according to an aspect of the disclosure. The "NR-PositionCalculationAssistance" 1300 is used by a location server (e.g., LMF 270) to provide assistance data to enable RAT-dependent UE-based downlink positioning. For example, the location server may provide the "NR-PositionCalculationAssistance" 1300 in stage 730 of FIG. 7. The "nr-TRP-LocationInfo" field provides location coordinates of the antenna reference point of the TRP. The "nr-DL-PRS-BeamInfo" field provides spatial directions of DL-PRS resources for the TRP.

[0163]

[0176] With specific reference to the assistance data provided for DL-AoD positioning, for TRP beam / antenna information to be optionally provided by the LMF to the UE for UE-based DL-AoD, the LMF provides (e.g., in the assistance data in step 730 of FIG. 7) a quantized version of the relative power (e.g., RSRP) between PRS resources per angle per TRP. The relative power is defined in terms of the peak power at each angle. For each angle, the UE reports at least two PRS resources. Note that the peak power per angle is not provided.

[0164]

[0177] Regarding support of AoD measurements with expected uncertainty windows for both UE-B DL-AoD and UE-A DL-AoD, the following is currently supported: First, a range(s) of expected angle values ​​(of expected azimuth and zenith angle values) and an indication of the uncertainty are signaled by the LMF to the UE. Second, the expected angle and the type of uncertainty can be requested by the UE among the following options: First, a range(s) of expected DL-AoD / ZoD values ​​(of expected DL-AoD / ZoD values) and an indication of the uncertainty are signaled by the LMF to the UE. Second, a range(s) of expected DL-AoA / ZoA values ​​(of expected DL-AoA / ZoA values) and an indication of the uncertainty are signaled by the LMF to the UE.

[0165]

[0178] For UE-based positioning, it is agreed to support the following options for LOS and / or non-line-of-site (NLOS) indicators in the positioning assistance data: As a first option, if the LMF can provide different values ​​for the LOS / NLOS indicators for different DL-PRS resources of one TRP, the LMF can associate a UE-based LOS / NLOS indicator with each DL-PRS resource of each TRP. As a second option, the LMF can associate a UE-based LOS / NLOS indicator with each TRP. In the first option, one LOS / NLOS indicator is associated with one DL-PRS resource.

[0166]

[0179] With further reference to the LOS / NLOS indicators, it has been agreed to support two options for the value of the LOS / NLOS indicator reported by the UE or TRP: (1) soft values ​​and (2) hard values. The soft values ​​are selected from the set {0,0.1,...,0.9,1} (in increments of 0.1) and the hard values ​​are selected from the set {0,1]}. These values ​​correspond to the likelihood that the measured PRS resource follows an LOS path, with a value of 1 corresponding to LOS and a value of 0 corresponding to NLOS.

[0167]

[0180] As mentioned above, the present disclosure proposes to provide the UE with the integrity information of assistance data for RAT-dependent positioning methods. For example, the LMF may provide the integrity information for assistance data related to DL-AoD positioning procedures. Thus, as the first assistance data parameter for which the LMF may provide the integrity information, specifically the boresight direction(s) of the PRS resource, the LMF may provide the probability distribution (e.g., mean and standard deviation) of the error of the boresight direction. If the provided mean and standard deviation are associated with a PRS resource set, these values ​​will correspond to all PRS resources in the PRS resource set. Similarly, if the mean and standard deviation are associated with a TRP, these values ​​will correspond to all PRS resources of all PRS resource sets of the TRP.

[0168]

[0181] As a second assistance data parameter for which the LMF can provide completeness information, in particular beam information per angle (i.e., information for one or more beams at each given angle, such as the relative power difference between two or more beams), the LMF can provide a probability distribution (e.g., mean and standard deviation) of the error of the beam information per angle. A different mean and standard deviation may be provided for each angle or group of angles. An interval (or intervals) may be defined, in which in each angle interval a different mean and standard deviation is applied. An example would be one interval around the boresight direction, where one mean and standard deviation is applied, and another interval (and a different mean and standard deviation is applied) for all remaining angles outside the area around the boresight direction. Alternatively, a single mean and standard deviation that applies to all provided angles may be provided.

[0169]

[0182] As a third assistance data parameter for which the LMF may provide completeness information, in particular the predicted AoD and the predicted AoD uncertainty parameters, the LMF may provide a probability distribution (e.g., mean and standard deviation) of the error in the predicted AoD and the predicted AoD uncertainty.

[0170]

[0183] The LMF may also provide integrity information for assistance data related to Timing Error Groups (TEGs). TEGs are used to describe the internal timing error of the UE. From a signal transmission perspective, there is a time delay from when the digital signal is generated in baseband to when the RF signal is transmitted from the transmit antenna. To assist positioning, the UE / TRP may perform internal calibration / compensation of transmit time delay for DL-PRS / UL-SRS transmission, which may also include calibration / compensation of relative time delay between different RF chains in the same UE / TRP. This compensation may also take into account the offset of the phase center of the transmit antenna relative to the center of the physical antenna. However, the calibration may not be perfect. The remaining transmit time delay after calibration, or the transmit time delay that is not calibrated, is defined as the "transmit timing error" or "Tx timing error". The UE Tx-TEG is associated with the transmission of one or more UL-PRS resources for positioning purposes, which have a Tx timing error that is within a certain range (e.g., within a threshold of each other).

[0171]

[0184] Thus, as a fourth assistance data parameter for which the LMF may provide integrity information, specifically the Tx-TEG margin, the LMF may provide a probability distribution (eg, mean and standard deviation) of the error of the Tx-TEG margin.

[0172]

[0185] The LMF may also provide integrity information for assistance data related to the LOS / NLOS flags, i.e., as a fifth assistance data parameter for which the LMF may provide integrity information, specifically the LOS / NLOS flags associated with each PRS resource (or TRP), the LMF may provide a probability distribution (e.g., mean and standard deviation) of the error of the LOS / NLOS flags.

[0173]

[0186] The LMF may also provide completeness information for assistance data related to nested TRP location structures. There are four reference points defined in the TRP location information structure: (1) one reference point for different positioning frequency layers (PFLs), (2) one reference point for TRP locations within a PFL, (3) a reference point for PRS resource sets of TRPs within a TRP of a PFL, and (4) a reference point for PRS resources of PRS resource sets for each PRS resource set of a TRP of a PFL.

[0174]

[0187] 14 illustrates various TRP location information IEs 1400 that may be provided to a UE in assistance data according to an aspect of the disclosure. These IEs may be used to convey the reference points described above.

[0175]

[0188] Thus, as a sixth assistance data parameter for which the LMF can provide completeness information, the LMF can provide a probability distribution (e.g., mean and standard deviation) for the error of one or more of the reference points described above.

[0176]

[0189] 15 illustrates an example method 1500 of wireless communication according to an aspect of the disclosure. In one aspect, the method 1500 may be performed by a UE (e.g., any of the UEs described herein).

[0177]

[0190] In 1510, the UE receives from a location server (e.g., LMF 270) one or more positioning parameters for enabling the UE to perform a RAT-dependent positioning procedure involving at least one TRP (e.g., as in steps 730 and / or 740 of FIG. 7), the one or more positioning parameters including a boresight direction associated with a PRS resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with the location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof. In one aspect, operation 1510 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which may be considered as a means for performing this operation.

[0178]

[0191] At 1520, the UE receives one or more integrity parameters related to the one or more positioning parameters from the location server (e.g., at steps 730 and / or 740 of FIG. 7). In one aspect, operation 1520 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered a means for performing this operation.

[0179]

[0192] At 1530, the UE determines an integrity indication for the one or more positioning parameters based on the one or more integrity parameters. In one aspect, operation 1530 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered a means for performing this operation.

[0180]

[0193] Although not shown in FIG. 15, it should be noted that method 1500 may further include sending an integrity indication for one or more positioning parameters to the location server, for example, in an LPP location information provision message (e.g., as in step 760 of FIG. 7).

[0181]

[0194] 16 illustrates an example method 1600 of communication according to an aspect of the disclosure. In one aspect, the method 1600 may be performed by a location server (e.g., the LMF 270).

[0182]

[0195] In 1610, the location server transmits one or more positioning parameters for a RAT-dependent positioning procedure involving at least one TRP to the UE (e.g., any of the UEs described herein) (e.g., as in steps 730 and / or 740 of FIG. 7), the one or more positioning parameters including a boresight direction associated with a PRS resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with the location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof. In one aspect, operation 1610 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as a means for performing this operation.

[0183]

[0196] At 1620, the location server transmits (e.g., at steps 730 and / or 740 of FIG. 7) one or more integrity parameters related to the one or more positioning parameters to the UE. In one aspect, operation 1620 may be performed by one or more network transceivers 390, one or more processors 394, memories 396, and / or positioning components 398, any or all of which may be considered a means for performing this operation.

[0184]

[0197] Although not shown in Figure 16, it should be noted that method 1600 may further include receiving an integrity indication for the one or more positioning parameters from the UE (e.g., as in step 760 of Figure 7), e.g., in an LPP Provide Location Information message. Additionally, method 1600 may further include sending the integrity indication to an entity requesting the location of the UE, such as a third party client, a PSAP, another network entity (e.g., AMF), etc.

[0185]

[0198] As can be appreciated, a technical advantage of methods 1500 and 1600 is improved positioning performance through the determination of the completeness of positioning parameters provided in the Assistance Data.

[0186]

[0199] In the above detailed description, it can be seen that in each example, various features are grouped together. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly stated in each clause. Rather, various aspects of the disclosure may include fewer features than all features of each disclosed exemplary clause. Thus, the following clauses should be considered to be incorporated in the description, and each clause may stand alone as a separate example. Although each dependent clause may refer to a specific combination with one of the other clauses in the clause, the aspect(s) of the dependent clause are not limited to that specific combination. It will be understood that other exemplary clauses may also include combinations of the aspect(s) of the dependent clause with the subject matter of any other dependent clause or independent clause, or any combination of features with other dependent clauses and independent clauses. Various aspects disclosed herein expressly include these combinations, unless it is expressly expressed or can be easily inferred that a particular combination is not intended (e.g., inconsistent aspects, such as defining an element as both an electrical insulator and an electrical conductor). It is further contemplated that aspects of a clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0187]

[0200] The following numbered clauses describe example implementations.

[0188]

[0201] Clause 1. A method of wireless communications performed by a user equipment (UE), comprising: receiving from a location server one or more positioning parameters to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), the one or more positioning parameters comprising a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; receiving from the location server one or more integrity parameters related to the one or more positioning parameters; and determining an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0189]

[0202] Clause 2. The method of clause 1, wherein the one or more integrity parameters comprise a probability distribution for the error of the one or more positioning parameters.

[0190]

[0203] Clause 3. The method of clause 2, wherein the probability distribution comprises a mean and a standard deviation.

[0191]

[0204] Clause 4. The method of any one of clauses 1 to 3, wherein the one or more integrity parameters include a probability distribution for an error in the boresight direction of the PRS resource.

[0192]

[0205] Clause 5. The method of clause 4, wherein a probability distribution is associated with a PRS resource set that includes the PRS resource, the probability distribution applying to all PRS resources in the PRS resource set.

[0193]

[0206] Clause 6. The method of clause 4 or 5, wherein a probability distribution is associated with at least one TRP, the probability distribution applying to all PRS resources of all PRS resource sets of the at least one TRP.

[0194]

[0207] Clause 7. The method of any of clauses 1 to 6, wherein the one or more completeness parameters include a probability distribution for the error of the beam information per angle.

[0195]

[0208] Clause 8. The method of clause 7, wherein the probability distribution fits to an angular interval of a plurality of angular intervals of the beam information for each angle, and a different probability distribution fits to each angular interval of the plurality of angular intervals.

[0196]

[0209] Clause 9. The method of clause 7 or 8, wherein the beam information for each angle defines a plurality of angle intervals, and the probability distribution applies to all angle intervals of the plurality of angle intervals.

[0197]

[0210] Clause 10. The method of any of clauses 1 to 9, wherein the predicted angle comprises a predicted angle of departure (AoD) and a predicted AoD uncertainty parameter, and the one or more completeness parameters comprise a probability distribution for error in the predicted AoD and the predicted AoD uncertainty parameter.

[0198]

[0211] Clause 11. The method of any of clauses 1 to 10, wherein the one or more integrity parameters include a probability distribution for the error of the Tx-TEG margin.

[0199]

[0212] Clause 12. A method according to any one of clauses 1 to 11, wherein the LOS information includes a LOS and / or non-line-of-sight (NLOS) flag associated with each PRS resource or each TRP indicated to the UE, and the one or more integrity parameters include a probability distribution for an error in the LOS flag and / or the NLOS flag.

[0200]

[0213] Clause 13. The method of any of clauses 1 to 12, wherein the one or more completeness parameters include a probability distribution for the error of the reference point information.

[0201]

[0214] Clause 14. The method of clause 13, wherein the reference point information is about a positioning frequency layer (PFL), a location of at least one TRP within the PFL, a PRS resource set of at least one TRP, a PRS resource of the PRS resource set, or any combination thereof.

[0202]

[0215] Clause 15. A method according to any one of clauses 1 to 14, wherein the one or more integrity parameters are received in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Location Information Request messages.

[0203]

[0216] Clause 16. A method according to any one of clauses 1 to 15, wherein one or more positioning parameters are received in one or more LPP Provide Assistance Data messages.

[0204]

[0217] Clause 17. The method of any one of clauses 1 to 16, wherein the RAT dependent positioning procedure comprises a Downlink Angle of Departure (DL-AoD) positioning procedure.

[0205]

[0218] Clause 18. The method of any of clauses 1 to 17, further comprising sending an integrity indication for one or more positioning parameters to the location server.

[0206]

[0219] Clause 19. The method of clause 18, wherein the integrity indication comprises a protection level (PL) determined by the UE, or wherein the integrity indication comprises an integrity status of one or more positioning parameters.

[0207]

[0220] Clause 20. The method of clause 18 or 19, wherein the integrity indication is sent in one or more LPP Location Information Provide messages.

[0208]

[0221] Clause 21. A method of communication implemented by a location server, comprising: transmitting one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmit / receive point (TRP) to a user equipment (UE), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line of sight (LOS) information associated with the PRS resource, or any combination thereof; and transmitting one or more integrity parameters related to the one or more positioning parameters to the UE.

[0209]

[0222] Clause 22. The method of clause 21, further comprising receiving an integrity indication for one or more positioning parameters from the UE, the integrity indication being determined based on the one or more integrity parameters.

[0210]

[0223] Clause 23. The method of clause 22, wherein the integrity indication comprises a protection level (PL) determined by the UE, or wherein the integrity indication comprises an integrity status of one or more positioning parameters.

[0211]

[0224] Clause 24. The method of clause 22 or 23, wherein one or more integrity parameters are sent in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Assistance Data Provide messages or one or more LPP Location Information Request messages, and the integrity indication is received in one or more LPP Location Information Provide messages.

[0212]

[0225] Clause 25. The method of any of clauses 22 to 24, further comprising sending an integrity indication to an entity requesting the location of the UE.

[0213]

[0226] Clause 26. A device comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor receives, via the at least one transceiver, one or more positioning parameters from a location server for enabling a UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), the one or more positioning parameters including a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, a positioning reference signal (PRS) resource associated with ... and a positioning reference signal (PRS) resource associated with the at least one TRP. A user equipment (UE) configured to receive, via at least one transceiver, one or more integrity parameters related to one or more positioning parameters from a location server, the one or more integrity parameters including beam information per angle, an expected angle associated with a PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof, and to determine an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0214]

[0227] Clause 27. The UE of clause 26, wherein the one or more integrity parameters comprise a probability distribution for the error of the one or more positioning parameters.

[0215]

[0228] Clause 28. The UE of clause 27, wherein the probability distribution comprises a mean and a standard deviation.

[0216]

[0229] Clause 29. A UE as described in any of clauses 26 to 28, wherein the one or more integrity parameters include a probability distribution for an error in the boresight direction of the PRS resource.

[0217]

[0230] Clause 30. The UE of clause 29, wherein a probability distribution is associated with a PRS resource set that includes the PRS resource, the probability distribution applying to all PRS resources in the PRS resource set.

[0218]

[0231] Clause 31. The UE of clause 29 or 30, wherein a probability distribution is associated with at least one TRP, the probability distribution applying to all PRS resources of all PRS resource sets of the at least one TRP.

[0219]

[0232] Clause 32. A UE as described in any of clauses 26 to 31, wherein the one or more completeness parameters include a probability distribution for an error in the beam information per angle.

[0220]

[0233] Clause 33. The UE of clause 32, wherein a probability distribution applies to an angular interval of a plurality of angular intervals of the beam information for each angle, and a different probability distribution applies to each angular interval of the plurality of angular intervals.

[0221]

[0234] Clause 34. The UE of clause 32 or 33, wherein the beam information for each angle defines a plurality of angle intervals, and the probability distribution applies to all angle intervals of the plurality of angle intervals.

[0222]

[0235] Clause 35. A UE as described in any of clauses 26 to 34, wherein the predicted angle includes a predicted angle of departure (AoD) and a predicted AoD uncertainty parameter, and the one or more completeness parameters include a probability distribution for an error in the predicted AoD and the predicted AoD uncertainty parameter.

[0223]

[0236] Clause 36. The UE of any of clauses 26 to 35, wherein the one or more integrity parameters include a probability distribution for an error in the Tx-TEG margin.

[0224]

[0237] Clause 37. A UE as described in any of clauses 26 to 36, wherein the LOS information includes a LOS flag and / or a non-line-of-sight (NLOS) flag associated with each PRS resource or each TRP indicated to the UE, and the one or more integrity parameters include a probability distribution for an error in the LOS flag and / or the NLOS flag.

[0225]

[0238] Clause 38. A UE as described in any of clauses 26 to 37, wherein the one or more integrity parameters include a probability distribution for an error in the reference point information.

[0226]

[0239] Clause 39. The UE of clause 38, wherein the reference point information is about a positioning frequency layer (PFL), a location of at least one TRP within the PFL, a PRS resource set of at least one TRP, a PRS resource of the PRS resource set, or any combination thereof.

[0227]

[0240] Clause 40. The UE of any of clauses 26 to 39, wherein the one or more integrity parameters are received in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Location Information Request messages.

[0228]

[0241] Clause 41. A UE according to any of clauses 26 to 40, wherein the one or more positioning parameters are received in one or more LPP Provide Assistance Data messages.

[0229]

[0242] Clause 42. A UE as described in any of clauses 26 to 41, wherein the RAT dependent positioning procedure includes a Downlink Angle of Departure (DL-AoD) positioning procedure.

[0230]

[0243] Clause 43. A UE as described in any of clauses 26 to 42, wherein the at least one processor is further configured to transmit, via the at least one transceiver, an integrity indication for one or more positioning parameters to the location server.

[0231]

[0244] Clause 44. The UE of clause 43, wherein the integrity indication comprises a protection level (PL) determined by the UE, or wherein the integrity indication comprises an integrity status of one or more positioning parameters.

[0232]

[0245] Clause 45. The UE of clause 43 or 44, wherein the integrity indication is sent in one or more LPP Location Information Provide messages.

[0233]

[0246] Clause 46. A location server comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to: transmit, via the at least one transceiver, one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP) to a user equipment (UE), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; and transmit, via the at least one transceiver, one or more integrity parameters related to the one or more positioning parameters to the UE.

[0234]

[0247] Clause 47. The location server of clause 46, further configured such that the at least one processor receives, via the at least one transceiver, from the UE, an integrity indication for one or more positioning parameters, and the integrity indication is determined based on the one or more integrity parameters.

[0235]

[0248] Clause 48. The location server of clause 47, wherein the integrity indication comprises a protection level (PL) determined by the UE, or wherein the integrity indication comprises an integrity status of one or more positioning parameters.

[0236]

[0249] Clause 49. A location server as described in clause 47 or 48, wherein one or more integrity parameters are sent in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Assistance Data Provide messages or one or more LPP Location Information Request messages, and an integrity indication is received in one or more LPP Location Information Provide messages.

[0237]

[0250] Clause 50. A location server according to any of clauses 47 to 49, wherein the at least one processor is further configured to transmit, via the at least one transceiver, an integrity indication to an entity requesting the location of the UE.

[0238]

[0251] Clause 51. A user equipment (UE), comprising: means for receiving from a location server one or more positioning parameters to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), the one or more positioning parameters including a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; means for receiving from the location server one or more integrity parameters related to the one or more positioning parameters; and means for determining an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0239]

[0252] Clause 52. The UE of clause 51, wherein the one or more integrity parameters include a probability distribution for an error in the one or more positioning parameters.

[0240]

[0253] Clause 53. The UE of clause 52, wherein the probability distribution comprises a mean and a standard deviation.

[0241]

[0254] Clause 54. A UE as described in any of clauses 51 to 53, wherein the one or more integrity parameters include a probability distribution for an error in the boresight direction of the PRS resource.

[0242]

[0255] Clause 55. The UE of clause 54, wherein a probability distribution is associated with a PRS resource set that includes the PRS resource, the probability distribution applying to all PRS resources in the PRS resource set.

[0243]

[0256] Clause 56. The UE of clause 54 or 55, wherein a probability distribution is associated with at least one TRP, the probability distribution applying to all PRS resources of all PRS resource sets of the at least one TRP.

[0244]

[0257] Clause 57. A UE as described in any of clauses 51 to 56, wherein the one or more completeness parameters include a probability distribution for an error in the beam information per angle.

[0245]

[0258] Clause 58. The UE of clause 57, wherein a probability distribution applies to an angular interval of a plurality of angular intervals of the beam information for each angle, and a different probability distribution applies to each angular interval of the plurality of angular intervals.

[0246]

[0259] Clause 59. The UE of clause 57 or 58, wherein the beam information for each angle defines a plurality of angle intervals, and the probability distribution applies to all angle intervals of the plurality of angle intervals.

[0247]

[0260] Clause 60. A UE as described in any of clauses 51 to 59, wherein the predicted angle includes a predicted angle of departure (AoD) and a predicted AoD uncertainty parameter, and the one or more completeness parameters include a probability distribution for an error in the predicted AoD and the predicted AoD uncertainty parameter.

[0248]

[0261] Clause 61. The UE of any of clauses 51 to 60, wherein the one or more integrity parameters include a probability distribution for an error in the Tx-TEG margin.

[0249]

[0262] Clause 62. A UE as described in any of clauses 51 to 61, wherein the LOS information includes a LOS flag and / or a non-line-of-sight (NLOS) flag associated with each PRS resource or each TRP indicated to the UE, and the one or more integrity parameters include a probability distribution for an error in the LOS flag and / or the NLOS flag.

[0250]

[0263] Clause 63. A UE as described in any of clauses 51 to 62, wherein the one or more integrity parameters include a probability distribution for an error in the reference point information.

[0251]

[0264] Clause 64. The UE of clause 63, wherein the reference point information is about a positioning frequency layer (PFL), a location of at least one TRP within the PFL, a PRS resource set of at least one TRP, a PRS resource of the PRS resource set, or any combination thereof.

[0252]

[0265] Clause 65. The UE of any of clauses 51 to 64, wherein the one or more integrity parameters are received in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Location Information Request messages.

[0253]

[0266] Clause 66. A UE according to any of clauses 51 to 65, wherein the one or more positioning parameters are received in one or more LPP Provide Assistance Data messages.

[0254]

[0267] Clause 67. The UE according to any of clauses 51 to 66, wherein the RAT dependent positioning procedure includes a Downlink Angle of Departure (DL-AoD) positioning procedure.

[0255]

[0268] Clause 68. A UE as claimed in any of clauses 51 to 67, further comprising means for transmitting an integrity indication for one or more positioning parameters to the location server.

[0256]

[0269] Clause 69. The UE of clause 68, wherein the integrity indication comprises a protection level (PL) determined by the UE, or wherein the integrity indication comprises an integrity status of one or more positioning parameters.

[0257]

[0270] Clause 70. The UE of clause 68 or 69, wherein the integrity indication is sent in one or more LPP Location Information Provide messages.

[0258]

[0271] Clause 71. A location server comprising: means for transmitting one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP) to a user equipment (UE), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; and means for transmitting one or more integrity parameters related to the one or more positioning parameters to the UE.

[0259]

[0272] Clause 72. The location server of clause 71, further comprising receiving an integrity indication for one or more positioning parameters from the UE, the integrity indication being determined based on the one or more integrity parameters.

[0260]

[0273] Clause 73. The location server of clause 72, wherein the integrity indication comprises a protection level (PL) determined by the UE, or wherein the integrity indication comprises an integrity status of one or more positioning parameters.

[0261]

[0274] Clause 74. The location server of clause 72 or 73, wherein one or more integrity parameters are sent in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Assistance Data Provide messages or one or more LPP Location Information Request messages, and the integrity indication is received in one or more LPP Location Information Provide messages.

[0262]

[0275] Clause 75. The location server according to any of clauses 72 to 74, further comprising means for sending an integrity indication to an entity requesting the location of the UE.

[0263]

[0276] Clause 76. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to receive from a location server one or more positioning parameters to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), the one or more positioning parameters including a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; receive from the location server one or more integrity parameters related to the one or more positioning parameters; and determine an integrity indication for the one or more positioning parameters based on the one or more integrity parameters.

[0264]

[0277] Clause 77. The non-transitory computer-readable medium of clause 76, wherein the one or more integrity parameters include a probability distribution for an error in the one or more positioning parameters.

[0265]

[0278] Clause 78. The non-transitory computer-readable medium of clause 77, wherein the probability distribution comprises a mean and a standard deviation.

[0266]

[0279] Clause 79. The non-transitory computer-readable medium of any of clauses 76-78, wherein the one or more integrity parameters include a probability distribution for an error in a boresight direction of a PRS resource.

[0267]

[0280] Clause 80. The non-transitory computer-readable medium of clause 79, wherein a probability distribution is associated with a PRS resource set that includes the PRS resource, the probability distribution applying to all PRS resources in the PRS resource set.

[0268]

[0281] Clause 81. The non-transitory computer-readable medium of clause 79 or 80, wherein a probability distribution is associated with at least one TRP, the probability distribution applying to all PRS resources of all PRS resource sets of the at least one TRP.

[0269]

[0282] Clause 82. A non-transitory computer-readable medium according to any of clauses 76 to 81, wherein the one or more completeness parameters include a probability distribution for an error in the beam information per angle.

[0270]

[0283] Clause 83. The non-transitory computer readable medium of clause 82, wherein a probability distribution applies to one angular interval of a plurality of angular intervals of the beam information for each angle, and a different probability distribution applies to each angular interval of the plurality of angular intervals.

[0271]

[0284] Clause 84. The non-transitory computer-readable medium of clause 82 or 83, wherein the beam information for each angle defines a plurality of angle intervals, and the probability distribution applies to all angle intervals of the plurality of angle intervals.

[0272]

[0285] Clause 85. A non-transitory computer-readable medium according to any of clauses 76 to 84, wherein the predicted angle comprises a predicted angle of departure (AoD) and a predicted AoD uncertainty parameter, and the one or more completeness parameters comprise a probability distribution for an error in the predicted AoD and the predicted AoD uncertainty parameter.

[0273]

[0286] Clause 86. The non-transitory computer-readable medium of any of clauses 76 to 85, wherein the one or more integrity parameters include a probability distribution for an error in the Tx-TEG margin.

[0274]

[0287] Clause 87. A non-transitory computer-readable medium according to any of clauses 76 to 86, wherein the LOS information includes an LOS flag and / or a non-line-of-sight (NLOS) flag associated with each PRS resource or each TRP indicated to the UE, and the one or more integrity parameters include a probability distribution for an error in the LOS flag and / or the NLOS flag.

[0275]

[0288] Clause 88. A non-transitory computer-readable medium according to any of clauses 76 to 87, wherein the one or more integrity parameters include a probability distribution for an error in the reference point information.

[0276]

[0289] Clause 89. The non-transitory computer-readable medium of clause 88, wherein the reference point information is about a positioning frequency layer (PFL), a location of at least one TRP within the PFL, a PRS resource set of at least one TRP, a PRS resource of the PRS resource set, or any combination thereof.

[0277]

[0290] Clause 90. The non-transitory computer-readable medium of any of clauses 76-89, wherein the one or more integrity parameters are received in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Location Information Request messages.

[0278]

[0291] Clause 91. The non-transitory computer-readable medium of any of clauses 76-90, wherein the one or more positioning parameters are received in one or more LPP Assistance Data Provide messages.

[0279]

[0292] Clause 92. The non-transitory computer-readable medium of any of clauses 76 to 91, wherein the RAT-dependent positioning procedure includes a Downlink Angle of Departure (DL-AoD) positioning procedure.

[0280]

[0293] Clause 93. A non-transitory computer-readable medium according to any of clauses 76 to 92, further comprising computer-executable instructions that, when executed by the UE, cause the UE to send an integrity indication for one or more positioning parameters to a location server.

[0281]

[0294] Clause 94. The non-transitory computer-readable medium of clause 93, wherein the integrity indication includes a protection level (PL) determined by the UE, or wherein the integrity indication includes an integrity status of one or more positioning parameters.

[0282]

[0295] Clause 95. The non-transitory computer-readable medium of clause 93 or 94, wherein the integrity indication is transmitted in one or more LPP location information provide messages.

[0283]

[0296] Clause 96. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to transmit one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmitting / receiving point (TRP) to a user equipment (UE), the one or more positioning parameters including a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, beam information per angle associated with the at least one TRP, an expected angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof, and cause the location server to transmit one or more integrity parameters related to the one or more positioning parameters to the UE.

[0284]

[0297] Clause 97. The non-transitory computer-readable medium of clause 96, further comprising receiving an integrity indication for one or more positioning parameters from the UE, the integrity indication being determined based on the one or more integrity parameters.

[0285]

[0298] Clause 98. The non-transitory computer-readable medium of clause 97, wherein the integrity indication includes a protection level (PL) determined by the UE, or wherein the integrity indication includes an integrity status of one or more positioning parameters.

[0286]

[0299] Clause 99. The non-transitory computer-readable medium of clause 97 or 98, wherein the one or more integrity parameters are transmitted in one or more Long Term Evolution (LTE) Positioning Procedure (LPP) Assistance Data Provide messages or one or more LPP Location Information Request messages, and the integrity indication is received in one or more LPP Location Information Provide messages.

[0287]

[0300] Clause 100. The non-transitory computer-readable medium of any of clauses 97-99, further comprising computer-executable instructions that, when executed by the location server, cause the location server to send an integrity indication to an entity requesting the location of the UE.

[0288]

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

[0289]

[0302] Moreover, those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may realize the described functionality in various ways for each particular application, and such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0290]

[0303] The various example logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A 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 in conjunction with a DSP core, or any other such configuration.

[0291]

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

[0292]

[0305] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0293]

[0306] Although the above disclosure illustrates exemplary aspects of the disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, 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 the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. 1. A method of wireless communication implemented by a user equipment (UE), comprising: receiving one or more positioning parameters from a location server to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), the one or more positioning parameters including: a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP; angle-specific beam information associated with the at least one TRP; a predicted angle associated with the PRS resource; one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE; reference point information associated with a location of the at least one TRP; line-of-sight (LOS) information associated with the PRS resource; or any combination thereof; receiving from the location server one or more integrity parameters related to the one or more positioning parameters; determining an integrity indication for the one or more positioning parameters based on the one or more integrity parameters; A method comprising:

2. the one or more integrity parameters comprise a probability distribution for an error in the one or more positioning parameters; Optionally, the probability distribution comprises a mean and a standard deviation.

3. The method of claim 1 , wherein the one or more integrity parameters comprise a probability distribution for an error in the boresight direction of the PRS resource.

4. the probability distribution is associated with a PRS resource set that includes the PRS resource; the probability distribution applies to all PRS resources in the PRS resource set; or the probability distribution is associated with the at least one TRP; the probability distribution applies to all PRS resources of all PRS resource sets of the at least one TRP; The method of claim 3.

5. The method of claim 1 , wherein the one or more integrity parameters comprise a probability distribution for an error in the beam information for each angle.

6. the probability distribution fits to one angular interval among a plurality of angular intervals of the beam information for each angle; a different probability distribution applies to each angular interval of the plurality of angular intervals; or the beam information for each angle defines a plurality of angle intervals; the probability distribution applies to all of the plurality of angle intervals; The method of claim 5.

7. the predicted angle comprises a predicted angle of departure (AoD) and a predicted AoD uncertainty parameter; the one or more completeness parameters include a probability distribution for the error of the forecast AoD and the forecast AoD uncertainty parameter; The method of claim 1.

8. The method of claim 1 , wherein the one or more integrity parameters comprise a probability distribution for an error in the Tx-TEG margin.

9. the LOS information includes a LOS flag and / or a non-line-of-sight (NLOS) flag associated with each PRS resource or each TRP indicated to the UE; the one or more completeness parameters include a probability distribution for an error in the LOS flag and / or the NLOS flag; The method of claim 1.

10. wherein the one or more completeness parameters comprise a probability distribution for an error in the reference point information, and optionally the reference point information is Positioning Frequency Layer (PFL), the location of the at least one TRP within the PFL; a PRS resource set for the at least one TRP; a PRS resource of the PRS resource set; or Any combination of them The method of claim 1, wherein

11. 1. A method of communication implemented by a location server, comprising: Transmitting one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmitting / receiving point (TRP) to a user equipment (UE), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, angle-specific beam information associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; transmitting to the UE one or more integrity parameters related to the one or more positioning parameters; A method comprising:

12. A user equipment (UE), Memory and at least one transceiver; at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor: and receiving, via the at least one transceiver, one or more positioning parameters from a location server to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, angle-specific beam information associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; receiving, via the at least one transceiver, from the location server, one or more integrity parameters related to the one or more positioning parameters; determining an integrity indication for the one or more positioning parameters based on the one or more integrity parameters; A user equipment (UE) configured to:

13. a location server, Memory and at least one transceiver; at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor: Transmitting, via the at least one transceiver, one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP) to a user equipment (UE), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, angle-specific beam information associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; transmitting, via the at least one transceiver, to the UE, one or more integrity parameters related to the one or more positioning parameters; The location server is configured to:

14. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: Receive one or more positioning parameters from a location server to enable the UE to perform a radio access technology (RAT) dependent positioning procedure involving at least one transmission / reception point (TRP), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, angle-specific beam information associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; receiving from the location server one or more integrity parameters related to the one or more positioning parameters; determining an integrity indication for the one or more positioning parameters based on the one or more integrity parameters; Non-transitory computer-readable medium.

15. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: and causing a user equipment (UE) to transmit one or more positioning parameters of a radio access technology (RAT) dependent positioning procedure involving at least one transmitting / receiving point (TRP), wherein the one or more positioning parameters include a boresight direction associated with a positioning reference signal (PRS) resource transmitted by the at least one TRP, angle-specific beam information associated with the at least one TRP, a predicted angle associated with the PRS resource, one or more transmit timing error group (Tx-TEG) ​​margins associated with the UE, reference point information associated with a location of the at least one TRP, line-of-sight (LOS) information associated with the PRS resource, or any combination thereof; causing the UE to transmit one or more integrity parameters related to the one or more positioning parameters; Non-transitory computer-readable medium.

Images