Group delay look-up table signaling per beam eigenfrequency for high-precision multiple round trip times
A group delay look-up table signaling mechanism addresses the challenge of varying group delays in 5G wireless communication systems, enhancing spectral efficiency and positioning accuracy by providing precise calibration for downlink and uplink beams.
Patent Information
- Application Number
- JP2022514584
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-02-19
- Filing Date
- 2020-08-18
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-08-18
AI Technical Summary
The challenge in 5G wireless communication systems is to enhance spectral efficiency, reduce latency, and improve positioning accuracy, particularly in high-precision multiple round trip time measurements, due to variations in group delay across different frequencies and beams.
Implementing a group delay look-up table (LUT) signaling mechanism that provides per-frequency group delay information for downlink and uplink beams, allowing for precise calibration and compensation of group delay variations in user equipment (UE) and network entities, thereby enhancing positioning accuracy.
The solution enables high-precision positioning by accurately determining the position of user equipment based on beam-specific group delay information, improving spectral efficiency and reducing latency in 5G networks.
Smart Images

Figure 0007592072000003 
Figure 0007592072000004 
Figure 0007592072000005
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This patent application claims priority under 35 U.S.C. § 119 to Greek Patent Application No. 20190100390, entitled "BEAM-SPECIFIC GROUP DELAY / FREQUENCY LOOKUP TABLE SIGNALING FOR HIGH-PRECISION MULTI-ROUND-TRIP-TIME", filed on September 10, 2019, and U.S. Nonprovisional Patent Application No. 16 / 795,338, entitled "BEAM-SPECIFIC GROUP DELAY / FREQUENCY LOOKUP TABLE SIGNALING FOR HIGH-PRECISION MULTI-ROUND-TRIP-TIME", filed on February 19, 2020, both of which are assigned to the assignee of this application and are expressly incorporated by reference in their entireties herein. Introduction
[0002] Aspects of the present disclosure relate generally to wireless communications. [Background technology]
[0002]
[0003] Wireless communication systems have evolved through various generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including intermediate 2.5G networks), third generation (3G) high speed data, Internet-enabled wireless service, and fourth generation (4G) service (e.g., LTE or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular 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 Access (GSM) variants of TDMA, and the like.
[0003]
[0004] The fifth generation (5G) wireless standard, called New Radio (NR), will allow higher data rates, a larger number of connections, and better coverage, among other improvements. The 5G standard by the Next Generation Mobile Network Alliance is designed to give data rates of tens of megabits per second to each of tens of thousands of users, and data rates of one gigabit per second to a few dozen workers on an office floor. To support large wireless sensor deployments, hundreds of thousands of simultaneous connections should be supported. Thus, the spectral efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G standard. Furthermore, signaling efficiency should be enhanced and latency should be significantly reduced compared to the current standard. Summary of the Invention
[0004]
[0005] The following presents a simplified summary related to one or more aspects disclosed herein. As such, the following summary is not intended to be an extensive overview related to all contemplated aspects, nor is it intended to identify key or critical elements related to all contemplated aspects or to delineate the scope related to any particular aspect. As such, the following summary has the sole purpose of presenting some concepts related to one or more aspects related to the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.
[0005]
[0006] In one aspect, a user equipment (UE) includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to receive a first downlink reference signal from a transmission-reception point (TRP) via the at least one transceiver on at least one downlink reference signal resource using a downlink receive beam, cause the at least one transceiver to transmit an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam, determine a parameter indicative of a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal, and cause the at least one transceiver to transmit an uplink reference signal to a network entity. and causing the at least one transceiver to transmit parameters to the network entity; and causing the at least one transceiver to transmit a first lookup table or an identifier of the first lookup table to the network entity, where the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam.
[0006]
[0007] In one aspect, a network entity includes a memory, at least one network interface, and at least one processor communicatively coupled to the memory and the at least one network interface, the at least one processor causing the at least one network interface to transmit, to a user equipment (UE), an identification of at least one downlink reference signal resource to enable the UE to receive a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from the TRP, and causing the at least one network interface to transmit, to the UE, an identification of at least one uplink reference signal resource to enable the UE to transmit an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam to the TRP. the first lookup table representing a difference between a reception time of the first downlink reference signal at the UE and a transmission time of an uplink reference signal from the UE via the at least one network interface; receiving a first lookup table or an identifier of the first lookup table from the UE via the at least one network interface, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam; and estimating a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and a group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
[0007]
[0008] In one aspect, a method of wireless communication implemented by a UE includes receiving a first downlink reference signal from a TRP on at least one downlink reference signal resource using a downlink receive beam; transmitting an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; determining a parameter representative of a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal; transmitting the parameter to a network entity; and transmitting a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam.
[0008]
[0009] In one aspect, a method of wireless communication implemented by a network entity includes transmitting, to the UE, an identification of at least one downlink reference signal resource, to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource using a downlink receive beam from the TRP; transmitting, to the UE, an identification of at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmit beam to the TRP; and transmitting, from the UE, an identification of at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmit beam. The method includes receiving a parameter representing a difference between a reception time at E and a transmission time of an uplink reference signal from the UE, receiving a first lookup table or an identifier of the first lookup table from the UE, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam, and estimating a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and the group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
[0009]
[0010] In one aspect, the UE includes means for receiving a first downlink reference signal from the TRP on at least one downlink reference signal resource using a downlink receive beam, means for transmitting an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam, means for determining a parameter representing a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal, means for transmitting the parameter to a network entity, and means for transmitting a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam.
[0010]
[0011] In one aspect, the network entity includes means for transmitting, to the UE, an identification of at least one downlink reference signal resource, to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource using a downlink receive beam from the TRP; means for transmitting, to the UE, an identification of at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmit beam to the TRP; and means for transmitting, from the UE, a reception time at the UE of the first downlink reference signal and an uplink transmit beam. The method includes receiving a parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal from the UE, a means for receiving a first lookup table or an identifier of the first lookup table from the UE, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam, and a means for estimating a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and the group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
[0011]
[0012] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions includes at least one instruction to instruct a UE to receive a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from the TRP, at least one instruction to instruct the UE to transmit an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam to the TRP, at least one instruction to instruct the UE to determine a parameter representing a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal, at least one instruction to instruct the UE to transmit the parameter to a network entity, and at least one instruction to instruct the UE to transmit a first lookup table or an identifier of the first lookup table to the network entity, where the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam.
[0012]
[0013] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions includes at least one instruction to instruct a network entity to transmit to the UE an identification of at least one downlink reference signal resource to enable the UE to receive a first downlink reference signal from the TRP on the at least one downlink reference signal resource using a downlink receive beam, at least one instruction to instruct the network entity to transmit to the UE an identification of at least one uplink reference signal resource to enable the UE to transmit an uplink reference signal to the TRP on the at least one uplink reference signal resource using an uplink transmit beam, and at least one instruction to instruct the network entity to transmit from the UE an identification of at least one uplink reference signal resource to enable the UE to transmit an uplink reference signal to the TRP on the at least one uplink reference signal resource using an uplink transmit beam, and at least one instruction to transmit from the UE a reception time at the UE of the first downlink reference signal and an uplink reference signal resource from the UE. The method includes computer-executable instructions comprising: at least one instruction to instruct a network entity to receive a parameter representing a difference between a reception time of a first downlink reference signal and a transmission time of an uplink reference signal; at least one instruction to instruct the network entity to receive from the UE a first lookup table or an identifier of the first lookup table; and at least one instruction to instruct the network entity to estimate a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and the group delay for the downlink receive beam and / or uplink transmit beam retrieved from the first lookup table, where the first lookup table represents per-frequency group delay information for the downlink receive beam and / or uplink transmit beam.
[0013]
[0014] 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.
[0014]
[0015] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are given merely to illustrate, not to limit, the aspects. [Brief description of the drawings]
[0015] [Figure 1]
[0016] 1 illustrates an example wireless communication system, in accordance with various aspects. [Figure 2A]
[0017] 1 illustrates an example wireless network structure, in accordance with various aspects. [Figure 2B] 1 illustrates an example wireless network structure, in accordance with various aspects. [Figure 3A]
[0018] 1 is a simplified block diagram of several sample aspects of components that may be employed in a wireless communication node and configured to support communication as taught herein; [Figure 3B] 1 is a simplified block diagram of several sample aspects of components that may be employed in a wireless communication node and configured to support communication as taught herein; [Figure 3C] 1 is a simplified block diagram of several sample aspects of components that may be employed in a wireless communication node and configured to support communication as taught herein; [Figure 4]
[0019] 1 illustrates an example of a frame structure for use in a wireless telecommunications system, according to one aspect of the present disclosure. [Diagram 5]
[0020] 1 illustrates an example technique for determining a location of a UE using information obtained from multiple base stations. [Figure 6A]
[0021] 4 illustrates an example timing of round-trip-time (RTT) measurement signals exchanged between a base station and a UE, in accordance with an aspect of the present disclosure. [Figure 6B] 4 illustrates an example timing of round trip time (RTT) measurement signals exchanged between a base station and a UE, in accordance with an aspect of the present disclosure. [Figure 7]
[0022] 1 illustrates a graph comparing group delay with frequency, in accordance with an aspect of the present disclosure. [Figure 8A]
[0023] 1 illustrates two downlink reference signal resources having the same quasi-collocation source reference signal, according to an aspect of the disclosure. [Figure 8B]
[0024] 1 illustrates two uplink reference signal resources having the same spatial relation reference downlink reference signal, according to an aspect of the disclosure. [Figure 9]
[0025] FIG. 1 illustrates a method of wireless communication according to an aspect of the present disclosure. [Figure 10] FIG. 1 illustrates a method of wireless communication according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016]
[0026] Aspects of the present disclosure are provided in the following description and associated drawings, directed to various examples provided for illustration 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.
[0017]
[0027] 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" is not necessarily to 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.
[0018]
[0028] 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, the 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.
[0019]
[0029] Furthermore, many aspects are described in terms of a sequence of actions to be performed, for example, by elements of a computing device. It will be appreciated that the various actions 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. Furthermore, a sequence of actions described herein may be considered to be embodied as a whole in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or instruct an associated processor of a 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 fall within the scope of the claimed subject matter. Moreover, 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.
[0020]
[0030] The terms "user equipment" (UE) and "base station" as used herein are not intended to be specific or otherwise limited to any particular radio access technology (RAT) unless otherwise stated. Generally, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable (e.g., a smart watch, glasses, an 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 (e.g., at some times) stationary and may communicate with a radio access network (RAN). The term "UE" as used herein 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 terminal", "mobile station", or variations thereof. Generally, a UE may communicate with a core network via a RAN, through which the UE may be connected with external networks such as the Internet and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are possible for a UE, such as via a wired access network, a wireless local area network (WLAN) network (eg, based on IEEE 802.11, etc.), etc.
[0021]
[0031] Depending on the network in which it is deployed, the base station may operate according to one of several RATs in communication with the UE and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), New Radio (NR) Node B (also referred to as gNB or gNode B), etc. Furthermore, in some systems the base station may provide purely edge node signaling functionality, while in other systems it may provide additional control and / or network management functionality. A communication link through which the UE can send signals to the base station is referred to as an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which the base station can send signals to the UE is referred to as a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to either a UL / reverse traffic channel or a DL / forward traffic channel.
[0022]
[0032] The term "base station" may refer to a single physical transmit 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 the cell 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 a multiple-input multiple-output (MIMO) system or in cases where 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, the non-collocated physical TRP may be a serving base station that receives a measurement report from a UE and a neighbor base station whose reference RF signal the UE is measuring. A TRP is a point from which a base station transmits and receives wireless signals, and therefore, as used herein, references to transmission from or reception at a base station should be understood as referring to the particular TRP of the base station.
[0023]
[0033] An "RF signal" comprises electromagnetic waves of a given frequency that transport 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, a 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 transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal.
[0024]
[0034] In accordance with various aspects, FIG. 1 illustrates an exemplary wireless communication system 100. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 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 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]
[0035] The base stations 102 collectively form a RAN and may interface with a core network 170 (e.g., Evolved Packet Core (EPC) or Next Generation Core (NGC)) through backhaul links 122 and to one or more location servers 172 through the core network 170. In addition to other functions, the base stations 102 may perform functions related to one or more of 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, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracing, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / NGC) via backhaul links 134, which may be wired or wireless.
[0026]
[0036] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage to 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 resource, called a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., physical cell identifier (PCI), virtual cell identifier (VCI)) 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 to different types of UEs. Because a cell is supported by a particular base station, the term "cell" may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In some cases, the term “cell” may also refer to a geographic coverage area (e.g., a sector) of a base station, so long as the carrier frequency can be detected and used for communication within any portion of the geographic coverage area 110.
[0027]
[0037] The geographic coverage areas 110 of neighboring macrocell base stations 102 may overlap partially (e.g., in handover regions), but some of the geographic coverage areas 110 may be significantly overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' may have a 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) that may serve restricted groups known as Closed Subscriber Groups (CSGs).
[0028]
[0038] The communication link 120 between the base station 102 and the UE 104 may include UL (also called reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also called 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 DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL).
[0029]
[0039] 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) procedure or a listen-before-talk (LBT) procedure before communicating to determine if a channel is available.
[0030]
[0040] The small cell base station 102' may operate in licensed and / or unlicensed frequency spectrums. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. A small cell base station 102' employing LTE / 5G in an unlicensed frequency spectrum may boost coverage to and / or increase capacity of an access network. NR in an unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.
[0031]
[0041] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW and / or near-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 between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Near-mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band, also called centimeter wave, extends between 3 GHz and 30 GHz. Communications using the mmW / near-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 high path loss and short distances. Moreover, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Thus, it will be appreciated that the above description is by way of example only and should not be construed as limiting various aspects disclosed herein.
[0032]
[0042] Transmit beamforming is a technique for focusing an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). In transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that particular direction, thereby giving a faster (in terms of data rate) and stronger RF signal to the receiving device(s). To change 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 transmitter or transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (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. In particular, RF currents from the transmitters are fed to the individual antennas with the proper phase relationship so that the waves from the separate antennas add together to increase radiation in desired directions and cancel to suppress radiation in undesired directions.
[0033]
[0043] Transmit beams may be quasi-colocated, meaning that they appear to have the same parameters to a receiver (e.g., a UE) regardless of whether the network node's transmit antennas themselves are physically colocated. In NR, there are four types of quasi-colocated (QCL) relationships. In particular, 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.
[0034]
[0044] 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 its gain level) an RF signal received from that direction. Thus, when a receiver is said to beamform in a direction, it means that the beam gain in that direction is high relative to 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 the RF signal received from that direction.
[0035]
[0045] The receive beams may be spatially related. The spatial relationship means that the parameters for the transmit beam for the second reference signal may be derived from information about the receive 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., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for sending an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.
[0036]
[0046] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if the base station forms a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE forms a downlink beam, it is a receive beam to receive the downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if the base station forms an uplink beam, it is an uplink receive beam, and if the UE forms an uplink beam, it is an uplink transmit beam.
[0037]
[0047] In 5G, the frequency spectrum in which wireless nodes (e.g., base station 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges: FR1 (450 to 6000 MHz), FR2 (24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). 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 the carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and 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 and UE-specific control channels and may be a carrier in licensed frequencies (although this is not always the case). 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 in unlicensed frequencies. The secondary carrier may contain only the necessary signaling information and signals, e.g., nothing UE-specific may be present in the secondary carrier, since both the primary uplink carrier and the primary downlink carrier are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is capable of changing the primary carrier of any UE 104 / 182 at any time. This is done, for example, to distribute the load on the different carriers.Since a "serving cell" (whether a PCell or an SCell) corresponds to the carrier frequency / component carrier over which some base station is communicating, terms such as "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.
[0038]
[0048] 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 aggregated carriers in a multi-carrier system would theoretically lead to a doubling of the data rate (i.e., 40 MHz) compared to that achieved by a single 20 MHz carrier.
[0039]
[0049] 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. In the example of FIG. 1, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which the UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (through which the UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth, etc.
[0040]
[0050] The wireless communication system 100 may further include a UE 164, which may communicate with the macrocell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication 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. In an aspect, the UE 164 may include a LUT manager 166 that may enable the UE 164 to perform the UE operations described herein. It should be noted that although only one UE is shown in FIG. 1 as having a LUT manager 166, any of the UEs in FIG. 1 may be configured to perform the UE operations described herein.
[0041]
[0051] In accordance with various aspects, FIG. 2A illustrates an exemplary wireless network structure 200. For example, the NGC 210 (also referred to as "5GC") may be considered functionally as a control plane function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane function 212 (e.g., UE gateway function, access to data network, 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 NGC 210, specifically to the control plane function 214 and the user plane function 212. In an additional configuration, the eNB 224 may also be connected to the NGC 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 eNB 224 may communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include one or more of both the eNBs 224 and the gNBs 222. Either the gNBs 222 or the eNBs 224 may be in communication with the UEs 204 (e.g., any of the UEs shown in FIG. 1). Another optional aspect may include a location server 230 (which may correspond to location server 172), which may be in communication with the NGC 210 to provide location assistance to the UEs 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 spread 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 be connected to the location server 230 via a core network, the NGC 210, and / or via the Internet (not shown). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network.
[0042]
[0052] 2B illustrates another exemplary wireless network structure 250. For example, the NGC 260 (also referred to as "5GC") may be considered functionally as a control plane function provided by an Access and Mobility Management Function (AMF) / User Plane Function (UPF) 264 and a user plane function provided by a Session Management Function (SMF) 262, which operate cooperatively to form a core network (i.e., the NGC 260). A user plane interface 263 and a control plane interface 265 connect the eNB 224 to the NGC 260, specifically to the SMF 262 and the AMF / UPF 264, respectively. In an additional configuration, the gNB 222 may also be connected to the NGC 260 via a control plane interface 265 to the AMF / UPF 264 and a user plane interface 263 to the SMF 262. Additionally, eNB 224 may communicate directly with gNB 222 via backhaul connection 223, with or without gNB direct connectivity to NGC 260. In some configurations, new-RAN 220 may have only one or more gNBs 222, while other configurations include one or more of both eNB 224 and gNB 222. Either gNB 222 or eNB 224 may communicate with UE 204 (e.g., any of the UEs shown in FIG. 1). Base stations of new-RAN 220 communicate with the AMF side of AMF / UPF 264 via an N2 interface and with the UPF side of AMF / UPF 264 via an N3 interface.
[0043]
[0053] The functions of the AMF include registration management, connection management, reachability management, mobility management, lawful interception, transport of session management (SM) messages between the UE 204 and the SMF 262, a transparent proxy service for routing SM messages, access authentication and access authorization, transport of short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and a security anchor function (SEAF). The AMF also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives 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 retrieves security material from the AUSF. The functions of the AMF also include security context management (SCM). The SCM receives keys from the SEAF that it uses to derive access network specific keys. The AMF functions also include location service management for barred services, transport of location service messages between the UE 204 and a Location Management Function (LMF) 270 (which may correspond to the location server 172) and between the new 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 also supports functions for non-3rd Generation Partnership Project (3GPP®) access networks.
[0044]
[0054] The functions of the UPF 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), providing packet routing and forwarding, 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., UL / DL rate enforcement, reflective QoS marking in DL), UL traffic validation (Service Data Flow (SDF) to QoS flow mapping), transport level packet marking in UL and DL, DL packet buffering and DL data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node.
[0045]
[0055] The functions of the SMF 262 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 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 262 communicates with the AMF side of the AMF / UPF 264 is called the N11 interface.
[0046]
[0056] Another optional aspect may include the LMF 270, which may be in communication with the NGC 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 spread across multiple physical servers, etc.) or, alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204 that may connect to the LMF 270 via a core network, the NGC 260, and / or via the Internet (not shown).
[0047]
[0057] 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 perform any of the network functions described herein, including the location server 230 and the LMF 270) to support file transmission operations as taught herein. It will be appreciated that these components may be implemented in different types of devices (e.g., in an ASIC, in a system on a chip (SoC), etc.) in different implementations. The illustrated components may also be incorporated in other devices in a communication system. For example, other devices in the system may include similar components to those described to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.
[0048]
[0058] The UE 302 and the base station 304 each include a wireless wide area network (WWAN) transceiver 310 and 350, respectively, configured to communicate 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 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, respectively (e.g., messages, instructions, information, etc.), and conversely, to receive and decode signals 318 and 358, respectively (e.g., messages, instructions, information, pilots, etc.), in accordance with the designated RAT. In particular, the transceivers 310 and 350 each include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, and each include one or more receivers 312 and 352, respectively, for receiving and decoding the signals 318 and 358, respectively.
[0049]
[0059] The UE 302 and base station 304 also, at least in some cases, include wireless local area network (WLAN) transceivers 320 and 360, respectively. The WLAN transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, for communicating 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, etc.) over a wireless communication medium of interest. The WLAN transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368, respectively (e.g., messages, instructions, information, etc.), and conversely, to receive and decode signals 328 and 368, respectively (e.g., messages, instructions, information, pilots, etc.), in accordance with the designated RAT. In particular, the transceivers 320 and 360 each include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, and each include one or more receivers 322 and 362, respectively, for receiving and decoding the signals 328 and 368, respectively.
[0050]
[0060] A transceiver circuit including a transmitter and a receiver may in some implementations comprise an integrated device (e.g., implemented as a transmitter circuit and a receiver circuit of a single communication device), in some implementations comprise separate transmitter devices and separate receiver devices, or in other implementations may be implemented in other ways. In one aspect, the transmitter may include or be coupled to multiple antennas, such as an antenna array (e.g., antennas 316, 336, and 376), that enable each device to perform transmit "beamforming" as described herein. Similarly, the receiver may include or be coupled to multiple antennas, such as an antenna array (e.g., antennas 316, 336, and 376), that enable each device to perform receive beamforming as described herein. In one aspect, the transmitter and receiver may share the same multiple antennas (e.g., antennas 316, 336, and 376), that enable each device to only receive or transmit at a given time, rather than both receive and transmit at the same time. The wireless communication devices of apparatus 302 and / or 304 (e.g., one or both of transceivers 310 and 320 and / or 350 and 360) may also include a network listen module (NLM) or the like for performing various measurements.
[0051]
[0061] The devices 302 and 304 also, in at least some cases, include satellite positioning system (SPS) receivers 330 and 370. The SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, for receiving SPS signals 338 and 378, respectively, such as Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. The SPS receivers 330 and 370 may comprise any suitable hardware and / or software for receiving and processing the SPS signals 338 and 378, respectively. The SPS receivers 330 and 370 request information and actions from other systems as appropriate, and perform the calculations necessary to determine the positions of the devices 302 and 304 using the measurements obtained by any suitable SPS algorithms.
[0052]
[0062] The base station 304 and the network entity 306 each include at least one network interface 380 and 390 for communicating with other network entities. For example, the network interfaces 380 and 390 (e.g., one or more network access ports) may be configured to communicate with one or more network entities over a wire-based or wireless backhaul connection. In some aspects, the network interfaces 380 and 390 may be implemented as transceivers configured to support wire-based or wireless signal communication. This communication may involve, for example, sending and receiving messages, parameters, or other types of information.
[0053]
[0063] The devices 302, 304, and 306 also include other components that may be used with the operations disclosed herein. The UE 302 includes a processor circuit that implements a processing system 332, for example, for providing functionality related to RTT positioning as disclosed herein and for providing other processing functions. The base station 304 includes a processing system 384, for example, for providing functionality related to RTT positioning as disclosed herein and for providing other processing functions. The network entity 306 includes a processing system 394, for example, for providing functionality related to RTT positioning as disclosed herein and for providing other processing functions. In an aspect, the processing systems 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), or other programmable logic devices or processing circuits.
[0054]
[0064] The devices 302, 304, and 306 include memory circuitry implementing memory components 340, 386, and 396, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). In some cases, the devices 302, 304, and 306 may include LUT managers 342, 388, and 398, respectively. The LUT managers 342, 388, and 398 may be hardware circuits that are part of or coupled to the processing systems 332, 384, and 394, respectively, that, when executed, cause the devices 302, 304, and 306 to perform the functions described herein. In other aspects, the LUT managers 342, 388, and 398 may be external to the processing systems 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, LUT managers 342, 388, and 398 may be memory modules stored in memory components 340, 386, and 396, respectively (as shown in Figures 3A-3C) that, when executed by processing systems 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause devices 302, 304, and 306 to perform the functions described herein.
[0055]
[0065] The UE 302 may include one or more sensors 344 coupled to the processing system 332 to provide movement and / or orientation information that is independent of movement data derived from signals received by the WWAN transceiver 310, the WLAN transceiver 320, and / or the SPS receiver 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a microelectromechanical system (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. Moreover, 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 a position in a 2D and / or 3D coordinate system.
[0056]
[0066] Additionally, the UE 302 includes a user interface 346 for providing instructions (e.g., audible and / or visual instructions) to a user and / or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, touch screen, microphone, etc.). Although not shown, the devices 304 and 306 may also include user interfaces.
[0057]
[0067] Referring more particularly to the processing system 384, in the downlink, IP packets from the network entity 306 may be provided to the processing system 384. The processing system 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 processing system 384 may provide RRC layer functions related to broadcasting 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 related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.
[0058]
[0068] The transmitter 354 and receiver 352 may implement Layer 1 functions related to 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 to 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), multi-level quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined with each other using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM 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 respective spatial stream for transmission.
[0059]
[0069] At the UE 302, the receiver 312 receives the signal through its respective antenna(s) 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to the processing system 332. The transmitter 314 and the receiver 312 implement layer 1 functions related to various signal processing functions. The receiver 312 may perform spatial processing on the information to recover the 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 comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and 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 signaling originally transmitted on the physical channel by the base station 304. The data and control signaling are then provided to a processing system 332 that implements Layer 3 and Layer 2 functions.
[0060]
[0070] In the UL, the processing system 332 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header recovery, and control signal processing to recover IP packets from the core network. The processing system 332 is also responsible for error detection.
[0061]
[0071] Similar to the functionality described with respect to DL transmission by the base station 304, the processing system 332 provides RRC layer functionality related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality related to transfer 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 related to mapping between logical channels and transport channels, multiplexing of MAC SDUs onto and demultiplexing of MAC SDUs from transport blocks (TBs), scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.
[0062]
[0072] 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 enable 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 each spatial stream for transmission.
[0063]
[0073] The UL 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 the signals through its respective antenna(s) 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to a processing system 384.
[0064]
[0074] In the UL, the processing system 384 provides 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 processing system 384 may be provided to the core network. The processing system 384 is also responsible for error detection.
[0065]
[0075] For convenience, devices 302, 304, and / or 306 are illustrated in Figures 3A-3C as including various components that may be configured in accordance with various examples described herein, however, it will be appreciated that the illustrated blocks may have different functions in different designs.
[0066]
[0076] The various components of the devices 302, 304, and 306 may communicate with each other via data buses 334, 382, and 392, respectively. The components of FIGS. 3A-3C may be implemented in various ways. In some implementations, the components of FIGS. 3A-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 a 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, acts, and / or functions are described herein as being performed "by a UE," "by a base station," "by a network entity," etc. However, it will be appreciated that such operations, acts, and / or functions may actually be performed by a particular component or combination of components of a UE, a base station, a network entity, etc., such as the processing systems 332, 384, 394, the transceivers 310, 320, 350, and 360, the memory components 340, 386, and 396, the LUT managers 342, 388, and 398, etc.
[0067]
[0077] Time intervals of communication resources in LTE or 5G NR may be organized according to radio frames. Figure 4 is a diagram 400 illustrating an example of a DL frame structure according to an embodiment of the present disclosure. Other wireless communication technologies may have different frame structures and / or different channels.
[0068]
[0078] LTE, and possibly NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR has the option to use OFDM on the uplink as well. 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. In general, 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, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the subcarrier spacing may be 15 kHz, and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Thus, the nominal 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.
[0069]
[0079] LTE supports a single numerology (subcarrier spacing, symbol length, etc.). In contrast, NR may support multiple numerologies, e.g., subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz and 204 kHz or greater may be available. Table 1 provided below lists some various parameters for different NR numerologies.
[0070] [Table 1]
[0071]
[0080] In the example of Figure 4, a numerology of 15 kHz is used. Thus, in the time domain, a frame (e.g., 10 milliseconds (ms)) 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 (e.g., on the X-axis), with time increasing from left to right, and frequency is represented vertically (e.g., on the Y-axis), with frequency increasing (or decreasing) from bottom to top.
[0072]
[0081] A resource grid may be used to represent a time slot, with each time slot including one or more (also called physical RB (PRB)) time-parallel resource blocks (RBs) 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 (OFDM symbols for DL, SC-FDMA symbols for UL) in the time domain for 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 for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.
[0073]
[0082] As shown in Figure 4, some of the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include a demodulation reference signal (DMRS) and a channel state information reference signal (CSI-RS), whose example locations are labeled as "R" in Figure 4.
[0074]
[0083] In some cases, the CSI-RS shown in FIG. 4 may be a positioning reference signal (PRS). The set of resource elements used for the transmission of the PRS is called a "PRS resource." The set of resource elements may span multiple PRBs in the frequency domain and N (e.g., one or more) consecutive symbols in a slot in the time domain. In a given OFDM symbol, the PRS resource occupies consecutive PRBs. The PRS resource is described by at least the following parameters: PRS resource identifier (ID), sequence ID, comb size N, resource element offset in the frequency domain, starting slot and starting symbol, number of symbols per PRS resource (i.e., duration of the PRS resource), and QCL information (e.g., QCL with respect to other DL reference signals). Currently, one antenna port is supported. The comb size indicates the number of subcarriers in each symbol carrying the PRS. For example, a comb size of comb 4 means that every fourth subcarrier of a given symbol carries the PRS.
[0075]
[0084] A "PRS resource set" is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. Furthermore, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set may be identified by a PRS resource set ID and associated with a specific TRP (identified by a cell ID) transmitted by an antenna panel of a base station. A PRS resource ID in a PRS resource set is associated with a single beam (and / 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 a "PRS resource" or simply a "resource" may also be referred to as a "beam". Note that this does not have any implication as to whether the TRP and the beam on which the PRS is transmitted are known to the UE.
[0076]
[0085] 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," a "PRS positioning instance," a "positioning occasion," a "positioning instance," or simply an "occasion" or "instance."
[0077]
[0086] It should be noted that the terms "positioning reference signal" and "PRS" may sometimes refer to specific reference signals used for positioning in LTE systems. However, unless otherwise specified, the terms "positioning reference signal" and "PRS" as used herein refer to any type of reference signal that may be used for positioning, such as, but not limited to, PRS signals in LTE, navigation reference signals (NRS) in 5G, tracking reference signals (TRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), primary synchronization signals (PSS), secondary synchronization signals (SSS), etc.
[0078]
[0087] In NR, there may be no requirement for precise timing synchronization across the network. Instead, it may be sufficient to have coarse time synchronization across the gNB (e.g., within the cyclic prefix (CP) duration of an OFDM symbol). RTT-based methods generally require only coarse timing synchronization and therefore may be the preferred positioning method in NR.
[0079]
[0088] In network-centric RTT estimation, a serving base station (e.g., base station 102) instructs a UE (e.g., UE 104) to scan / receive RTT measurement signals (e.g., PRS) on serving cells of two or more neighboring base stations (and the serving base station, since typically at least three base stations are required). One or more base stations transmit the RTT measurement signals on low reuse resources (e.g., resources used by base stations to transmit system information) allocated by the network (e.g., location server 230, LMF 270). The UE records the arrival time (also called receive time, reception time, time of reception, or time of arrival (ToA)) of each RTT measurement signal relative to the UE's current downlink timing (e.g., as derived by the UE from a downlink signal received from its serving base station), transmits common or individual RTT response messages (e.g., SRS, UL-PRS) to one or more base stations (e.g., when commanded by its serving base station), and includes in the payload of each RTT response message the difference T between the ToA of the RTT measurement signal and the transmission time of the RTT response message. Rx→Tx (For example, T in Fig. 6A Rx→Tx 612). The RTT response message will include a reference signal from which the base station can infer the ToA of the RTT response. The difference T Tx→Rx (For example, T in Fig. 6A Tx→Rx 622) by the difference T Rx→Tx (For example, T in 6A Rx→Tx 612), the base station (or positioning entity) can infer the propagation time between the base station and the UE, from which the base station can then determine the distance between the UE and the base station by assuming the speed of light during this propagation time.
[0080]
[0089] The UE-centric RTT estimation is similar to the network-based method, except that the UE (e.g., when commanded by the serving base station) transmits an uplink RTT measurement signal(s) that is received by multiple base stations in the UE's vicinity. Each participating base station responds with a downlink RTT response message, which may include in the RTT response message payload the time difference between the ToA of the RTT measurement signal at the base station and the transmission time of the RTT response message from the base station.
[0081]
[0090] For both network-centric and UE-centric procedures, the party performing the RTT calculation (network or UE) typically (but not always) sends an initial message(s) or signal(s) (e.g., RTT measurement signal(s)), and the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the initial message(s) or signal(s) and the transmission time of the RTT response message(s) or signal(s).
[0082]
[0091] FIG. 5 illustrates an example wireless communication system 500 according to an aspect of the disclosure. In the example of FIG. 5, a UE 504 (which may correspond to any of the UEs described herein) is attempting to calculate an estimate of its location or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its location. The UE 504 may wirelessly communicate with multiple base stations 502-1, 502-2, and 502-3 (which may collectively correspond to base station 502 and any of the base stations described herein) using RF signals and standardized protocols for modulation of RF signals and exchange of information packets. By extracting different types of information from the exchanged RF signals and utilizing the layout of the wireless communication system 500 (i.e., base station locations, geometry, etc.), the UE 504 may determine, or assist in determining, its location in a predefined reference coordinate system. In one aspect, the UE 504 may specify its location using a two-dimensional coordinate system, although the aspects disclosed herein are not so limited and may be applicable to determining location using a three-dimensional coordinate system if additional dimensions are desired. Additionally, while FIG. 5 shows one UE 504 and three base stations 502, it will be appreciated that there may be more UEs 504 and more base stations 502.
[0083]
[0092] To support position estimation, base stations 502 may be configured to broadcast reference RF signals (e.g., PRS, NRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to UEs 504 in their coverage areas to allow the UEs 504 to measure characteristics of such reference RF signals. For example, the UE 504 may measure the ToAs of particular reference RF signals transmitted by at least three different base stations 502 and use an RTT positioning method to report these ToAs (and additional information) to the serving base station 502 or another positioning entity (e.g., location server 230, LMF 270).
[0084]
[0093] In one aspect, the UE 504 is described as measuring a reference RF signal from the base station 502, but the UE 504 may measure a reference RF signal from one of a number of cells supported by the base station 502. When the UE 504 measures a reference RF signal transmitted by a cell supported by the base station 502, at least two other reference RF signals measured by the UE 504 to perform the RTT procedure are from cells supported by a base station 502 different from the first base station 502 and may have good or poor signal strength at the UE 504.
[0085]
[0094] To determine the position (x,y) of the UE 504, an entity that determines the position of the UE 504 may calculate the position (x,y) of the UE 504. k ,y k ), where k=1, 2, 3 in the example of FIG. 5. When one of the base stations 502 (e.g., the serving base station) or the UE 504 determines the location of the UE 504, the location of the involved base station 502 may be provided to the serving base station 502 or UE 504 by a location server (e.g., location server 230, LMF 270) with knowledge of the network geometry. Alternatively, the location server may determine the location of the UE 504 using the known network geometry.
[0086]
[0095] Either the UE 504 or the respective base station 502 determines the distance (d k , where k=1, 2, 3). In one aspect, determining the RTT 510 of signals exchanged between the UE 504 and any base station 502 is performed, and the distance (d k) As described further below, RTT techniques can measure the time between sending a signaling message (e.g., a reference RF signal) and receiving a response. These methods may utilize calibration to remove processing delays. In some environments, it may be assumed that the processing delays for the UE 504 and the base station 502 are the same. However, such an assumption may not be true in practice.
[0087]
[0096] each distance d k Once x,y is determined, the UE 504, base station 502, or location server (e.g., location server 230, LMF 270) can determine the position (x,y) of the UE 504 by using various known geometric techniques, such as, for example, trilateration. From FIG. 5, it can be seen that the position of the UE 504 is ideally at the common intersection of three semicircles, each of which has a radius d k and center (x k ,y k ) where k=1, 2, 3.
[0088]
[0097] In some cases, additional information may be obtained in the form of a linear direction (which may be, for example, in the horizontal plane or in three dimensions), or possibly an angle of arrival (AoA) or angle of departure (AoD) that defines a range of directions (e.g., for the UE 504 from the location of the base station 502). The intersection of the two directions at or near a point (x,y) may provide another estimate of the location for the UE 504.
[0089]
[0098] A location estimate (e.g., for a UE 504) may be called by other names, such as a location estimate, location, position, position fix, fix, etc. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of the location. A location estimate may further be defined relative to some other known location or in absolute terms (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 that the location is expected to cover with some specified or default confidence level).
[0090]
[0099] 6A is a diagram 600A illustrating example timing of RTT measurement signals exchanged between a base station 602 (e.g., any of the base stations described herein) and a UE 604 (e.g., any of the UEs described herein) in accordance with an aspect of the disclosure. In the example of FIG. 6A, the base station 602 sends an RTT measurement signal 610 (e.g., PRS, NRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to the UE 604 at time T1. The RTT measurement signal 610 incurs some propagation delay T Prop At time T2 (the ToA of the RTT measurement signal 610 at the UE 604), the UE 604 receives / measures the RTT measurement signal 610. After some UE processing time, the UE 604 transmits an RTT response signal 620 at time T3. The propagation delay T Prop Subsequently, the base station 602 receives / measures the RTT response signal 620 from the UE 604 at time T4 (the ToA of the RTT response signal 620 at the base station 602).
[0091]
[0100] To identify the ToA (e.g., T2) of a reference signal (e.g., RTT measurement signal 610) transmitted by a given network node (e.g., base station 602), the receiver (e.g., UE 604) first processes all resource elements (REs) on the channel on which the transmitter is transmitting the reference signal together and performs an inverse Fourier transform to convert the received reference signal to the time domain. The conversion of the received reference signal to the time domain is called an estimation of the channel energy response (CER). The CER indicates the peaks on the channel over time, and the earliest "significant" peak should therefore correspond to the ToA of the reference signal. In general, the receiver uses a noise-related quality threshold to remove false local peaks, thereby presumably correctly identifying the significant peaks on the channel. For example, the receiver may choose a ToA estimate that is the earliest local maximum of CER that is at least X dB higher than the median CER and a maximum value that is Y dB lower than the main peak on the channel. The receiver determines the CER for each reference signal from each transmitter in order to determine the ToA for each reference signal from a different transmitter.
[0092]
[0101] The RTT response signal 620 is the difference between time T3 and time T2 (i.e., T Rx→Tx 612). Alternatively, it may be derived from the timing advance (TA), i.e., the relative UL / DL frame timing, and the specified location of the UL reference signal. (Note that TA is typically the RTT between the base station and the UE, or twice the propagation time in one direction.) This measurement and the difference between time T4 and time T1 (i.e., T Tx→Rx 622), the base station 602 (or other positioning entity, such as location server 230, LMF 270, etc.) can calculate the distance to the UE 604 as follows:
[0093]
number
[0094] where c is the speed of light.
[0095]
[0102] 6B is a diagram 600B illustrating example timing of RTT measurement signals exchanged between a base station 602 and a UE 604 according to an embodiment of the disclosure. Diagram 600B is similar to diagram 600A, except that it includes processing delays that occur at both the base station 602 and the UE 604 when transmitting and receiving RTT measurement signals 610 and RTT response signals 620.
[0096]
[0103] In detail, on the base station 602 side, there is a time lag between the time when the baseband (BB) of the base station 602 generates the RTT measurement signal 610 and the time when the antenna (Ant) transmits the RTT measurement signal 610. gNB,Tx At the UE 604 side, there is a transmission delay of T between the time when the antenna of the UE 604 receives / detects the RTT measurement signal 610 and the time when the baseband processes the RTT measurement signal 610. UE,Rx Similarly, for the RTT response signal 620, there is a reception delay of T between the time when the baseband of the UE 104 generates the RTT response signal 620 and the antenna transmits the RTT response signal 620. UE,Tx On the base station 602 side, there is a transmission delay of T between the time when the antenna of the base station 602 receives / detects the RTT response signal 620 and the time when the baseband processes the RTT response signal 620. gNB,Rx There is a delay in receiving the message.
[0097]
[0104] The delay between the baseband and the antenna is referred to as the RF front-end (RFFE) group delay. Group delay is the time delay of the amplitude envelope (smooth curve that abbreviates the extremes of a sine wave) of the various sinusoidal components of the RF signal through a device (e.g., UE 604, base station 602) and is a function of frequency for each sinusoidal component. In one aspect, the UE 604 may know, for example, the average group delay (over other factors that may affect the group delay at a particular frequency, such as temperature, construction / fabrication errors, etc.) and the standard deviation around it, and thus be able to compensate for (i.e., calibrate out) the average group delay. Alternatively, the UE 604 may know the average group delay and standard deviation, but may not calibrate out anything. The average group delay and the standard deviation of the average group delay are referred to herein as group delay information.
[0098]
[0105] The base station 602 compensates for its own RFFE group delay to determine the actual transmission and reception times of the RTT measurement signal 610 and the RTT response signal 620, respectively. The base station 602 (or other positioning entity, such as the location server 230, the LMF 270, etc.) then determines the actual propagation delay T between the base station 602 and the UE 604. Prop , and thus the distance between the base station 602 and the UE 604 can be determined. Alternatively, the UE 604 may report its RFFE group delay rather than compensating for it itself, and the base station 602 (or other positioning entity) may then use the propagation delay T Prop and subtract the reported RFFE group delay to determine the final distance.
[0099]
[0106] The UE 604 may perform an RTT procedure with multiple base stations 604. However, the RTT procedure does not require synchronization between these base stations 602.
[0100]
[0107] Regarding downlink beam management, several options are currently supported to help the UE perform receive beamforming for positioning purposes. As a first option, the downlink PRS to be measured as an RTT measurement signal (e.g., RTT measurement signal 610) may be configured to be QCL type D with a downlink reference signal from a serving cell or a neighboring cell. As a second option, the UE may perform receive beam sweeping for downlink PRS resources transmitted with the same downlink spatial domain transmit filter. As a third option, the UE may use a fixed receive beam to receive downlink PRS resources transmitted with different downlink spatial domain transmit filters.
[0101]
[0108] For uplink beam management / alignment for serving and neighboring cells for positioning purposes, several options are currently supported. As a first option, a spatial relationship may be configured between a reference downlink reference signal from a serving or neighboring cell and a target SRS. Reference downlink reference signals that may be used include at least an SSB transmitted on a cell. As a second option, the UE may perform transmit beam sweeping of uplink SRS transmission across multiple uplink SRS resources. As a third option, the UE may use a fixed transmit beam for uplink SRS transmission across multiple uplink SRS resources for both FR1 and FR2. It should be noted that currently, the UE is not expected to transmit multiple SRS resources with different spatial relationships in the same OFDM symbol as was the case before.
[0102]
[0109] Turning to group delay in more detail, there are several sources of variation in the group delay of a UE. An accurately estimated group delay is important because it affects positioning accuracy. Generally, 1 nanosecond (ns) in time translates to 1 foot in positioning accuracy. Thus, a 5ns difference between two group delays translates to a 5 foot (ft) difference in position. While this may be accurate enough for some applications, in high-precision positioning scenarios (e.g., centimeter-level accuracy), this is unacceptable.
[0103]
[0110] Some sources of group delay variation are part-specific (for both analog and digital paths); that is, physical parts, or components, of the UE contribute to the group delay for both analog and digital paths. To determine the resulting group delay, a reference design (multiple instances) should be tested to measure the part-to-part variation. Customers and vendors with proprietary designs typically perform their own testing and provide this information, for example, in an application note or as part of a software release. This testing also includes third-party components, since it is the designer's responsibility to use good parts.
[0104]
[0111] Another source of variation is frequency specific. For example, the group delay for the lower edge and the group delay for the upper edge of the 5 GHz frequency band may differ by 500 picoseconds (ps). Thus, the group delay of a signal received on one subcarrier may differ from the group delay of a signal received on a different subcarrier. FIG. 7 illustrates a graph 700 comparing group delay (on the Y-axis) with frequency (on the X-axis) according to an embodiment of the disclosure. A specific 200 MHz frequency band (2493 MHz to 2693 MHz) is shown between two vertical lines. Within that frequency band, UE components are designed to make the group delay as constant as possible. However, this is not entirely possible, hence the "U" shape of the graph between the vertical lines. For example, as shown in FIG. 7, at a frequency of 2498 MHz, there is a group delay of 18.333 ns, but at a frequency of 2613 MHz, there is a group delay of 3.52 ns. To determine the likely group delay for each frequency band, the UE should calibrate for each channel in the band, although some channels may be avoided for RTT and therefore would not need to be tested.
[0105]
[0112] Yet another source of variation is path specific; i.e., group delay may vary depending on the selected antenna or antenna panel, transmit power / processing, and / or receive power / processing. Another source of variation is temperature specific; this can be addressed with a calibration table for temperature. Other errors that can affect group delay include calibration errors (e.g., technical or procedural), measurement accuracy, etc.
[0106]
[0113] Another source of group delay variation addressed in this disclosure is beam-specific. Group delay not only varies from frequency to frequency, as described above with reference to FIG. 7, but also varies based on the particular receive / transmit beam(s) used within that frequency. This is because different sets of antenna elements of an antenna panel form different beams, and therefore different beams have different physical characteristics. Therefore, this disclosure describes techniques for reporting beam-specific delays over frequency.
[0107]
[0114] In one aspect, the UE may report group delay-per-frequency look up tables (LUTs) for different transmit and receive beams. The LUTs may be a set of frequency bins, each associated with a group delay (e.g., in nanoseconds). For example, graph 700 in FIG. 7 may represent group delay per frequency for a particular beam / PRS resource. Rather than reporting a function representing a curve for an example frequency band (i.e., the "U" curve between the two vertical lines in FIG. 7), the UE discretizes the curve into a set of frequency bins (e.g., 10 MHz or 50 MHz in size) and reports the group delay associated with each frequency bin. The UE also reports the beam ID (or PRS resource ID or SRS resource ID, since downlink beams are generally associated with PRS resources and uplink beams are generally associated with SRS resources) for which the group delay per frequency bin is applicable.
[0108]
[0115] To achieve this, a location server (e.g., location server 230, LMF 270) configures PRS resources, PRS resource sets, SRS resources, and SRS resource sets to the UE in positioning assistance data (e.g., LTE Positioning Protocol (LPP) assistance data). Each PRS resource and PRS resource set may be configured to be QCL type D with a source downlink reference signal from a serving cell or a neighboring cell. Similarly, each SRS resource and SRS resource set may be spatially related to a reference downlink reference signal. The UE then configures the UE Rx-Tx parameters (e.g., T Rx→Tx 612) or in a separate transmission, the location server can report the LUT table for each PRS resource ID, PRS resource set ID, SRS resource, and SRS resource set ID used to calculate the UE Rx-Tx parameters. That way, the location server can look up the group delay for the frequencies on which the PRS and SRS resources were transmitted and subtract them from the UE Rx-Tx parameters.
[0109]
[0116] In one aspect, the UE may be configured with PRS / SRS resources and report the LUT(s) before calculating the UE Rx-Tx parameters. For example, the UE may report the LUT in the capability information (e.g., one or more LPP capability messages). In this scenario, the UE may only provide a range of group delays per frequency across different beams. For example, for a 28100 MHz carrier, the group delay may range from 10 ns to 30 ns depending on the beam selection. In this case, the location server will not be able to explicitly associate each beam with a delay per frequency, but it can use this information to weight the received measurements accordingly.
[0110]
[0117] For example, the UE may report 16 LUTs to the location server in the capability information (e.g., LPP capability message) for the UE. The location server may then configure the UE with some set of PRS resources (i.e., some PRS resource set(s)), where each PRS resource is associated with a downlink beam from the base station. The location server may then report the UE Rx-Tx parameters (e.g., T Rx→Tx When reporting the value of LUT "15" for downlink beam "10", the UE may also report that the location server should use, for example, LUT "15" for downlink beam "10". Note that the UE does not need to explicitly identify that for a particular beam ID, a particular LUT should be used to determine the group delay for that beam ID. Rather, the beam ID may be implicit as long as the UE reports a LUT for the PRS resource ID, and the identified PRS resource is received via a particular beam with a particular beam ID.
[0111]
[0118] In one aspect, when the UE reports all of the LUTs for all of the PRS resources, PRS resource sets, etc., for which it is configured (e.g., as capability information) at once, it may associate each LUT with an identifier. In that way, the UE may report the UE Rx-Tx parameters (e.g., T Rx→Tx When reporting LUT (612), it can simply report the ID(s) of the applicable LUT(s). This saves the overhead of transmitting the entire LUT in the report. For example, a 200 MHz frequency band with 20 MHz frequency bins would result in 10 bins. Since group delay is reported in nanosecond levels, each frequency bin would require 8 bits to report the group delay for that bin, for a total of 800 bits for the entire LUT.
[0112]
[0119] Alternatively, rather than reporting all of the LUTs at once, the UE may instead report only the LUT(s) for the PRS and SRS resources used to calculate the UE Rx-Tx parameters. However, the UE may still assign an identifier to each LUT if it can reuse the LUT(s) in the future. Note that, as used herein, a reference to the UE reporting a LUT means that the UE is sending either the entire LUT or an identifier for the LUT, unless otherwise specified. Similarly, a reference to the base station or location server receiving a LUT means that the base station or location server is receiving the entire LUT or an identifier for the LUT, unless otherwise specified.
[0113]
[0120] In one aspect, the LUT used to calculate the UE Rx-Tx parameters may be signaled in an information element (IE) comprising a sequence of tables. Each table may correspond to a carrier frequency on which a PRS or SRS resource is transmitted. Each table may be associated with an identifier and comprise a sequence of values corresponding to a sequence of frequency bins of the carrier frequency. Each value of the sequence of values will represent a group delay in nanoseconds for the corresponding frequency bin. Such an IE may be a field in an LPP message.
[0114]
[0121] As described above with reference to FIG. 6B, the UE knows the average group delay and the standard deviation around it and may therefore be able to compensate for (i.e., calibrate out) the average group delay. Alternatively, the UE may know the average group delay and the standard deviation but not calibrate out anything. In either case, the standard deviation may be different for different beams and frequencies. Thus, in one aspect, the UE may report a LUT for both the average group delay (if the UE has not calibrated it out) and the standard deviation of the average group delay. If the UE has calibrated out the average group delay, it may still report the standard deviation in the LUT.
[0115]
[0122] In one aspect, if the UE reports only one LUT for the UE Rx-Tx parameters, the base station may assume that it applies to all beams (uplink and downlink) used to calculate the UE Rx-Tx parameters. If the UE reports two LUTs, the base station may assume that the first LUT applies to the transmit beam / SRS resource (where the RTT response signal is transmitted) and the second LUT applies to the receive beam / PRS resource (where the RTT measurement signal is received), or vice versa.
[0116]
[0123] In one aspect, if the UE previously reported a LUT (e.g., in a previous positioning session), the UE does not need to report the LUT(s) again unless the UE updates the association between the LUT and PRS / SRS resources. Instead, it needs to report only the new / updated LUT(s). However, the location server (e.g., location server 230, LMF 270) may trigger the UE to re-report the LUT(s) if it determines that they need to be updated (e.g., after some threshold time period).
[0117]
[0124] In one aspect, the UE may report multiple LUTs in a differential manner. For example, the UE may report a first LUT for a first PRS resource ID and then provide the remaining LUT(s) for the remaining RPS resource ID(s) differentially. That is, the UE will simply report the difference between the first LUT and the subsequent LUT(s) rather than the entire table for the subsequent LUT(s).
[0118]
[0125] In one aspect, the LUT may not be associated with a PRS resource ID, but rather with a downlink reference signal used as a QCL type D source reference signal for the PRS resource. For example, as shown in FIG. 8A, if two PRS resources (labeled as "PRS ID2" and "PRS ID3" in FIG. 8A) have the same QCL type D source reference signal, such as the same SSB, PRS, or TRS, the UE does not need to send two LUTs for the two PRS resources to the location server. Rather, since the UE is expected to receive the two PRS resources (i.e., PRS ID2 and PRS ID3) with the same beam when it receives a source reference signal (e.g., SSB, PRS, TRS), the UE can report the LUT and an identifier (e.g., SSB ID, PRS ID, TRS ID) of the source reference signal with which the reported LUT is associated. Because the location server configured the source reference signal for two PRS resources (i.e., PRS ID2 and PRS ID3), whenever it receives the LUT for the source reference signal, it knows that the LUT applies to the two PRS resources.
[0119]
[0126] Similarly, if each SRS resource allocated to a UE comprises SRS spatial relationship information, the LUT may not be associated with an SRS resource ID, but rather with a downlink reference signal that is used as the spatial relationship reference downlink reference signal for the SRS resource, i.e., the LUT for an SRS resource may be associated with a reference downlink reference signal that is the source of the spatial relationship between the downlink receive beam (on which the reference downlink reference signal is received) and the uplink transmit beam (on which the SRS resource is transmitted).
[0120]
[0127] For example, as shown in FIG. 8B, if two SRS resources (labeled as "SRS ID2" and "SRS ID3" in FIG. 8B) have the same spatial relationship reference downlink reference signal, such as the same SSB, PRS, or TRS, the UE does not need to send two LUTs for the two SRS resources to the location server. Rather, because the UE is expected to transmit the two SRS resources (i.e., SRS ID2 and SRS ID3) using beams derived from the spatial relationship reference downlink reference signals (e.g., SSB, PRS, TRS), the UE can report the LUT and the identifiers (e.g., SSB ID, PRS ID, TRS ID) of the reference downlink reference signals with which the reported LUT is associated. Because the location server configured the reference downlink reference signals for the two SRS resources (i.e., SRS ID2 and SRS ID3), whenever it receives the LUTs for the reference downlink reference signals, it knows that the LUTs apply to the two SRS resources.
[0121]
[0128] In one aspect, the UE may send per-beam specific frequency group delay LUT to base stations (both serving and neighboring) participating in the multi-RTT procedure via a location server, and the base stations may send base station Tx-Rx parameters (e.g., T Tx→Rx 622) to the SRS reception. More specifically, the location server computes a position estimate based on measurements from the base stations (e.g., the base station Tx-Rx parameters T Tx→Rx622). The base station receives the uplink SRS from the UE and processes it to obtain base station Tx-Rx parameters. If the base station has knowledge of the LUT from the UE, it can apply this knowledge to adjust the received SRS waveform before deriving the base station Tx-Rx parameters. In one aspect, the UE can report the LUT(s) to a location server using LPP, and the location server will send the LUT(s) to the base station via LTE Positioning Protocol A (LPPa) or NR Positioning Protocol A (NRPPa).
[0122]
[0129] In the case of UE-based positioning, the base station may forward the per-beam specific frequency group delay LUT to the UE (e.g., through a location server or serving base station), and the UE may apply this information to derive UE Tx-Rx parameters before performing positioning estimation.
[0123]
[0130] 9 illustrates an example method 900 for wireless communication according to an aspect of the present disclosure. The method 900 may be performed by a UE (e.g., any of the UEs described herein).
[0124]
[0131] At 910, the UE receives a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from the TRP. In an aspect, the operation 910 may be performed by the WWAN transceiver 310, the receiver(s) 312, the processing system 332, the memory component 340, and / or the LUT manager 342, which and / or all may be considered as means for performing this operation.
[0125]
[0132] At 920, the UE transmits an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam to the TRP. In an aspect, the operation 920 may be performed by the WWAN transceiver 310, the transmitter(s) 314, the processing system 332, the memory component 340, and / or the LUT manager 342, which and / or all may be considered as means for performing this operation.
[0126]
[0133] At 930, the UE determines a parameter (e.g., a UE Rx-Tx parameter) that represents a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal. In an aspect, operation 930 may be performed by the WWAN transceiver 310, the processing system 332, the memory component 340, and / or the LUT manager 342, which and / or all may be considered as means for performing this operation.
[0127]
[0134] At 940, the UE transmits the parameters to a network entity (e.g., the TRP, the location server 230, the LMF 270). In an aspect, the operation 940 may be performed by the WWAN transceiver 310, the transmitter(s) 314, the processing system 332, the memory component 340, and / or the LUT manager 342, which and / or all may be considered as means for performing this operation.
[0128]
[0135] At 950, the UE transmits to a network entity the first lookup table or an identifier of the first lookup table, where the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam. In an aspect, operation 950 may be performed by the WWAN transceiver 310, the transmitter(s) 314, the processing system 332, the memory component 340, and / or the LUT manager 342, which and / or all may be considered as means for performing this operation.
[0129]
[0136] 10 illustrates an example method 1000 for wireless communication according to an aspect of the present disclosure. The method 1000 may be performed by a network entity (e.g., a serving TRP, a location server 230, an LMF 270).
[0130]
[0137] At 1010, the network entity transmits to the UE (e.g., any of the UEs described herein) an identification of at least one downlink reference signal resource to enable the UE to receive a first downlink reference signal from a TRP (e.g., a TRP of any of the base stations described herein) on the at least one downlink reference signal resource using a downlink receive beam. In an aspect, if the network entity is a location server, the operation 1010 may be performed by the network interface 390(s), the processing system 394, the memory component 396, and / or the LUT manager 398, any and / or all of which may be considered as means for performing this operation. If the network entity is a TRP, the operation 1010 may be performed by the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, any or all of which may be considered as means for performing this operation.
[0131]
[0138] At 1020, the network entity transmits to the UE an identification of at least one uplink reference signal resource to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmit beam to the TRP. In an aspect, if the network entity is a location server, the operation 1020 may be performed by the network interface(s) 390, the processing system 394, the memory component 396, and / or the LUT manager 398, any and / or all of which may be considered as a means for performing this operation. If the network entity is a TRP, the operation 1020 may be performed by the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, any or all of which may be considered as a means for performing this operation.
[0132]
[0139] At 1030, the network entity receives from the UE a parameter representing a difference between a reception time at the UE of the first downlink reference signal and a transmission time of the uplink reference signal from the UE. In an aspect, if the network entity is a location server, the operation 1030 may be performed by the network interface(s) 390, the processing system 394, the memory component 396, and / or the LUT manager 398, any and / or all of which may be considered as means for performing this operation. If the network entity is a TRP, the operation 1030 may be performed by the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, any or all of which may be considered as means for performing this operation.
[0133]
[0140] At 1040, the network entity receives from the UE a first lookup table or an identifier of the first lookup table, where the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam. In an aspect, if the network entity is a location server, the operation 1040 may be performed by the network interface(s) 390, the processing system 394, the memory component 396, and / or the LUT manager 398, any and / or all of which may be considered as means for performing this operation. If the network entity is a TRP, the operation 1040 may be performed by the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, any or all of which may be considered as means for performing this operation.
[0134]
[0141] At 1050, the network entity estimates the location of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and the group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table. The network entity may also base the location estimate based on the base station Tx-Rx parameters and group delay(s) received from the TRP. In an aspect, if the network entity is a location server, the operation 1050 may be performed by the network interface(s) 390, the processing system 394, the memory component 396, and / or the LUT manager 398, any and / or all of which may be considered as means for performing this operation. If the network entity is a TRP, the operation 1050 may be performed by the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, any or all of which may be considered as means for performing this operation.
[0135]
[0142] Those skilled in the art will appreciate that information and signals may be represented using any of a wide variety of 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.
[0136]
[0143] 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, 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 implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0137]
[0144] 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 DSP, an ASIC, an 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.
[0138]
[0145] The methods, sequences and / or algorithms described in connection with the aspects disclosed herein may be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules 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.
[0139]
[0146] 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 over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and computer communication media, including any medium that enables 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 in the definition of the medium. 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 with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0140]
[0147] Although the above disclosure illustrates exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and / or actions of the method claims according to the aspects of the present disclosure described herein need not be performed in any particular order. Furthermore, although elements of the present disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. The invention as described in the claims of the original application is set forth below. [C1] A user equipment (UE), Memory, At least one transceiver; and at least one processor communicatively coupled to the memory and to the at least one transceiver, the at least one processor comprising: receiving a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from a transmit receive point (TRP) via the at least one transceiver; causing the at least one transceiver to transmit an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam; determining a parameter representative of a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal; causing the at least one transceiver to transmit the parameters to a network entity; A user equipment (UE) configured to cause the at least one transceiver to transmit a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents frequency-specific group delay information for the downlink receive beam and / or the uplink transmit beam. [C2] The at least one processor: The UE of C1, further configured to cause the at least one transceiver to transmit an identifier associated with the downlink receiving beam to the network entity. [C3] The UE described in C2, wherein the identifier associated with the downlink receiving beam is an identifier of the first downlink reference signal. [C4] The UE of C2, wherein the identifier associated with the downlink receiving beam is an identifier of the at least one downlink reference signal resource. [C5] The at least one processor: The UE of C1, further configured to cause the at least one transceiver to transmit to the network entity a second lookup table or an identifier of the second lookup table, wherein the second lookup table represents frequency-specific group delay information for the uplink transmit beam and wherein the first lookup table represents the frequency-specific group delay information for the downlink receive beam. [C6] The at least one processor: causing the at least one transceiver to transmit to the network entity an identifier associated with the downlink receive beam; and / or The UE of C5, further configured to cause the at least one transceiver to transmit an identifier associated with the uplink transmission beam to the network entity. [C7] the identifier associated with the downlink receive beam is an identifier of the first downlink reference signal; and / or The UE described in C6, wherein the identifier associated with the uplink transmission beam is an identifier of the uplink reference signal. [C8] the identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource; and / or The UE of C6, wherein the identifier associated with the uplink transmission beam is an identifier of the at least one uplink reference signal resource. [C9] the first downlink reference signal is a positioning reference signal (PRS); the uplink reference signal is a sounding reference signal (SRS); the identifier of the at least one downlink reference signal resource is an identifier of a PRS resource or a PRS resource set on which the PRS is transmitted; The UE of C8, wherein the identifier of the at least one uplink reference signal resource is an identifier of an SRS resource or an SRS resource set over which the SRS is transmitted. [C10] The UE of C8, wherein the at least one processor configured to cause the at least one transceiver to transmit the second lookup table comprises the at least one processor configured to cause the at least one transceiver to transmit only a difference between the first lookup table and the second lookup table. [C11] the identifier associated with the downlink receive beam is an identifier of the downlink receive beam; The UE described in C6, wherein the identifier associated with the uplink transmission beam is an identifier of the uplink transmission beam. [C12] the at least one processor: The UE of C6, further configured to receive a second downlink reference signal on the downlink receive beam associated with the reception of the first downlink reference signal from the TRP or a second TRP via the at least one transceiver. [C13] the second downlink reference signal is a quasi-co-located source reference signal for the first downlink reference signal; The UE described in C12, wherein the identifier associated with the downlink receiving beam is an identifier of the second downlink reference signal. [C14] the second downlink reference signal is a spatially related reference downlink reference signal for the uplink reference signal; The UE of C12, wherein the identifier associated with the uplink transmission beam is an identifier of the second downlink reference signal. [C15] The UE of C12, wherein the second downlink reference signal is a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a tracking reference signal (TRS), or a PRS. [C16] The UE of C5, wherein the at least one processor causes the at least one transceiver to transmit the first lookup table or the identifier of the first lookup table before or simultaneously with transmission of the second lookup table or the identifier of the second lookup table to indicate that the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the second lookup table represents the frequency-specific group delay information for the uplink transmit beam. [C17] The UE of C5, wherein the at least one processor causes the at least one transceiver to transmit the second lookup table or the identifier of the second lookup table before or simultaneously with transmission of the first lookup table or the identifier of the first lookup table to indicate that the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the second lookup table represents the frequency-specific group delay information for the uplink transmit beam. [C18] A UE as described in C1, wherein the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the uplink transmit beam. [C19] The at least one processor: The UE of C1, further configured to cause the at least one transceiver to transmit the first lookup table to the network entity prior to reception of the first downlink reference signal from the TRP. [C20] A UE as described in C19, wherein the frequency-specific group delay information represented by the first lookup table comprises a range of an average group delay, a group delay spread, or both for the downlink receive beam and / or the uplink transmit beam. [C21] The UE of C19, wherein the at least one processor causes the at least one transceiver to transmit the identifier of the first lookup table to the network entity after receiving the first downlink reference signal from the TRP. [C22] The UE of C21, wherein the first lookup table is unchanged between transmission of the first lookup table and transmission of the identifier of the first lookup table. [C23] the at least one processor: The UE of C1, further configured to receive, via the at least one transceiver, a trigger from the network entity to transmit the first lookup table. [C24] The UE described in C1, wherein the first lookup table represents a plurality of frequency bins for a carrier frequency at which the first downlink reference signal is transmitted, where each frequency bin is associated with a group delay for the downlink receive beam when formed at a frequency within the frequency bin. [C25] The UE according to C1, wherein the network entity is the TRP or a location server. [C26] A network entity comprising: Memory, At least one network interface; and at least one processor communicatively coupled to the memory and the network interface, the at least one processor comprising: causing the at least one network interface to transmit, to a user equipment (UE), an identification of the at least one downlink reference signal resource, to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource using a downlink receive beam from a transmission receiving point (TRP); causing the at least one network interface to transmit to the UE an identification of the at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmission beam to the TRP; receiving from the UE via the at least one network interface a parameter indicative of a difference between a reception time at the UE of the first downlink reference signal and a transmission time of the uplink reference signal from the UE; receiving a first lookup table or an identifier of the first lookup table from the UE via the at least one network interface, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam; and estimating a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and a group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table. [C27] the at least one processor: The network entity of C26, further configured to receive an identifier associated with the downlink receiving beam from the UE via the at least one network interface. [C28] A network entity as described in C27, wherein the identifier associated with the downlink receive beam is an identifier of the first downlink reference signal. [C29] A network entity as described in C27, wherein the identifier associated with the downlink receiving beam is an identifier of the at least one downlink reference signal resource. [C30] The at least one processor: The network entity of C26, further configured to receive a second lookup table or an identifier of the second lookup table from the UE via the at least one network interface, wherein the second lookup table represents frequency-specific group delay information for the uplink transmit beam and wherein the first lookup table represents the frequency-specific group delay information for the downlink receive beam. [C31] the at least one processor: receiving an identifier associated with the downlink receive beam from the UE via the at least one network interface; The network entity of C30, further configured to receive an identifier associated with the uplink transmission beam from the UE via the at least one network interface. [C32] the identifier associated with the downlink receive beam is an identifier of the first downlink reference signal; A network entity as described in C31, wherein the identifier associated with the uplink transmission beam is an identifier of the uplink reference signal. [C33] the identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource; A network entity as described in C31, wherein the identifier associated with the uplink transmission beam is an identifier of the at least one uplink reference signal resource. [C34] the first downlink reference signal is a positioning reference signal (PRS); the uplink reference signal is a sounding reference signal (SRS); the identifier of the at least one downlink reference signal resource is an identifier of a PRS resource or a PRS resource set on which the PRS is transmitted; The network entity according to C33, wherein the identifier of the at least one uplink reference signal resource is an identifier of an SRS resource or an SRS resource set on which the SRS is transmitted. [C35] the identifier associated with the downlink receive beam is an identifier of the downlink receive beam; A network entity as described in C31, wherein the identifier associated with the uplink transmission beam is an identifier of the uplink transmission beam. [C36] The at least one processor: The network entity of C31, further configured to cause the at least one network interface to transmit, to the UE, identification information of the second at least one downlink reference signal resource, to enable the UE to receive a second downlink reference signal on the second at least one downlink reference signal resource using the downlink receiving beam prior to receiving the first downlink reference signal. [C37] the second downlink reference signal is a quasi-co-located source reference signal for the first downlink reference signal; A network entity as described in C36, wherein the identifier associated with the downlink receive beam is an identifier of the second downlink reference signal. [C38] the second downlink reference signal is a spatially related reference downlink reference signal for the uplink reference signal; A network entity as described in C36, wherein the identifier associated with the uplink transmission beam is an identifier of the second downlink reference signal. [C39] The network entity of C36, wherein the second downlink reference signal is a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a tracking reference signal (TRS), or a PRS. [C40] The network entity of C36, wherein the at least one downlink reference signal resource is the same as the second at least one downlink reference signal resource. [C41] A network entity as described in C30, wherein reception of the first lookup table or the identifier of the first lookup table prior to or simultaneous with reception of the second lookup table or the identifier of the second lookup table indicates that the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the second lookup table represents the frequency-specific group delay information for the uplink transmit beam. [C42] A network entity as described in C30, wherein reception of the second lookup table or the identifier of the second lookup table prior to or simultaneous with reception of the first lookup table or the identifier of the first lookup table indicates that the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the second lookup table represents the frequency-specific group delay information for the uplink transmit beam. [C43] The network entity of C30, wherein the second lookup table comprises only a difference between the first lookup table and the second lookup table. [C44] A network entity as described in C26, wherein the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the uplink transmit beam. [C45] The network entity of C26, wherein the first lookup table is received prior to transmission of the identification information of the at least one downlink reference signal resource to the UE. [C46] A network entity as described in C45, wherein the frequency-specific group delay information represented by the first lookup table comprises a range of average group delay, group delay spread, or both for the downlink receive beam and / or the uplink transmit beam. [C47] The network entity of C45, wherein the identifier of the first lookup table is received after transmission of identification information of the at least one downlink reference signal resource to the UE. [C48] The network entity of C47, wherein the first lookup table is unchanged between receiving the first lookup table and receiving the identifier of the first lookup table. [C49] The at least one processor: The network entity of C26, further configured to cause the at least one network interface to send a trigger to the UE to send the first lookup table. [C50] The network entity of C26, wherein the first lookup table represents a plurality of frequency bins for a carrier frequency at which the first downlink reference signal is transmitted, wherein each frequency bin is associated with a group delay for the downlink receive beam when formed at a frequency within the frequency bin. [C51] The network entity according to C26, wherein the network entity is the TRP or a location server. [C52] 1. A method of wireless communication implemented by a user equipment (UE), comprising: receiving a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from a transmit receive point (TRP); transmitting an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam to the TRP; determining a parameter representative of a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal; transmitting said parameters to a network entity; A method comprising: transmitting a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents frequency-specific group delay information for the downlink receive beam and / or the uplink transmit beam. [C53] The method of C52, further comprising transmitting an identifier associated with the downlink receive beam to the network entity. [C54] The method of C52, further comprising transmitting a second lookup table or an identifier of the second lookup table to the network entity, wherein the second lookup table represents frequency-specific group delay information for the uplink transmit beam and wherein the first lookup table represents the frequency-specific group delay information for the downlink receive beam. [C55] transmitting to the network entity an identifier associated with the downlink receive beam; and / or The method of claim 54, further comprising transmitting an identifier associated with the uplink transmission beam to the network entity. [C56] The method of C55, further comprising receiving a second downlink reference signal from the TRP or a second TRP on the downlink receive beam associated with the reception of the first downlink reference signal. [C57] The method of claim 54, wherein the UE transmits the first lookup table or the identifier of the first lookup table prior to or simultaneously with transmission of the second lookup table or the identifier of the second lookup table to indicate that the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the second lookup table represents the frequency-specific group delay information for the uplink transmit beam. [C58] The method of claim 54, wherein the UE transmits the second lookup table or the identifier of the second lookup table prior to or simultaneously with transmission of the first lookup table or the identifier of the first lookup table to indicate that the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the second lookup table represents the frequency-specific group delay information for the uplink transmit beam. [C59] The method of C52, wherein the first lookup table represents the frequency-specific group delay information for the downlink receive beam and the uplink transmit beam. [C60] The method of C52, further comprising transmitting the first lookup table to the network entity prior to receiving the first downlink reference signal from the TRP. [C61] The method of claim 52, wherein the first lookup table represents a plurality of frequency bins for a carrier frequency at which the first downlink reference signal is transmitted, where each frequency bin is associated with a group delay for the downlink receive beam when formed at a frequency within the frequency bin. [C62] The method according to C52, wherein the network entity is the TRP or a location server. [C63] 1. A method of wireless communication implemented by a network entity, comprising: transmitting, to a user equipment (UE), an identification of at least one downlink reference signal resource, to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource from a transmission receiving point (TRP) using a downlink receive beam; transmitting, to the UE, an identification of the at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmit beam to the TRP; receiving from the UE a parameter indicative of a difference between a receive time at the UE of the first downlink reference signal and a transmit time of the uplink reference signal from the UE; receiving from the UE a first lookup table or an identifier of the first lookup table, wherein the first lookup table represents group delay information per frequency for the downlink receive beam and / or the uplink transmit beam; and estimating a position of the UE based in part on the difference between the receive time of the first downlink reference signal and the transmit time of the uplink reference signal and a group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table. [C64] The method of C63, further comprising receiving an identifier associated with the downlink receive beam from the UE. [C65] The method of C63, further comprising receiving a second lookup table or an identifier of the second lookup table from the UE, wherein the second lookup table represents frequency-specific group delay information for the uplink transmit beam, and wherein the first lookup table represents the frequency-specific group delay information for the downlink receive beam. [C66] receiving, from the UE, an identifier associated with the downlink receive beam; and receiving, from the UE, an identifier associated with the uplink transmission beam. [C67] The method of claim 66, further comprising transmitting to the UE an identification of the second at least one downlink reference signal resource to enable the UE to receive a second downlink reference signal on the second at least one downlink reference signal resource using the downlink receive beam prior to receiving the first downlink reference signal. [C68] the second downlink reference signal is a quasi-co-located source reference signal for the first downlink reference signal; The method of C67, wherein the identifier associated with the downlink receive beam is an identifier of the second downlink reference signal. [C69] the second downlink reference signal is a spatially related reference downlink reference signal for the uplink reference signal; The method of C67, wherein the identifier associated with the uplink transmission beam is an identifier of the second downlink reference signal. [C70] The method of C65, wherein the second lookup table comprises only the difference between the first lookup table and the second lookup table. [C71] The method of C63, wherein the first lookup table is received prior to transmission of the identity of the at least one downlink reference signal resource to the UE. [C72] The method according to C63, wherein the network entity is the TRP or a location server. [C73] A user equipment (UE), means for receiving a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from a transmit receive point (TRP); means for transmitting an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam to the TRP; means for determining a parameter representative of a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; means for transmitting said parameters to a positioning entity; A user equipment (UE) comprising: means for transmitting a first lookup table or an identifier of the first lookup table to the positioning entity, wherein the first lookup table represents frequency-specific group delay information for the downlink receive beam and / or the uplink transmit beam. [C74] A network entity comprising: means for transmitting, to a user equipment (UE), an identification of at least one downlink reference signal resource, to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource from a transmission receiving point (TRP) using a downlink receive beam; means for transmitting, to the UE, an identification of the at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmission beam to the TRP; means for receiving from the UE a parameter indicative of a difference between a reception time at the UE of the first downlink reference signal and a transmission time of the uplink reference signal from the UE; means for receiving from the UE a first lookup table or an identifier of the first lookup table, wherein the first lookup table represents group delay information per frequency for the downlink receive beam and / or the uplink transmit beam; and means for estimating a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and a group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table. [C75] A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions comprising: at least one instruction to instruct a user equipment (UE) to receive a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from a transmit receive point (TRP); at least one instruction to the TRP to instruct the UE to transmit an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam; at least one instruction to instruct the UE to determine a parameter indicative of a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal; at least one instruction to instruct the UE to transmit the parameters to a positioning entity; A non-transitory computer-readable medium comprising at least one instruction instructing the UE to transmit a first lookup table or an identifier of the first lookup table to the positioning entity, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam. [C76] A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions comprising: at least one instruction to instruct a network entity to transmit, to a user equipment (UE), an identification of at least one downlink reference signal resource, to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource from a transmission receiving point (TRP) using a downlink receive beam; at least one instruction to instruct the network entity to transmit to the UE an identification of the at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmission beam to the TRP; at least one instruction to instruct the network entity to receive from the UE a parameter indicative of a difference between a reception time at the UE of the first downlink reference signal and a transmission time of the uplink reference signal from the UE; at least one instruction to instruct the network entity to receive from the UE a first lookup table or an identifier of the first lookup table, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam; and at least one instruction to instruct the network entity to estimate a position of the UE based in part on the difference between the receive time of the first downlink reference signal and the transmit time of the uplink reference signal and a group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
Claims
1. A user equipment (UE), Memory, at least one transceiver coupled to a plurality of antennas; and at least one processor communicatively coupled to the memory and to the at least one transceiver, the at least one processor comprising: receiving a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from a transmit receive point (TRP) via the at least one transceiver; causing the at least one transceiver to transmit an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam; determining a parameter representative of a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal; causing the at least one transceiver to transmit the parameters to a network entity; A user equipment (UE) configured to cause the at least one transceiver to transmit a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam, each beam being transmitted from or received by the multiple antennas.
2. The at least one processor The UE of claim 1 , further configured to cause the at least one transceiver to transmit, to the network entity, an identifier associated with the downlink receive beam.
3. A UE as described in claim 2, wherein the identifier associated with the downlink receiving beam is an identifier of the first downlink reference signal.
4. A UE as described in claim 2, wherein the identifier associated with the downlink receiving beam is an identifier of the at least one downlink reference signal resource.
5. The at least one processor 2. The UE of claim 1, further configured to: cause the at least one transceiver to transmit to the network entity a second lookup table or an identifier of the second lookup table, wherein the second lookup table represents per-frequency group delay information for the uplink transmit beam and wherein the first lookup table represents the per-frequency group delay information for the downlink receive beam.
6. The at least one processor, causing the at least one transceiver to transmit to the network entity an identifier associated with the downlink receive beam; and / or The UE of claim 5 , further configured to: cause the at least one transceiver to transmit, to the network entity, an identifier associated with the uplink transmission beam.
7. The method of claim 1, wherein the identifier associated with the downlink receive beam is an identifier of the first downlink reference signal; and / or The UE of claim 6 , wherein the identifier associated with the uplink transmission beam is an identifier of the uplink reference signal.
8. The method according to claim 7, wherein the identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource; and / or The UE of claim 6 , wherein the identifier associated with the uplink transmission beam is an identifier of the at least one uplink reference signal resource.
9. The method of claim 8, wherein the first downlink reference signal is a positioning reference signal (PRS); the uplink reference signal is a sounding reference signal (SRS); the identifier of the at least one downlink reference signal resource is an identifier of a PRS resource or a PRS resource set on which the PRS is transmitted; The UE of claim 8 , wherein the identifier of the at least one uplink reference signal resource is an identifier of an SRS resource or an SRS resource set over which the SRS is transmitted.
10. The UE of claim 8, wherein the at least one processor being configured to cause the at least one transceiver to transmit the second lookup table comprises the at least one processor being configured to cause the at least one transceiver to transmit only the difference between the first lookup table and the second lookup table.
11. the identifier associated with the downlink receive beam is an identifier of the downlink receive beam; The UE of claim 6 , wherein the identifier associated with the uplink transmission beam is an identifier of the uplink transmission beam.
12. The at least one processor, 7. The UE of claim 6, further configured to receive a second downlink reference signal from the TRP or a second TRP via the at least one transceiver on the downlink receive beam associated with the reception of the first downlink reference signal.
13. The method of claim 12, wherein the second downlink reference signal is a quasi-co-located source reference signal for the first downlink reference signal; The UE of claim 12 , wherein the identifier associated with the downlink receive beam is an identifier of the second downlink reference signal.
14. the second downlink reference signal is a spatially related reference downlink reference signal for the uplink reference signal; The UE of claim 12 , wherein the identifier associated with the uplink transmission beam is an identifier of the second downlink reference signal.
15. The UE of claim 12, wherein the second downlink reference signal is a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a tracking reference signal (TRS), or a PRS.
16. the at least one processor causes the at least one transceiver to transmit, prior to or simultaneously with transmission of the second lookup table or the identifier of the second lookup table, to indicate that the first lookup table represents the per-frequency group delay information for the downlink receive beam and the second lookup table represents the per-frequency group delay information for the uplink transmit beam; or 6. The UE of claim 5, wherein the at least one processor causes the at least one transceiver to transmit the identifier of the second lookup table or the identifier of the first lookup table before or simultaneously with transmitting the identifier of the first lookup table or the identifier of the first lookup table to indicate that the first lookup table represents the per-frequency group delay information for the downlink receive beam and the second lookup table represents the per-frequency group delay information for the uplink transmit beam.
17. the first look-up table represents the group delay information per frequency for the downlink receive beam and the uplink transmit beam; and / or The at least one processor The at least one transceiver is further configured to cause the first look-up table to be transmitted to the network entity prior to reception of the first downlink reference signal from the TRP, preferably the per-frequency group delay information represented by the first look-up table comprises a range of average group delay, group delay spread, or both for the downlink receive beam and / or the uplink transmit beam; and / or The at least one processor causes the at least one transceiver to transmit the identifier of the first look-up table to the network entity after receiving the first downlink reference signal from the TRP, and preferably 2. The UE of claim 1, wherein the first lookup table is unchanged between transmission of the first lookup table and transmission of the identifier of the first lookup table.
18. The at least one processor: and / or further configured to receive a trigger from the network entity via the at least one transceiver to transmit the first look-up table. the first lookup table represents a number of frequency bins for a carrier frequency at which the first downlink reference signal is transmitted, where each frequency bin is associated with a group delay for the downlink receive beam when formed at a frequency within the frequency bin; and / or The UE of claim 1 , wherein the network entity is the TRP or a location server.
19. A network entity comprising: Memory, At least one network interface; and at least one processor communicatively coupled to the memory and the network interface, the at least one processor comprising: causing the at least one network interface to transmit, via a plurality of antennas, an identification of the at least one downlink reference signal resource to a user equipment (UE) to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource using a downlink receive beam from a transmit receive point (TRP); causing the at least one network interface to transmit to the UE an identification of the at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmission beam to the TRP; receiving from the UE via the at least one network interface a parameter indicative of a difference between a reception time at the UE of the first downlink reference signal and a transmission time of the uplink reference signal from the UE; receiving a first lookup table or an identifier of the first lookup table from the UE via the at least one network interface, wherein the first lookup table represents per-frequency group delay information for the downlink receive beams and / or the uplink transmit beams, each beam being transmitted from or received by the plurality of antennas; A network entity configured to estimate a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and a group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
20. The at least one processor: The network entity of claim 19 , further configured to receive an identifier associated with the downlink receive beam from the UE via the at least one network interface.
21. The network entity of claim 20 , wherein the identifier associated with the downlink receive beam is an identifier of the first downlink reference signal.
22. The network entity of claim 20 , wherein the identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource.
23. The at least one processor 20. The network entity of claim 19, further configured to: receive a second lookup table or an identifier of the second lookup table from the UE via the at least one network interface, where the second lookup table represents per-frequency group delay information for the uplink transmit beam and where the first lookup table represents the per-frequency group delay information for the downlink receive beam.
24. The at least one processor: receiving an identifier associated with the downlink receive beam from the UE via the at least one network interface; and receiving an identifier associated with the uplink transmission beam from the UE via the at least one network interface.
24. A network entity according to claim 23.
25. the identifier associated with the downlink receive beam is an identifier of the first downlink reference signal; The network entity of claim 24 , wherein the identifier associated with the uplink transmission beam is an identifier of the uplink reference signal.
26. the identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource; The network entity of claim 24 , wherein the identifier associated with the uplink transmission beam is an identifier of the at least one uplink reference signal resource.
27. the first downlink reference signal is a positioning reference signal (PRS); the uplink reference signal is a sounding reference signal (SRS); the identifier of the at least one downlink reference signal resource is an identifier of a PRS resource or a PRS resource set on which the PRS is transmitted; 27. The network entity of claim 26, wherein the identifier of the at least one uplink reference signal resource is an identifier of an SRS resource or an SRS resource set over which the SRS is transmitted.
28. the identifier associated with the downlink receive beam is an identifier of the downlink receive beam; the identifier associated with the uplink transmission beam is an identifier of the uplink transmission beam.
25. A network entity according to claim 24.
29. The at least one processor 25. The network entity of claim 24, further configured to cause the at least one network interface to transmit, to the UE, an identification of the second at least one downlink reference signal resource, to enable the UE to receive a second downlink reference signal on a second at least one downlink reference signal resource using the downlink receive beam prior to reception of the first downlink reference signal.
30. the second downlink reference signal is a quasi-co-located source reference signal for the first downlink reference signal; 30. The network entity of claim 29, wherein the identifier associated with the downlink receive beam is an identifier of the second downlink reference signal.
31. the second downlink reference signal is a spatially related reference downlink reference signal for the uplink reference signal; 30. The network entity of claim 29, wherein the identifier associated with the uplink transmission beam is an identifier of the second downlink reference signal.
32. 30. The network entity of claim 29, wherein the second downlink reference signal is a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a tracking reference signal (TRS), or a PRS.
33. 30. The network entity of claim 29, wherein the at least one downlink reference signal resource is the same as the second at least one downlink reference signal resource.
34. Receiving the first lookup table or the identifier of the first lookup table prior to or simultaneously with receiving the second lookup table or the identifier of the second lookup table indicates that the first lookup table represents the group delay information per frequency for the downlink receive beam and the second lookup table represents the group delay information per frequency for the uplink transmit beam; and / or 24. The network entity of claim 23, wherein receipt of the second lookup table or the identifier of the second lookup table prior to or simultaneous with receipt of the first lookup table or the identifier of the first lookup table indicates that the first lookup table represents the per-frequency group delay information for the downlink receive beam and the second lookup table represents the per-frequency group delay information for the uplink transmit beam.
35. 1. A method of wireless communication implemented by a user equipment (UE), comprising: receiving a first downlink reference signal on at least one downlink reference signal resource using a downlink receive beam from a transmit receive point (TRP); transmitting an uplink reference signal on at least one uplink reference signal resource using an uplink transmit beam to the TRP; determining a parameter representative of a difference between a receive time of the first downlink reference signal and a transmit time of the uplink reference signal; transmitting said parameters to a network entity; A method comprising: transmitting a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents per-frequency group delay information for the downlink receive beam and / or the uplink transmit beam, wherein each beam is transmitted from or received by multiple antennas.
36. 1. A method of wireless communication implemented by a network entity, comprising: transmitting, to a user equipment (UE), an identification of at least one downlink reference signal resource, to enable the UE to receive a first downlink reference signal on the at least one downlink reference signal resource from a transmission receiving point (TRP) using a downlink receive beam; transmitting, to the UE, an identification of the at least one uplink reference signal resource, to enable the UE to transmit an uplink reference signal on the at least one uplink reference signal resource using an uplink transmission beam to the TRP; receiving from the UE a parameter indicative of a difference between a reception time at the UE of the first downlink reference signal and a transmission time from the UE of the uplink reference signal; receiving from the UE a first lookup table or an identifier of the first lookup table, wherein the first lookup table represents per-frequency group delay information for the downlink receive beams and / or the uplink transmit beams, wherein each beam is transmitted from or received by multiple antennas; and estimating a position of the UE based in part on the difference between the reception time of the first downlink reference signal and the transmission time of the uplink reference signal and a group delay for the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
37. A non-transitory computer readable medium storing computer executable instructions that, when executed, perform the method of any one of claims 35 or 36.
Citation Information
Patent Citations
Method and system for real-time calibration and reporting of processing delays
JP2013517709A
Frequency Bias Compensation between Frequencies for Time Difference Measurement in Position Determination
JP2018510331A
Selecting primary and secondary component carrier for carrier aggregation based on carrier group delay variation, insertion loss, and other carrier attributes
US9999052B1
