Beam-specific per-frequency group delay lookup table signaling for high-precision multiple round-trip time
By exchanging reference signals between user equipment and network entities and using lookup tables to estimate beam delay information, the signaling efficiency and latency issues in 5G wireless communication systems are solved, achieving efficient location estimation and low-latency communication.
Patent Information
- Application Number
- CN202080061865.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-02-19
- Filing Date
- 2020-08-18
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-08-18
AI Technical Summary
Existing wireless communication systems struggle to achieve high signaling efficiency and low latency under the 5G standard, especially in multipath channel environments where the accuracy of beamforming and location estimation is affected by frequency and path delay.
By exchanging reference signals between the user equipment (UE) and network entities, and using lookup tables or lookup table identifiers to estimate the group delay information of downlink and uplink beams, the difference between the reception time and the transmission time is determined, thereby accurately estimating the UE's location.
It improves the signaling efficiency and location estimation accuracy of wireless communication systems, reduces latency, and meets the 5G standard's requirements for high data rates and massive connectivity.
Smart Images

Figure CN114365525B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority under 35 U.S.C. §119 to Greek Patent Application No. 20190100390, filed on September 10, 2019, entitled “BEAM-SPECIFIC GROUP DELAY / FREQUENCY LOOKUP TABLE SIGNALING FOR HIGH-PRECISION MULTI-ROUND-TRIP-TIME,” and U.S. Non-Provisional Patent Application No. 16 / 795,338, filed on February 19, 2020, entitled “BEAM-SPECIFIC GROUP DELAY / FREQUENCY LOOKUP TABLE SIGNALING FOR HIGH-PRECISION MULTI-ROUND-TRIP-TIME,” both of which are assigned to the present assignee and are expressly incorporated herein by reference in their entirety. Technical Field
[0003] Aspects of the present disclosure generally relate to wireless communications. Background Art
[0004] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G networks), and third generation (3G) high speed data, network-enabled wireless services, as well as fourth generation (4G) services (e.g., LTE or WiMax). There are many different types of wireless communication systems in use today, 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) variations of TDMA, and the like.
[0005] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transmission speeds, more connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide data rates of tens of megabits per second for each of tens of thousands of users, with a data rate of 1 gigabit per second for dozens of employees on an office floor. Hundreds of thousands of simultaneous connections should be supported to support large wireless sensor deployments. Therefore, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. In addition, signaling efficiency should be enhanced and latency should be significantly reduced compared to the current standard. Summary of the invention
[0006] A simplified overview of one or more aspects disclosed herein is presented below. As such, the following overview should neither be considered an exhaustive overview of all conceived aspects, nor should the following overview be considered to identify key or decisive elements associated with all conceived aspects or to delineate the scope associated with any particular aspect. Accordingly, the following overview merely has the purpose of presenting certain concepts related to one or more aspects related to the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.
[0007] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, which is communicatively coupled to the memory and the at least one transceiver, and the at least one processor is configured to: receive a first downlink reference signal from a transmission-receive point (TRP) via the at least one transceiver on at least one downlink reference signal resource using a downlink receive beam; cause at least one transceiver to send an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; determine a parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; cause at least one transceiver to send the parameter to a network entity; and cause at least one transceiver to send a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents frequency group delay information of the downlink receive beam and / or the uplink transmit beam.
[0008] In one aspect, a network entity includes: a memory; at least one network interface; and at least one processor, which is communicatively coupled to the memory and the at least one network interface, and the at least one processor is configured to: cause the at least one network interface to send an identifier of at least one downlink reference signal resource to a user equipment (UE) so that the UE can use a downlink receive beam to receive a first downlink reference signal from a TRP on the at least one downlink reference signal resource; cause the at least one network interface to send an identifier of at least one uplink reference signal resource to the UE so that the UE can use an uplink transmit beam to send a first downlink reference signal to the TRP on the at least one uplink reference signal resource. Sending an uplink reference signal; receiving a parameter from the UE via at least one network interface, the parameter representing the difference between the reception time of a first downlink reference signal at the UE and the 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 at least one network interface, wherein the first lookup table represents frequency-based group delay information of a downlink receive beam and / or an uplink transmit beam; estimating the 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 of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
[0009] In one aspect, a method of wireless communication performed 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; sending an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; determining a parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; sending the parameter to a network entity; and sending a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents frequency group delay information for the downlink receive beam and / or the uplink transmit beam.
[0010] In one aspect, a method for wireless communication performed by a network entity includes: sending an identifier of at least one downlink reference signal resource to a UE so that the UE can receive a first downlink reference signal from a TRP on at least one downlink reference signal resource using a downlink receive beam; sending an identifier of at least one uplink reference signal resource to the UE so that the UE can send an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; receiving a parameter from the UE, the parameter representing a difference between a reception time of the first downlink reference signal at the UE 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, wherein the first lookup table represents frequency-based group delay information for a downlink receive beam and / or an 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 of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
[0011] In one aspect, the UE includes: a component for receiving a first downlink reference signal from a TRP on at least one downlink reference signal resource using a downlink receive beam; a component for sending an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; a component for determining a parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; a component for sending the parameter to a network entity; and a component for sending a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents frequency group delay information for the downlink receive beam and / or the uplink transmit beam.
[0012] In one aspect, a network entity includes: a component for sending an identifier of at least one downlink reference signal resource to a UE so that the UE can receive a first downlink reference signal from a TRP on at least one downlink reference signal resource using a downlink receive beam; a component for sending an identifier of at least one uplink reference signal resource to the UE so that the UE can send an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; a component for receiving a parameter from the UE, the parameter representing a difference between a reception time of the first downlink reference signal at the UE and a transmission time of the uplink reference signal from the UE; a component for receiving a first lookup table or an identifier of the first lookup table from the UE, wherein the first lookup table represents frequency-based group delay information for a downlink receive beam and / or an uplink transmit beam; and a component 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 of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
[0013] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions includes computer-executable instructions, which include: at least one instruction instructing the UE to receive a first downlink reference signal from a TRP on at least one downlink reference signal resource using a downlink receive beam; at least one instruction instructing the UE to send an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; at least one instruction instructing the UE to determine a parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; at least one instruction instructing the UE to send the parameter to a network entity; and at least one instruction instructing the UE to send a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents frequency group delay information for the downlink receive beam and / or the uplink transmit beam.
[0014] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions includes computer-executable instructions, the computer-executable instructions including: at least one instruction for directing a network entity to send an identifier of at least one downlink reference signal resource to a UE so that the UE can receive a first downlink reference signal from a TRP on at least one downlink reference signal resource using a downlink receive beam; at least one instruction for directing the network entity to send an identifier of at least one uplink reference signal resource to the UE so that the UE can send an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; at least one instruction for directing the network entity to transmit an uplink reference signal from the UE to the TRP; At least one instruction for receiving a parameter, the parameter representing a difference between a reception time of a first downlink reference signal at a UE and a transmission time of an uplink reference signal from the UE; at least one instruction for directing a network entity to receive a first lookup table or an identifier of a first lookup table from the UE, wherein the first lookup table represents frequency-based group delay information for a downlink receive beam and / or an uplink transmit beam; and at least one instruction for directing the network entity to estimate a position of the UE based in part on the difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal and the group delay of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
[0015] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings are presented to aid in describing aspects of the present disclosure and are provided solely for illustration of these aspects and not limitation thereof.
[0017] Figure 1
[0013] Example wireless communication systems in accordance with various aspects are described.
[0018] Figure 2A and Figure 2B Example wireless network architectures in accordance with various aspects are described.
[0019] FIG. 3A to FIG. 3C is a simplified block diagram of several sample aspects of components that may be employed in a wireless communication node and configured to support communications as taught herein.
[0020] Figure 4 is a diagram illustrating an example of a frame structure for use in a wireless telecommunications system according to aspects of the present invention.
[0021] Figure 5 is a diagram illustrating an exemplary technique for determining the location of a UE using information obtained from multiple base stations.
[0022] Fig. 6A and Figure 6B is a diagram illustrating an exemplary timing of round trip time (RTT) measurement signals exchanged between a base station and a UE in accordance with aspects of the present disclosure.
[0023] Figure 7 Graphs comparing group delay versus frequency are illustrated in accordance with aspects of the present disclosure.
[0024] Fig. 8A Two downlink reference signal resources having the same quasi co-located source reference signal in accordance with aspects of the present disclosure are illustrated.
[0025] Figure 8B Two uplink reference signal resources having the same spatial relationship referencing a downlink reference signal in accordance with aspects of the present disclosure are illustrated.
[0026] Fig. 9 and Fig.10 Methods of wireless communication according to aspects of the present disclosure are described. DETAILED DESCRIPTION
[0027] Various aspects of the present disclosure are provided in the following description and in the relevant figures for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid confusing the relevant details of the present disclosure.
[0028] 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.
[0029] Those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.
[0030] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, elements of a computing device. It will be understood that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. In addition, it may be considered that the sequence of (one or more) actions described herein is fully embodied in any form of computer-readable storage medium, which stores a corresponding set of computer instructions that, when executed, will cause or instruct the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in many different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any of these aspects may be described herein as, for example, "logic configured to perform the described actions."
[0031] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any specific radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet, a laptop, a tracking device, a wearable device (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headsets, 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 via a wireless communication network. A UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber equipment", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile terminal", "mobile station" or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may connect to external networks (such as the Internet) and to other UEs. Of course, other mechanisms are also possible for the UE to connect to the core network and / or the Internet, such as via a wired access network, a wireless local area network (WLAN) network (eg, based on IEEE 802.11, etc.), and the like.
[0032] A base station may operate according to one of several RATs that communicate with a UE depending on the network in which the UE is deployed, and may alternatively be referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a new radio (NR) NodeB (also referred to as a gNB or gNodeB), etc. In addition, in some systems, a base station may provide only edge node signaling functions, while in other systems, a base station may provide additional control and / or network management functions. The communication link through which a UE may send a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link through which a base station may send a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to a UL / reverse or DL / forward traffic channel.
[0033] The term "base station" may refer to a single physical transmission reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station, which corresponds to the cell of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located 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 transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference RF signal the UE is measuring. Since a TRP is a point from which a base station transmits and receives wireless signals, as used herein, references to transmission from a base station or reception at a base station will be understood to refer to a specific TRP of a base station.
[0034] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal.
[0035] According to various aspects, Figure 1An exemplary wireless communication system 100 is shown. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). In one aspect, the macro cell base station may include an eNB in which the wireless communication system 100 corresponds to an LTE network, or a gNB in which the wireless communication system 100 corresponds to an NR network, or a combination of both, and the small cell base station may include a femto cell, a pico cell, a micro cell, etc.
[0036] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a next generation core (NGC)) via a backhaul link 122 and interface to one or more location servers 172 via the core network 170. The base stations 102 may perform functions related to, among other things, transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, non-access stratum (NAS) message distribution, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, positioning, and delivering warning information. The base stations 102 may communicate with each other directly or indirectly via a backhaul link 134 (e.g., via EPC / NGC), which may be wired or wireless.
[0037] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., via some frequency resources (referred to as carrier frequencies), component carriers, carriers, frequency bands, etc.), and can be associated with an identifier (e.g., physical cell identifier (PCI), virtual cell identifier (VCI)) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), etc.) that can provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" can refer to one or both of a logical communication entity and a base station that supports it, depending on the context. In some cases, as long as the carrier frequency can be detected and used for communication within a certain portion of the geographic coverage area 110, the term "cell" can also refer to a geographic coverage area (e.g., sector) of a base station.
[0038] Although the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in a handoff region), some of the geographic coverage areas 110 may substantially overlap with a larger geographic coverage area 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network including small cells and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG).
[0039] The communication link 120 between the base station 102 and the UE 104 may include UL (also referred to as a reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as a forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over 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).
[0040] The wireless communication system 100 may also include a wireless local area network (WLAN) access point (AP) 150 that communicates with a WLAN station (STA) 152 via a communication link 154 in an unlicensed spectrum (e.g., 5 GHz). When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or a listen before talk (LBT) process to determine whether a channel is available before communicating.
[0041] The small cell base station 102' can operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' adopting LTE / 5G in the unlicensed spectrum can enhance the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA) or MulteFire.
[0042] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can communicate with UE 182 at mmW frequencies and / or near mmW frequencies. Extremely high frequency (EHF) is part of RF in the electromagnetic spectrum. The range of EHF is 30GHz to 300GHz, and the wavelength is between 1 mm and 10 mm. The radio waves in this band can be called millimeter waves. Near millimeter waves can be extended down to a frequency of 3GHz, where the wavelength is 100 mm. The super high frequency (SHF) band extends between 3GHz and 30GHz, which is also called centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and UE 182 can utilize beamforming (transmitting and / or receiving) on the mmW communication link 184 to compensate for the extremely high path loss and short distance. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Therefore, it should be understood that the foregoing description is merely exemplary and should not be construed as limiting the various aspects disclosed herein.
[0043] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectional). In the case of transmit beamforming, the network node determines the location of a given target device (e.g., a UE) (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the (one or more) receiving devices. In order 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 one or more transmitters that broadcast the RF signal. For example, a network node can use an antenna array (referred to as a "phased array" or "antenna array") that creates an RF beam that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from each antenna are superimposed to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.
[0044] The transmit beams can be quasi-co-located, which means that they appear to have the same parameters to the receiver (e.g., UE), regardless of whether the transmit antennas of the network nodes themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay and delay spread of the second reference RF signal sent 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 sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.
[0045] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signals received from that direction (e.g., increase its gain level). Thus, when the receiver performs beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain 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 signals received from that direction.
[0046] The receive beams may be spatially correlated. The spatial relationship means that the parameters of 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 transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.
[0047] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, it is a receive beam for receiving downlink reference signals. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station is forming an uplink beam, it is an uplink receive beam, and if the UE is forming an uplink beam, it is an uplink transmit beam.
[0048] In 5G, the spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges, FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In 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 "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection reestablishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those specific to the UE may not be present in the secondary carrier, because the primary uplink and downlink carriers 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 able to change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier with which a certain base station is communicating, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably.
[0049] For example, still refer to Figure 1 , one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system theoretically result in a two-fold increase in data rate (i.e., 40 MHz) compared to a single 20 MHz carrier.
[0050] The wireless communication system 100 may also include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) or peer-to-peer (P2P) links. Figure 1 In the example of FIG. 1 , UE 190 has D2D P2P link 192 and D2D P2P link 194, wherein one of UE 104 is connected to one of base stations 102 through the D2D P2P link 192 (e.g., UE 190 can indirectly obtain cellular connection through it), and WLAN STA 152 is connected to WLAN AP 150 through the D2D P2P link 194 (UE 190 can indirectly obtain WLAN-based Internet connection through it). In the example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.
[0051] The wireless communication system 100 may also include a UE 164 that may communicate with the macrocell base station 102 via a communication link 120 and / or with the mmW base station 180 via a 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 one 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 Figure 1 Only one UE is shown as having a LUT manager 166, but Figure 1 Any of the UEs in the may be configured to perform the UE operations described herein.
[0052] According to various aspects, Figure 2AAn example wireless network architecture 200 is shown. For example, N5GC 210 (also referred to as "5GC") can be functionally viewed as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.) that operate in conjunction 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, and specifically to the control plane functions 214 and the user plane functions 212. In additional configurations, the eNB 224 can also be connected to the NGC 210 via the NG-C 215 to the control plane functions 214 and the NG-U 213 to the user plane functions 212. In addition, the eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include one or more of the eNBs 224 and the gNBs 222. The gNB 222 or the eNB 224 may communicate with the UE 204 (e.g., Figure 1 204). Another optional aspect may include a location server 230 (which may correspond to location server 172), which may communicate with NGC 210 to provide location assistance to UE 204. Location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. Location server 230 may be configured to support one or more location services for UE 204, which may be connected to location server 230 via the core network, NGC 210, and / or via the Internet (not shown). In addition, location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network.
[0053] According to various aspects, Figure 2BAnother example wireless network structure 250 is shown. For example, the NGC 260 (also referred to as "5GC") can be functionally viewed 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 in conjunction to form a core network (i.e., NGC 260). The user plane interface 263 and the control plane interface 265 connect the eNB 224 to the NGC 260, and specifically, to the SMF 262 and the AMF / UPF 264, respectively. In additional configurations, the gNB 222 can also be connected to the NGC 260 via the control plane interface 265 to the AMF / UPF 264 and the user plane interface 263 to the SMF 262. In addition, the eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223 in the presence or absence of gNB direct connectivity to the NGC 260. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include one or more of the eNBs 224 and the gNBs 222. The gNB 222 or the eNB 224 may communicate with the UE 204 (e.g., Figure 1 The base station of the new RAN 220 communicates with the AMF side of the AMF / UPF 264 via the N2 interface, and communicates with the UPF side of the AMF / UPF 264 via the N3 interface.
[0054] The functions of AMF include registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between UE204 and SMF 262, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and short message service function (SMSF) (not shown), and security anchor function (SEAF). AMF also interacts with authentication server function (AUSF) (not shown) and UE 204, and receives intermediate keys established as a result of UE 204 authentication process. In the case of authentication based on UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), AMF retrieves security materials from AUSF. The functions of AMF also include security context management (SCM). SCM receives keys from SEAF, which are used to derive access network specific keys. The functions of the AMF also include location service management of regulatory services, transmission of location service messages between the UE 204 and the location management function (LMF) 270 (which may correspond to the location server 172) and between the new RAN 220 and the LMF 270, allocation of an evolved packet system (EPS) bearer identifier for interworking with the EPS, and notification of mobility events of the UE 204. In addition, the AMF also supports the functions of non-3rd Generation Partnership Project (3GPP) access networks.
[0055] The functions of the UPF include acting as an anchor point for intra-RAT / 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 manipulation), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., UL / DL rate enforcement, reflective QoS marking in DL), UL traffic verification (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.
[0056] The functions of SMF 262 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration at UPF for routing traffic to the appropriate destination, control of part of policy enforcement and QoS, and downlink data notification. The interface via which SMF 262 communicates with the AMF side of AMF / UPF 264 is called the N11 interface.
[0057] Another optional aspect may include LMF 270, which may communicate with NGC 260 to provide location assistance for UE 204. LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. LMF 270 may be configured to support one or more location services for UE 204, which may be connected to LMF 270 via a core network, NGC 260, and / or via the Internet (not shown).
[0058] Figure 3A , Figure 3B and Figure 3C Several sample components (represented by respective blocks) are shown that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including a location server 230 and a LMF 270) to support file transfer operations as taught herein. It should be understood that these components may be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The components shown may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. In addition, 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.
[0059] UE 302 and base station 304 each include a wireless wide area network (WWAN) transceiver 310 and 350, respectively, which is configured to communicate via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 can 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.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). WWAN transceivers 310 and 350 can be configured differently for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, etc.), respectively, and conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, etc.), respectively, according to the designated RAT. Specifically, transceivers 310 and 350 include one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.
[0060] At least in some cases, the UE 302 and the base station 304 also include wireless local area network (WLAN) transceivers 320 and 360, respectively. The WLAN transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The transceivers 320 and 360 may be configured differently to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), respectively, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.), respectively, according to the specified RAT. Specifically, the transceivers 320 and 360 include one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively.
[0061] In some implementations, the transceiver circuitry including the transmitter and the receiver may include an integrated device (e.g., transmitter circuitry and receiver circuitry embodied as a single communication device), may include a separate transmitter device and, in some implementations, a separate receiver device, or may be embodied in other ways in other implementations. In one aspect, the transmitter may include or be coupled to multiple antennas (e.g., antennas 316, 336, and 376), such as an antenna array, which allows the corresponding device to perform transmit "beamforming", as described herein. Similarly, the receiver may include or be coupled to multiple antennas (e.g., antennas 316, 336, and 376), such as an antenna array, which allows the corresponding 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) so that the corresponding device may only receive or transmit at a given time, rather than simultaneously. The wireless communication device of apparatus 302 and / or 304 (eg, one or both of transceivers 310 and 320 and / or 350 and 360 ) may further include a network listening module (NLM) or the like for performing various measurements.
[0062] Devices 302 and 304 also include, at least in some cases, satellite positioning system (SPS) receivers 330 and 370. SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, 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. SPS receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing SPS signals 338 and 378, respectively. SPS receivers 330 and 370 request appropriate information and operations from other systems, and perform calculations required to determine the position of devices 302 and 304 using measurements obtained by any suitable SPS algorithm.
[0063] 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 via a wired or wireless backhaul connection. In some aspects, the network interfaces 380 and 390 may be implemented as a transceiver configured to support communication based on wired or wireless signals. The communication may involve, for example, sending and receiving messages, parameters, or other types of information.
[0064] Apparatuses 302, 304, and 306 also include other components that may be used in conjunction with the operations disclosed herein. UE 302 includes a processor circuit that implements a processing system 332, which is used to provide functions related to, for example, RTT positioning as disclosed herein and to provide other processing functions. Base station 304 includes a processing system 384 for providing functions related to, for example, RTT positioning as disclosed herein and to provide other processing functions. Network entity 306 includes a processing system 394 for providing functions related to, for example, RTT positioning as disclosed herein and to provide other processing functions. In one aspect, processing systems 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), or other programmable logic devices or processing circuits.
[0065] The apparatuses 302, 304, and 306 include memory circuitry that implements memory components 340, 386, and 396, respectively (e.g., each including a memory device), for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). In some cases, the apparatuses 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, which, when executed, cause the apparatuses 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, the LUT managers 342, 388, and 398 may be memory modules (e.g., FIG. 3A to FIG. 3C ), which, when executed by the processing systems 332, 384, and 394 (or a modem processing system, another processing system, etc.), causes the devices 302, 304, and 306 to perform the functions described herein.
[0066] UE 302 may include one or more sensors 344 coupled to processing system 332 to provide movement and / or orientation information independent of motion data derived from signals received by WWAN transceiver 310, WLAN transceiver 320, and / or SPS receiver 330. For example, 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 motion detection sensor. In addition, sensor(s) 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, 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.
[0067] In addition, UE 302 includes a user interface 346 to provide indications (e.g., audible and / or visual indications) to a user and / or receive user input (e.g., when a user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, apparatuses 304 and 306 may also include a user interface.
[0068] Referring to the processing system 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processing system 384. The processing system 384 may implement functions for the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The processing system 384 can provide RRC layer functions associated with 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 of UE measurement reports; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and switching support functions; RLC layer functions associated with transmission of upper layer packet data units (PDUs), error correction through 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 associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel priority.
[0069] The transmitter 354 and the receiver 352 may implement layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be divided 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 domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from the channel estimator may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback sent 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 a corresponding spatial stream for transmission.
[0070] At the UE 302, the receiver 312 receives the signal through its corresponding (one or more) antennas 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 associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they can be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 304. These soft decisions can be based on the channel estimates calculated by the channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to a processing system 332 that implements layer 3 and layer 2 functions.
[0071] In the UL, the processing system 332 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. The processing system 332 is also responsible for error detection.
[0072] Similar to the functions described in conjunction with DL transmissions performed by the base station 304, the processing system 332 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel priority.
[0073] Channel estimates derived by a channel estimator from a reference signal or feedback sent by base station 304 may be used by transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams produced by transmitter 314 may be provided to different antenna(s) 316. Transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0074] UL transmissions are processed at the base station 304 in a similar manner as described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its corresponding antenna(s) 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to the processing system 384.
[0075] In the UL, the processing system 384 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, 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.
[0076] For convenience, devices 302, 304 and / or 306 are FIG. 3A to FIG. 3C The block diagram is shown as including various components that can be configured according to various examples described herein. However, it should be understood that the blocks shown may have different functions in different designs.
[0077] The various components of devices 302, 304, and 306 may communicate with one another via data buses 334, 382, and 392, respectively. FIG. 3A to FIG. 3C The components of can be implemented in various ways. In some implementations, FIG. 3A to FIG. 3CThe components 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). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functions represented by blocks 310 to 346 may be implemented by the processor and (one or more) memory components of UE 302 (e.g., by the execution of appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functions represented by blocks 350 to 388 may be implemented by the processor and (one or more) memory components of base station 304 (e.g., by the execution of appropriate code and / or by appropriate configuration of the processor component). In addition, some or all of the functions represented by blocks 390 to 398 may be implemented by the processor and (one or more) memory components of network entity 306 (e.g., by the execution of appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, as will be appreciated, such operations, actions and / or functions may actually be performed by specific components or combinations of components of the UE, base station, network entity, etc., such as processing systems 332, 384, 394, transceivers 310, 320, 350 and 360, memory components 340, 386 and 396, LUT managers 342, 388 and 398, etc.
[0078] The 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 aspects of the present disclosure. Other wireless communication technologies may have different frame structures and / or different channels.
[0079] LTE (and in some cases, NR) utilizes OFDM on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as frequency tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain by OFDM and in the time domain by SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Therefore, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048 for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into sub-bands. For example, a sub-band may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 sub-bands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.
[0080] LTE supports a single digital scheme (subcarrier spacing, symbol length, etc.). In contrast, NR may support multiple digital schemes, for example, 15kHz, 30kHz, 60kHz, 120kHz, and 204kHz or larger subcarrier spacings may be available. Table 1 provided below lists some of the various parameters for different NR digital schemes.
[0081]
[0082]
[0083] Table 1
[0084] exist Figure 4 In the example of , a 15kHz digital scheme is used. Therefore, in the time domain, a frame (e.g., 10 milliseconds (ms)) is divided into 10 equally sized subframes (each 1 ms), and each subframe includes one time slot. Figure 4 , time is represented horizontally (eg, on the X-axis) by time increasing from left to right, and frequency is represented vertically (eg, on the Y-axis) by frequency increasing (or decreasing) from bottom to top.
[0085] A resource grid may be used to represent a time slot, each of which includes one or more time-parallel resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 4 In the digital scheme of , for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain (OFDM symbols for DL and SC-FDMA symbols for UL), for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six 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.
[0086] like Figure 4 As described in , 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), with exemplary locations at Figure 4 are marked with an "R".
[0087] In some cases, Figure 4 The CSI-RS described in the figure may be a positioning reference signal (PRS). A set of resource elements used to send PRS is referred to as a "PRS resource". A set of resource elements may span multiple PRBs in the frequency domain and N (e.g., 1 or greater than 1) consecutive symbols within a time 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: a PRS resource identifier (ID), a sequence ID, a comb size-N, a resource element offset in the frequency domain, a starting time slot and a starting symbol, a symbol number / PRS resource (i.e., a duration of a PRS resource), and QCL information (e.g., a QCL with other DL reference signals). Currently, one antenna port is supported. The comb size indicates the number of subcarriers in each symbol carrying PRS. For example, a comb size of comb-4 means that every fourth subcarrier of a given symbol carries PRS.
[0088] A "PRS resource set" is a set of PRS resources used to send a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in the PRS resource set are associated with the same TRP. The PRS resource set is identified by a PRS resource set ID and can be associated with a specific TRP (identified by a cell ID) sent by the antenna panel of the base station. The PRS resource ID in the PRS resource set is associated with a single beam (and / or beam ID) sent from a single TRP (where the TRP can send one or more beams). That is, each PRS resource of a PRS resource set can be sent on a different beam, and therefore a "PRS resource" or just a "resource" may also be referred to as a "beam". It should be noted that this does not have any implication as to whether the TRP and the beam on which the PRS is sent are known to the UE.
[0089] A "PRS instance" or "PRS opportunity" is one instance of a periodically repeating time window (e.g., a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS opportunity may also be referred to as a "PRS positioning opportunity," "PRS positioning instance," "positioning opportunity," "positioning instance," or simply "opportunity" or "instance."
[0090] It should be noted that the terms "positioning reference signal" and "PRS" may sometimes refer to a specific reference signal used for positioning in an LTE system. However, as used herein, unless otherwise indicated, the terms "positioning reference signal" and "PRS" refer to any type of reference signal that can 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.
[0091] In NR, there may be no requirement for precise timing synchronization across the network. Instead, having coarse time synchronization across gNBs (e.g., within the cyclic prefix (CP) duration of an OFDM symbol) may be sufficient. RTT-based methods typically only require coarse timing synchronization and, therefore, may be a better positioning method in NR.
[0092] In network-centric RTT estimation, a serving base station (e.g., base station 102) directs 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 typically a serving base station, since at least three base stations are required). One of the more base stations transmits the RTT measurement signal on a low reuse resource (e.g., a resource used by the base station to transmit system information) allocated by the network (e.g., location server 230, LMF 270). The UE records the arrival time (also referred to as reception time, reception time, received time, or arrival time (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), and sends a common or individual RTT response message (e.g., SRS, UL-PRS) to one or more base stations (e.g., when directed by its serving base station), and may include the difference T between the ToA of the RTT measurement signal and the transmission time of the RTT response message in the payload of each RTT response message. Rx→Tx (For example, Fig. 6A T Rx→Tx 612). The RTT response message will include a reference signal from which the base station can deduce the ToA of the RTT response. By calculating the difference T between the transmission time of the RTT measurement signal and the ToA of the RTT response Tx→Rx (For example, Fig. 6A T Tx→Rx 622) and the difference T reported by UE Rx→Tx (For example, Fig. 6A T Rx→Tx 612), the base station (or positioning entity) can deduce the propagation time between the base station and the UE, and can then determine the distance between the UE and the base station by assuming the speed of light during the propagation time from the propagation time.
[0093] UE-centric RTT estimation is similar to the network-based approach, except that the UE sends an uplink RTT measurement signal (e.g., when directed by a serving base station), which is received by multiple base stations in the UE's neighborhood. Each involved base station responds with a downlink RTT response message, which may include 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 in the RTT response message payload.
[0094] For both network-centric and UE-centric procedures, the side performing the RTT calculation (network or UE) typically (although not necessarily always) sends a first message or signal (e.g., an RTT measurement signal), while the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the first message or signal and the transmission time of the RTT response message or signal.
[0095] Figure 5 An exemplary wireless communication system 500 is illustrated according to aspects of the present disclosure. Figure 5 In the example of , UE 504 (which may correspond to any of the UEs described herein) is attempting to compute 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.) in computing an estimate of its location. UE 504 may use RF signals and standardized protocols for modulation of the RF signals and exchange of information packets to wirelessly communicate with multiple base stations 502-1, 502-2, and 502-3 (collectively referred to as base stations 502, and which may correspond to any of the base stations described herein). By extracting different types of information from the exchanged RF signals and utilizing the layout of the wireless communication system 500 (i.e., the location, geometry, etc. of the base stations), UE 504 may determine its location in a predetermined reference coordinate system or assist in determining its location in a predetermined reference coordinate system. In one aspect, UE 504 may specify its location using a two-dimensional coordinate system; however, the aspects disclosed herein are not limited thereto and may also be applicable to determining a location using a three-dimensional coordinate system where additional dimensions are desired. In addition, as will be appreciated, while Figure 5 One UE 504 and three base stations 502 are illustrated, but there may be more UEs 504 and more or fewer base stations 502.
[0096] To support position estimation, the base station 502 may be configured to broadcast reference RF signals (e.g., PRS, NRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to the UE 504 in its coverage area to enable the UE 504 to measure the characteristics of such reference RF signals. For example, the UE 504 may measure the ToA of a particular reference RF signal transmitted by at least three different base stations 502, and may report these ToAs (and additional information) back to the serving base station 502 or another positioning entity (e.g., location server 230, LMF 270) using an RTT positioning method.
[0097] In an aspect, although described as UE 504 measuring a reference RF signal from base station 502, UE 504 may measure a reference RF signal from one of a plurality of cells supported by base station 502. In the case where UE 504 measures a reference RF signal sent by a cell supported by base station 502, at least two other reference RF signals measured by UE 504 to perform the RTT procedure will be from cells supported by base stations 502 different from the first base station 502 and have good or poor signal strength at UE 504.
[0098] In order to determine the position (x, y) of UE 504, the entity determining the position of UE 504 needs to know the position of base station 502, which can be represented as (x, y) in the reference coordinate system. k ,y k ), among which Figure 5 In the example of , k = 1, 2, 3. In the case where one of the base station 502 (e.g., serving base station) or UE 504 determines the location of UE 504, the location of the base station 502 in question may be provided to the serving base station 502 or UE 504 by a location server (e.g., location server 230, LMF 270) having knowledge of the network geometry. Alternatively, the location server may determine the location of UE 504 using known network geometry.
[0099] Either the UE 504 or the corresponding base station 502 may determine 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 may be performed and converted into a distance (d k ). As discussed 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 can utilize calibration to remove any processing delays. In some environments, it can be assumed that the processing delays of the UE 504 and the base station 502 are the same. However, this assumption may not actually be true.
[0100] Once each distance d k Once the location (x, y) of UE 504 is determined, UE 504, base station 502 or a location server (e.g., location server 230, LMF 270) can solve the location (x, y) of UE 504 by using various known geometric techniques (such as triangulation). Figure 5 It can be seen that the location of UE 504 is ideally located at the common intersection of three semicircles, each of which has a radius d k and center (x k ,y k ) definition, where k = 1, 2, 3.
[0101] In some cases, additional information may be obtained in the form of an angle of arrival (AoA) or angle of departure (AoD) that defines a straight line direction (e.g., which may be in a horizontal plane or in three dimensions) or a range of possible directions (e.g., from the location of base station 502 for UE 504). The intersection of the two directions at or near a point (x, y) may provide another position estimate for UE 504.
[0102] A location estimate (e.g., for a UE 504) may be referred to by other names, such as a location estimate, a position fix, a fixed point, a location fix, a fixed, etc. The location estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be urban and include a street address, a postal address, or some other verbal description of the location. The location estimate may be further defined relative to some other known location, or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). The location estimate may include an expected error or uncertainty (e.g., by including an area or volume that is expected to include the location with some specified or default confidence level).
[0103] Fig. 6A 600A is a diagram illustrating an exemplary 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) according to aspects of the present disclosure. Fig. 6A In the example of FIG. 6 , 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 has a certain propagation delay T as it travels from the base station 602 to the UE 604. Prop At time T2 (ToA of RTT measurement signal 610 at UE 604), UE 604 receives / measures RTT measurement signal 610. After a certain UE processing time, UE 604 sends RTT response signal 620 at time T3. Prop Thereafter, the base station 602 receives / measures the RTT response signal 620 from the UE 604 at time T4 (ToA of the RTT response signal 620 at the base station 602).
[0104] In order 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 jointly processes all resource elements (REs) on the channel on which the transmitter is transmitting the reference signal, and performs an inverse Fourier transform to convert the received reference signal to the time domain. Converting the received reference signal to the time domain is called estimating the channel energy response (CER). The CER shows the peaks on the channel over time, and therefore the earliest "significant" peak should correspond to the ToA of the reference signal. In general, the receiver will use a noise-related quality threshold to filter out the mixed local peaks, so as to roughly correctly identify the significant peaks on the channel. For example, the receiver can select the ToA estimate that is the earliest local maximum of the CER, which is at least X dB higher than the median of the CER and lower than the maximum Y dB of the main peak on the channel. The receiver determines the CER for each reference signal from each transmitter in order to determine the ToA of each reference signal from different transmitters.
[0105] The RTT response signal 620 may explicitly include the difference between time T3 and time T2 (ie, T Rx→Tx 612). Alternatively, it can be derived from the timing advance (TA), i.e., the relative UL / DL frame timing and canonical position of the UL reference signal. (Note that TA is typically the RTT between the base station and the UE, or double the propagation time in one direction.) Using this measurement and the difference between time T4 and time T1 (i.e., T Tx→Rx 622), the base station 602 (or other positioning entities, such as the location server 230, LMF 270) can calculate the distance to the UE 604 as:
[0106]
[0107] Where c is the speed of light.
[0108] Figure 6B 600B is a diagram illustrating an exemplary timing of RTT measurement signals exchanged between a base station 602 and a UE 604 according to aspects of the present disclosure. Diagram 600B is similar to diagram 600A, except that diagram 600B includes processing delays that occur at both the base station 602 and the UE 604 when sending and receiving the RTT measurement signal 610 and the RTT response signal 620.
[0109] Specifically, on the base station 602 side, there is a transmission delay T 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) sends the RTT measurement signal 610. gNB , TxOn the UE 604 side, there is a reception delay 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 transmission delay T between the time when the baseband of the UE 104 generates the RTT response signal 620 and the time when the antenna transmits the RTT response signal 620. UE,Tx On the base station 602 side, there is a reception delay 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 .
[0110] The delay between the baseband and the antenna is referred to as the RF front-end (RFFE) group delay. The group delay is the time delay of the amplitude envelope (a smooth curve outlining the end values of the sine wave) of the various sinusoidal components of the RF signal passing through the device (e.g., UE 604, base station 602), and is a function for each sinusoidal component. In one aspect, the UE 604, for example, may know the average group delay (e.g., across other factors that may affect the group delay in a particular frequency, such as temperature, construction / manufacturing errors, etc.) and the standard deviation around the group delay, and may therefore be able to compensate (i.e., calibrate) the average group delay. Alternatively, the UE 604 may know the average group delay and the standard deviation, but may not calibrate anything. The average group delay and the standard deviation of the average group delay are referred to herein as group delay information.
[0111] The base station 602 compensates for its own RFFE group delay to determine the actual transmission time and reception time 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, LMF 270) can then determine the actual propagation delay T between the base station 602 and the UE 604. Prop , and thus determine the distance between base station 602 and UE 604. Alternatively, UE 604 may report its RFFE group delay rather than compensating for the RFFE group delay itself, and base station 602 (or other positioning entity) subtracts the reported RFFE group delay to determine the propagation delay T Prop And the final distance between the base station 602 and the UE 604.
[0112] The UE 604 may perform the RTT procedure with multiple base stations 602. However, the RTT procedure does not require synchronization between these base stations 602.
[0113] With respect to downlink beam management, several options are currently supported for assisting the UE in performing 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 as a 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 scanning on downlink PRS resources transmitted through the same downlink spatial domain transmission filter. As a third option, the UE may use a fixed receive beam to receive downlink PRS resources transmitted through different downlink spatial domain transmission filters.
[0114] Several options are currently supported for uplink beam management / alignment towards the serving cell and neighboring cells for positioning purposes. As a first option, the spatial relationship between the reference downlink reference signal from the serving cell or neighboring cell and the target SRS can be configured. The reference downlink reference signal that can be used includes at least the SSB transmitted on the cell. As a second option, the UE can perform a transmit beam scan for uplink SRS transmission across multiple uplink SRS resources. As a third option, the UE can 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 send multiple SRS resources with different spatial relationships in the same OFDM symbol, as was the case previously.
[0115] Referring to the group delay in more detail, there are multiple sources of variation in the group delay of the UE. An accurate estimate of the estimated group delay is important because it affects the estimation accuracy. In general, one nanosecond (ns) of time translates to one foot in positioning accuracy. Therefore, 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, it is unacceptable for high-accuracy positioning scenarios (e.g., centimeter-level accuracy).
[0116] One source of variation in group delay is component specific (for both analog and digital paths). That is, for both analog and digital paths, the physical components or assemblies of the UE contribute to the group delay. To determine the resulting group delay, the reference design (multiple instances) should be tested to measure component-to-component variation. Customers and vendors with dedicated designs typically perform their own testing and provide this information, for example, in application notes or as part of a software release. This testing also includes third-party components, since it is the designer's responsibility to use good components.
[0117] Another source of variation is frequency specific. For example, the group delay for the lower and upper edges of the 5 GHz band may differ by 500 picoseconds (ps). Thus, the group delay received on one subcarrier may be different from the group delay of a signal received on a different subcarrier. Figure 7 Graph 700 comparing group delay (on the Y-axis) versus frequency (on the X-axis) according to aspects of the present disclosure. A particular 200 MHz frequency band (2493 MHz to 2693 MHz) is shown between the two vertical lines. Within this frequency band, the UE components have been designed so that the group delay is as constant as possible. However, this is not entirely possible; therefore, between the vertical lines is the "U" shape of the graph. For example, Figure 7 As shown in , at a frequency of 2498 MHz, there is a group delay of 18.333 ns, while at a frequency of 2613 MHz, there is a group delay of 3.52 ns. In order to determine the possible group delay by frequency band, the UE should be calibrated by channel in the frequency band, although some channels can be avoided for RTT and therefore will not need to be tested.
[0118] Yet another source of variation is path specific. That is, the 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 may affect group delay include calibration errors (e.g., technical or procedural errors), measurement accuracy, etc.
[0119] Another source of variation in group delay discussed in this disclosure is beam specific. Not only does group delay vary with frequency, as discussed above with reference to Figure 7 discussed above; and varies based on the specific receive / transmit beam used within that frequency. This is because different sets of antenna components of the antenna panel form different beams, and therefore different beams will have different physical characteristics. Therefore, this disclosure describes techniques for reporting beam-specific delays for a frequency.
[0120] In one aspect, the UE may report a group delay per frequency lookup table (LUT) for different transmit and receive beams. The LUT may be a set of frequency bins, each associated with a group delay (e.g., in nanoseconds). For example, Figure 7 The graph 700 in FIG. 700 may represent the group delay by frequency for a particular beam / PRS resource. Rather than reporting a function representing a curve for an example frequency band (ie, Figure 7The UE may discretize the curve into a set of frequency bins (e.g., 10 MHz or 50 MHz in size) and report the group delay associated with each frequency bin. The UE also reports a beam ID (or PRS resource ID or SRS resource ID, since downlink beams are usually associated with PRS resources and uplink beams are usually associated with SRS resources), where the group delay per frequency bin applies to the beam ID.
[0121] To achieve this, a location server (e.g., location server 230, LMF 270) configures the 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 can be configured as QCL type D in the case of a source downlink reference signal from a serving cell or a neighboring cell. Similarly, each SRS resource and SRS resource set can be spatially correlated with a reference downlink reference signal. The UE can then use UE Rx-Tx parameters (e.g., T Rx→Tx 612) or in a separate transmission, reports a LUT table for each PRS resource ID, PRS resource set ID, SRS resource, and SRS resource set ID used to calculate the UERx-Tx parameters. In this way, the location server can look up the group delay for the frequency on which the PRS and SRS resources are transmitted and subtract the group delay from the UERx-Tx parameters.
[0122] In one aspect, the UE may report the LUT before configuring with PRS / SRS resources and calculating the UE Rx-Tx parameters. For example, the UE may report the LUT in capability information (e.g., one or more LPP capability messages). In this scenario, the UE may provide only a group delay range per frequency across different beams. For example, for a 28100 MHz carrier, the group delay range is 10 ns to 30 ns depending on the selection of beams. In this case, the location server will not be able to explicitly associate each beam with a per-frequency delay, but it may use this information to weight the received measurements accordingly.
[0123] For example, the UE may report 16 LUTs to the location server in the capability information for the UE (e.g., LPP capability message). The location server may then configure the UE with a certain set of PRS resources (i.e., some PRS resource sets), each PRS resource being associated with a downlink beam from a base station. Then, when reporting the UE Rx-Tx parameters (e.g., T Rx→Tx612), the UE may also report that the location server should use, for example, LUT "15" for downlink beam "10". It should be noted that the UE does not need to explicitly identify that for a particular beam ID, a particular LUT applies to determine the group delay for that beam ID. Instead, the beam ID may imply that the UE reports the LUT for the PRS resource ID so far, and the identified PRS resource is received via a particular beam with a particular beam ID.
[0124] In one aspect, when the UE reports all of the LUTs for all PRS resources, PRS resource sets, etc. that the UE has configured (e.g., as capability information) at one time, the UE may associate each LUT with an identifier. In this manner, when the UE reports UE Rx-Tx parameters (e.g., T Rx→Tx 612), the UE can simply report the ID of the applicable LUT. This saves the additional overhead of sending the entire LUT in the report. For example, a 200MHz band with 20MHz frequency bins will result in 10 bins. Since the group delay is reported in nanometers, each frequency bin will require 8 bits to report the group delay for that frequency bin for a total of 800 bits for the entire LUT.
[0125] Alternatively, instead of reporting all LUTs at once, the UE may instead report LUTs only for PRS and SRS resources used to calculate UE Rx-Tx parameters. However, if the UE may still reuse the LUTs in the future, the UE may still assign identifiers to each LUT. It should be noted that, as used herein, reference to the UE reporting the LUT means that the UE is sending the entire LUT or an identifier of the LUT, unless otherwise specified. Similarly, reference to the base station or location server receiving the LUT means that the base station or location server is receiving the entire LUT or an identifier of the LUT, unless otherwise specified.
[0126] In one aspect, the LUT for calculating the UE Rx-Tx parameters may be signaled in an information element (IE) comprising a series of tables. Each table may correspond to a carrier frequency on which PRS resources or SRS resources are transmitted. Each table may be associated with an identifier and include a series of values for a series of frequency regions corresponding to the carrier frequency. Each value in the series of values will represent the group delay in nanoseconds for the corresponding frequency region. The IE may be a field in an LPP message.
[0127] As mentioned above Figure 6BAs discussed, the UE may know the average group delay and its standard deviation, and thus be able to compensate (i.e., calibrate) the average group delay. Alternatively, the UE may know the average group delay and the standard deviation, but may not calibrate anything. In both cases, the standard deviation may be different for different beams and frequencies. Therefore, in one aspect, the UE may report a LUT for the average group delay (if the UE is not calibrating the average group delay) and the standard deviation of the average group delay. If the UE is calibrating the average group delay, the UE may still report the standard deviation in the LUT.
[0128] In one aspect, if the UE reports only one LUT for 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 (on which the RTT response signal is sent) and the second LUT applies to the receive beam / PRS resource (on which the RTT measurement signal is sent), or vice versa.
[0129] In one aspect, if the UE has previously reported the LUT (e.g., in a previous positioning session), then unless the UE updates the association between the LUT and the PRS / SRS resources, the UE will not need to report the LUT again. Instead, the UE needs to report only any new / updated LUT. However, if the location server determines that the LUT needs to be updated (e.g., after a certain threshold period of time), the location server (e.g., location server 230, LMF 270) can trigger the UE to re-report the LUT.
[0130] 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 LUTs for the remaining RPS resource IDs in a different manner. That is, the UE will only report the difference between the first LUT and the subsequent LUTs, rather than the entire table of subsequent LUTs.
[0131] In one aspect, the LUT may not be associated with a PRS resource ID, but may actually be associated with a downlink reference signal used as a QCL type D source reference signal for a PRS resource. Fig. 8A As shown in Fig. 8AIf two PRS resources (i.e., PRS ID2 and PRS ID3) have the same QCL type D source reference signal, such as the same SSB, PRS or TRS, then there is no need to send two LUTs for the two PRS resources to the location server for the UE. Instead, since the UE is expected to receive two PRS resources (i.e., PRS ID2 and PRS ID3) with the same beam, as the UE receives the source reference signal (e.g., SSB, PRS, TRS), the UE can report the LUT and identifier (e.g., SSB ID, PRS ID, TRSID) of the source reference signal, and the reported LUT is associated with the identifier of the LUT. Because the location server has configured the source reference signal for the two PRS resources (i.e., PRS ID2 and PRS ID3), as long as it receives the LUT for the source reference signal, the UE knows that the LUT applies to both PRS resources.
[0132] Similarly, in the case where each SRS resource allocated to a UE is provided with SRS spatial relationship information, the LUT may not be associated with the SRS resource ID, but is actually associated with a downlink reference signal used as a spatial relationship reference downlink reference signal for the SRS resource. That is, the LUT for an SRS resource may be associated with a reference downlink reference signal that is the source of the spatial relationship between a downlink receive beam (on which the reference downlink reference signal is received) and an uplink transmit beam (on which the SRS resource is transmitted).
[0133] For example, Figure 8B As shown in Figure 8B If two SRS resources (i.e., SRS ID2 and SRS ID3) have the same spatially related reference downlink reference signal, such as the same SSB, PRS, or TRS, then it is not necessary for the UE to send two LUTs for the two SRS resources to the location server. Alternatively, since the UE expects to transmit the two SRS resources (i.e., SRS ID2 and SRS ID3) with beams derived from the spatially related reference downlink reference signal (e.g., SSB, PRS, TRS), the UE can report the LUT and identifier (e.g., SSB ID, PRS ID, TRSID) of the reference downlink reference signal, and the reported LUT is associated with the reference downlink reference signal. Because the location server has configured the reference downlink reference signal for the two SRS resources (i.e., SRS ID2 and SRS ID3), as long as the location server receives the LUT of the reference downlink reference signal, it knows that the LUT applies to both SRS resources.
[0134] In one aspect, the UE may send the LUT of beam-specific per-frequency group delay to base stations (both serving base stations and neighboring base stations) participating in the multi-RTT procedure via the location server and transmit the LUT of beam-specific per-frequency group delay to the base stations (both serving base stations and neighboring base stations) when transmitting the base station Tx-Rx parameters (e.g., Fig. 6A T Tx→Rx The base station may apply this information to SRS reception before forwarding it to the location server for use in the location estimate at 622. More specifically, although the location server calculates the location estimate, the location server does so based on measurements from the base station (e.g., Fig. 6A Base station Tx-Rx parameters T Tx→Rx 622). The base station receives an uplink SRS from the UE and processes the uplink SRS to obtain base station Tx-Rx parameters. If the base station has knowledge of the LUT from the UE, the base station 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 to the location server using LPP, and the location server will send the LUT to the base station via LTE Positioning Protocol A (LPPa) or NR Positioning Protocol A (NRPPa).
[0135] In the case of UE-based positioning, the base station may forward the LUT of beam-specific per-frequency group delays to the UE (e.g., via a location server or serving base station), and the UE may apply this information to derive UE Tx-Rx parameters before performing positioning estimation.
[0136] Fig. 9 An exemplary method 900 for wireless communication according to aspects of the present disclosure is illustrated. The method 900 may be performed by a UE (eg, any of the UEs described herein).
[0137] At 910, the UE receives a first downlink reference signal from the TRP on at least one downlink reference signal resource using a downlink receive beam. In an aspect, operation 910 may be performed by all of the WWAN transceiver 310, the receiver 312, the processing system 332, the memory component 340, and / or the LUT manager 342, and or may be considered as components for performing such operation.
[0138] At 920, the UE transmits an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam. In an aspect, operation 920 may be performed by the WWAN transceiver 310, the transmitter 314, the processing system 332, the memory component 340, and / or the LUT manager 342, and or all of the components that may be considered as components for performing this operation.
[0139] At 930, the UE determines a parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal (e.g., a UE Rx-Tx parameter). In an aspect, operation 930 may be performed by all of the WWAN transceiver 310, the processing system 332, the memory component 340, and / or the LUT manager 342, and or may be considered as a means for performing such operation.
[0140] At 940, the UE sends the parameters to a network entity (e.g., TRP, location server 230, LMF 270). In an aspect, operation 940 may be performed by WWAN transceiver 310, transmitter 314, processing system 332, memory component 340, and / or LUT manager 342, and or all of the components that may be considered as components for performing such operation.
[0141] At 950, the UE sends a first lookup table or an identifier of the first lookup table to a network entity, wherein the first lookup table represents per-frequency group delay information for a downlink receive beam and / or an uplink transmit beam. In an aspect, operation 950 may be performed by the WWAN transceiver 310, the transmitter 314, the processing system 332, the memory component 340, and / or the LUT manager 342, and or all of the components that may be considered as components for performing this operation.
[0142] Fig.10 An exemplary method 1000 for wireless communication according to aspects of the present disclosure is described. The method 1000 may be performed by a network entity (eg, serving TRP, location server 230, LMF 270).
[0143] At 1010, the network entity sends an identification of at least one downlink reference signal resource to a UE (e.g., any of the UEs described herein) 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 one aspect, where the network entity is a location server, operation 1010 may be performed by the network interface 390, the processing system 394, the memory component 396, and / or the LUT manager 398, and or all of the components that may be considered to be used to perform this operation. Where the network entity is a TRP, operation 1010 may be performed by the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, and any or all of the components that may be considered to be used to perform this operation.
[0144] At 1020, the network entity sends an identification of at least one uplink reference signal resource to the UE to enable the UE to send an uplink reference signal to the TRP on the at least one uplink reference signal resource using an uplink transmit beam. In one aspect, where the network entity is a location server, operation 1020 may be performed by the network interface 390, the processing system 394, the memory component 396, and / or the LUT manager 398, and or all of the components that may be considered to be used to perform this operation. Where the network entity is a TRP, operation 1020 may be performed by any one or all of the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, and or all of the components that may be considered to be used to perform this operation.
[0145] At 1030, the network entity receives a parameter from the UE, the parameter representing a difference between a reception time of a first downlink reference signal at the UE and a transmission time of an uplink reference signal from the UE. In one aspect, where the network entity is a location server, operation 1030 may be performed by the network interface 390, the processing system 394, the memory component 396, and / or the LUT manager 398, and or all of the components that may be considered to be used to perform this operation. Where the network entity is a TRP, operation 1030 may be performed by any one or all of the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, and may be considered to be used to perform this operation.
[0146] At 1040, the network entity receives 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 a downlink receive beam and / or an uplink transmit beam. In one aspect, where the network entity is a location server, operation 1040 may be performed by the network interface 390, the processing system 394, the memory component 396, and / or the LUT manager 398, and or all of the components that may be considered to be used to perform this operation. Where the network entity is a TRP, operation 1040 may be performed by any one or all of the WWAN transceiver 350, the processing system 384, the memory 386, and / or the LUT manager 388, and or all of the components that may be considered to be used to perform this operation.
[0147] At 1050, the network entity estimates the 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 of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table. The network entity may also base the position estimate on the base station Tx-Rx parameters received from the TRP and any group delay. In one aspect, where the network entity is a location server, operation 1050 may be performed by the network interface 390, the processing system 394, the memory component 396 and / or the LUT manager 398, and or all of the components that may be considered to be used to perform this operation. Where the network entity is a TRP, operation 1050 may be performed by any one or all of the WWAN transceiver 350, the processing system 384, the memory 386 and / or the LUT manager 388, and components that may be considered to be used to perform this operation.
[0148] Those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0149] In addition, it will be appreciated by those skilled in the art that the various illustrative logic blocks, modules, circuits and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits and steps have been generally described above according to their functions. Whether this function is implemented as hardware or software depends on specific applications and the design constraints imposed on the entire system. The technician can implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing deviations from the scope of the present disclosure.
[0150] The various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed with 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 in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.
[0151] The methods, sequences and / or algorithms described in conjunction with the aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integrated with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.
[0152] 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 sent on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media and communication media, which include any media that facilitate the transmission of a computer program from one place to another. Storage media may be any available media that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage devices, disk storage devices, or other magnetic storage devices, or may be used to carry or store required program codes and any other media that can be accessed by a computer in the form of instructions or data structures. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if 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 microwaves, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0153] Although the foregoing disclosure shows illustrative 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 disclosed aspects described herein do not need to be performed in any particular order. In addition, although elements of the present disclosure may be described or claimed in the singular, plural forms are contemplated unless limitation to the singular is explicitly stated.
Claims
1. A user equipment UE, include: Memory; at least one transceiver; as well as at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receiving 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; causing 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; determining a parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; causing the at least one transceiver to send the parameter to a network entity; as well as The at least one transceiver is caused to send a first lookup table or an identifier of the first lookup table to the network entity, wherein the first lookup table represents frequency group delay information of the downlink receive beam and / or the uplink transmit beam.
2. The UE according to claim 1, in, The at least one processor is further configured to: The at least one transceiver is caused to send an identifier associated with the downlink receive beam to the network entity.
3. The UE according to claim 2, in, The identifier associated with the downlink receive beam is an identifier of the first downlink reference signal.
4. The UE according to claim 2, in, The identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource.
5. The UE according to claim 1, in, The at least one processor is further configured to: Causes the at least one transceiver to send a second lookup table or an identifier of the second lookup table to the network entity, wherein the second lookup table represents frequency group delay information of the uplink transmit beam, and wherein the first lookup table represents the frequency group delay information of the downlink receive beam.
6. The UE according to claim 5, in, The at least one processor is further configured to: causing the at least one transceiver to send an identifier associated with the downlink receive beam to the network entity; and / or The at least one transceiver is caused to transmit an identifier associated with the uplink transmit beam to the network entity.
7. The UE according to claim 6, in: The identifier associated with the downlink receive beam is an identifier of the first downlink reference signal, and / or The identifier associated with the uplink transmit beam is an identifier of the uplink reference signal.
8. The UE according to claim 6, in: The identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource, and / or The identifier associated with the uplink transmit beam is an identifier of the at least one uplink reference signal resource.
9. The UE according to claim 8, in: 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, and 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.
10. The UE according to claim 8, in, The at least one processor being configured to cause the at least one transceiver to transmit the second lookup table includes the at least one processor being configured to cause the at least one transceiver to transmit only a difference between the first lookup table and the second lookup table.
11. The UE according to claim 6, in: the identifier associated with the downlink receive beam is an identifier of the downlink receive beam, and The identifier associated with the uplink transmit beam is an identifier of the uplink transmit beam.
12. The UE according to claim 6, in, The at least one processor is further configured to: A second downlink reference signal is received from the TRP or a second TRP via the at least one transceiver on the downlink receive beam, and the downlink receive beam is associated with the reception of the first downlink reference signal.
13. The UE according to claim 12, in: The second downlink reference signal is a quasi co-located source reference signal of the first downlink reference signal, and The identifier associated with the downlink receive beam is an identifier of the second downlink reference signal.
14. The UE according to claim 12, in: The second downlink reference signal is a spatial relation reference downlink reference signal of the uplink reference signal, and The identifier associated with the uplink transmit beam is an identifier of the second downlink reference signal.
15. The UE according to claim 12, in, 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 PRS.
16. The UE according to claim 5, in, 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 the transmission of the second lookup table or the identifier of the second lookup table to indicate that the first lookup table represents the frequency group delay information of the downlink receive beam, and the second lookup table represents the frequency group delay information of the uplink transmit beam.
17. The UE according to claim 5, in, 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 the transmission of the first lookup table or the identifier of the first lookup table to indicate that the first lookup table represents the frequency group delay information of the downlink receive beam, and the second lookup table represents the frequency group delay information of the uplink transmit beam.
18. The UE according to claim 9, in, If the first lookup table has been previously transmitted to a network entity, the first lookup table is no longer transmitted to the network entity unless the UE updates an association between the first lookup table and the PRS resources or the SRS resources.
19. The UE according to claim 1, in, The at least one processor is further configured to: Causes the at least one transceiver to send the first lookup table to the network entity before receiving the first downlink reference signal from the TRP.
20. The UE according to claim 19, in, The per-frequency group delay information represented by the first lookup table includes a range of average group delays, a range of group delay spreads, or both, for the downlink receive beam and / or the uplink transmit beam.
21. The UE according to claim 19, in, The at least one processor causes the at least one transceiver to send the identifier of the first lookup table to the network entity after receiving the first downlink reference signal from the TRP.
22. The UE according to claim 21, in, The first lookup table is not changed between transmission of the first lookup table and transmission of the identifier of the first lookup table.
23. The UE according to claim 1, in, The at least one processor is further configured to: A trigger is received from the network entity via the at least one transceiver to send the first lookup table.
24. The UE according to claim 1, in, The first lookup table represents a plurality of frequency regions of a carrier frequency on which the first downlink reference signal is transmitted, wherein each frequency region is associated with a group delay when the downlink receive beam is formed at a frequency within the frequency region.
25. The UE according to claim 1, in, The network entity is the TRP or location server.
26. The UE according to claim 1, in, The first lookup table is sent to the network entity in capability information for the UE.
27. A network entity, include: Memory; At least one network interface; as well as at least one processor communicatively coupled to the memory and the network interface, the at least one processor configured to: causing the at least one network interface to send an identifier of at least one downlink reference signal resource to a user equipment UE so that the UE can receive a first downlink reference signal from a transmission reception point TRP on the at least one downlink reference signal resource using a downlink reception beam; causing the at least one network interface to send an identifier of at least one uplink reference signal resource to the UE so that the UE can send an uplink reference signal to the TRP on the at least one uplink reference signal resource using an uplink transmit beam; receiving, via the at least one network interface, a parameter from the UE, the parameter representing a difference between a reception time of the first downlink reference signal at the UE 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 frequency group delay information of the downlink receive beam and / or the uplink transmit beam; as well as The position of the UE is estimated based in part on a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal and a group delay of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
28. The network entity according to claim 27, in, The at least one processor is further configured to: An identifier associated with the downlink receive beam is received from the UE via the at least one network interface.
29. The network entity according to claim 28, in, The identifier associated with the downlink receive beam is an identifier of the first downlink reference signal.
30. The network entity according to claim 28, in, The identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource.
31. The network entity according to claim 27, in, The at least one processor is further configured to: A second lookup table or an identifier of the second lookup table is received from the UE via the at least one network interface, wherein the second lookup table represents frequency group delay information of the uplink transmit beam, and wherein the first lookup table represents the frequency group delay information of the downlink receive beam.
32. The network entity according to claim 31, in, The at least one processor is further configured to: receiving, from the UE via the at least one network interface, an identifier associated with the downlink receive beam; as well as An identifier associated with the uplink transmit beam is received from the UE via the at least one network interface.
33. The network entity according to claim 32, in: the identifier associated with the downlink receive beam is an identifier of the first downlink reference signal, and The identifier associated with the uplink transmit beam is an identifier of the uplink reference signal.
34. The network entity according to claim 32, in: The identifier associated with the downlink receive beam is an identifier of the at least one downlink reference signal resource, and The identifier associated with the uplink transmit beam is an identifier of the at least one uplink reference signal resource.
35. The network entity according to claim 34, in: 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, and 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.
36. The network entity according to claim 32, in: the identifier associated with the downlink receive beam is an identifier of the downlink receive beam, and The identifier associated with the uplink transmit beam is an identifier of the uplink transmit beam.
37. The network entity according to claim 32, in, The at least one processor is further configured to: The at least one network interface sends an identifier of a second at least one downlink reference signal resource to the UE so that the UE can use the downlink receive beam to receive a second downlink reference signal on the second at least one downlink reference signal resource before receiving the first downlink reference signal.
38. The network entity according to claim 37, in: The second downlink reference signal is a quasi co-located source reference signal of the first downlink reference signal, and The identifier associated with the downlink receive beam is an identifier of the second downlink reference signal.
39. The network entity according to claim 37, in: The second downlink reference signal is a spatial relation reference downlink reference signal of the uplink reference signal, and The identifier associated with the uplink transmit beam is an identifier of the second downlink reference signal.
40. The network entity according to claim 37, in, 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 PRS.
41. The network entity according to claim 37, in, The at least one downlink reference signal resource is the same as the second at least one downlink reference signal resource.
42. The network entity according to claim 31, in, The first lookup table or the identifier of the first lookup table is received before or simultaneously with the reception of the second lookup table or the identifier of the second lookup table, indicating that the first lookup table represents the frequency group delay information of the downlink receive beam and the second lookup table represents the frequency group delay information of the uplink transmit beam.
43. The network entity according to claim 31, in, The second lookup table or the identifier of the second lookup table is received before or simultaneously with the reception of the first lookup table or the identifier of the first lookup table, indicating that the first lookup table represents the frequency group delay information of the downlink receive beam and the second lookup table represents the frequency group delay information of the uplink transmit beam.
44. The network entity according to claim 31, in, The second lookup table includes only the difference between the first lookup table and the second lookup table.
45. The network entity according to claim 35, in, If the first lookup table has been previously transmitted to a network entity, the first lookup table is no longer transmitted to the network entity unless an association between the first lookup table and the PRS resources or the SRS resources is updated.
46. The network entity according to claim 27, in, The first lookup table is received before sending the identification of the at least one downlink reference signal resource to the UE.
47. The network entity according to claim 46, in, The per-frequency group delay information represented by the first lookup table includes a range of average group delays, a range of group delay spreads, or both, for the downlink receive beam and / or the uplink transmit beam.
48. The network entity according to claim 46, in, The identifier of the first look-up table is received after transmitting the identification of the at least one downlink reference signal resource to the UE.
49. The network entity according to claim 48, in, The first lookup table is not changed between receipt of the first lookup table and receipt of the identifier of the first lookup table.
50. The network entity according to claim 27, in, The at least one processor is further configured to: The at least one network interface is caused to send a trigger to the UE to send the first lookup table.
51. The network entity according to claim 27, in, The first lookup table represents a plurality of frequency regions of a carrier frequency on which the first downlink reference signal is transmitted, wherein each frequency region is associated with a group delay when the downlink receive beam is formed at a frequency within the frequency region.
52. The network entity according to claim 27, in, The network entity is the TRP or location server.
53. The network entity according to claim 27, in, The first lookup table is sent to the network entity in capability information for the UE.
54. A method of wireless communication performed by a user equipment UE, include: receiving a first downlink reference signal from a transmission reception point 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 representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; sending the parameters to a network entity; as well as A first lookup table or an identifier of the first lookup table is sent to the network entity, wherein the first lookup table represents frequency-based group delay information of the downlink receive beam and / or the uplink transmit beam.
55. The method according to claim 54, further comprising: include: An identifier associated with the downlink receive beam is sent to the network entity.
56. The method according to claim 54, further comprising: include: A second lookup table or an identifier of the second lookup table is sent to the network entity, wherein the second lookup table represents frequency group delay information of the uplink transmit beam, and wherein the first lookup table represents the frequency group delay information of the downlink receive beam.
57. The method according to claim 56, further comprising: include: sending an identifier associated with the downlink receive beam to the network entity; and / or An identifier associated with the uplink transmit beam is sent to the network entity.
58. The method according to claim 57, further comprising: include: A second downlink reference signal is received from the TRP or a second TRP on the downlink receive beam associated with the reception of the first downlink reference signal.
59. The method according to claim 56, in, The UE sends the first lookup table or the identifier of the first lookup table before or simultaneously with the transmission of the second lookup table or the identifier of the second lookup table to indicate that the first lookup table represents the frequency group delay information of the downlink receive beam and the second lookup table represents the frequency group delay information of the uplink transmit beam.
60. The method according to claim 56, in, The UE sends the second lookup table or the identifier of the second lookup table before or simultaneously with the transmission of the first lookup table or the identifier of the first lookup table to indicate that the first lookup table represents the frequency group delay information of the downlink receive beam and the second lookup table represents the frequency group delay information of the uplink transmit beam.
61. The method according to claim 54, in, The first downlink reference signal is a positioning reference signal PRS, The uplink reference signal is a sounding reference signal SRS, and If the first lookup table has been previously transmitted to a network entity, the first lookup table is no longer transmitted to the network entity unless the UE updates an association between the first lookup table and the resources of the PRS or the resources of the SRS.
62. The method of claim 54, further comprising: include: Prior to receiving the first downlink reference signal from the TRP, the first lookup table is sent to the network entity.
63. The method according to claim 54, in, The first lookup table represents a plurality of frequency bins on a carrier frequency on which the first downlink reference signal is transmitted, wherein each frequency bin is associated with a group delay when the downlink receive beam is formed at a frequency within the frequency bin.
64. The method according to claim 54, in, The network entity is the TRP or location server.
65. The method according to claim 54, in, The first lookup table is sent to the network entity in capability information for the UE.
66. A method of wireless communication performed by a network entity, include: Sending an identifier of at least one downlink reference signal resource to a user equipment UE so that the UE can receive a first downlink reference signal from a transmission reception point TRP on the at least one downlink reference signal resource using a downlink reception beam; sending an identifier of at least one uplink reference signal resource to the UE so that the UE can send an uplink reference signal to the TRP on the at least one uplink reference signal resource using an uplink transmit beam; receiving a parameter from the UE, the parameter representing a difference between a reception time of the first downlink reference signal at the UE 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, wherein the first lookup table represents frequency-based group delay information for the downlink receive beam and / or the uplink transmit beam; as well as The position of the UE is estimated based in part on a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal and a group delay of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
67. The method according to claim 66, further comprising: include: An identifier associated with the downlink receive beam is received from the UE.
68. The method according to claim 66, further comprising: include: A second lookup table or an identifier of the second lookup table is received from the UE, wherein the second lookup table represents frequency group delay information of the uplink transmit beam, and wherein the first lookup table represents the frequency group delay information of the downlink receive beam.
69. The method according to claim 68, further comprising: include: receiving, from the UE, an identifier associated with the downlink receive beam; as well as An identifier associated with the uplink transmit beam is received from the UE.
70. The method of claim 69, further comprising: include: An identifier of a second at least one downlink reference signal resource is sent to the UE so that the UE can receive a second downlink reference signal on the second at least one downlink reference signal resource using the downlink receive beam before receiving the first downlink reference signal.
71. The method according to claim 70, in: The second downlink reference signal is a quasi co-located source reference signal of the first downlink reference signal, and The identifier associated with the downlink receive beam is an identifier of the second downlink reference signal.
72. The method according to claim 70, in: The second downlink reference signal is a spatial relation reference downlink reference signal of the uplink reference signal, and The identifier associated with the uplink transmit beam is an identifier of the second downlink reference signal.
73. The method according to claim 68, in, The second lookup table includes only the difference between the first lookup table and the second lookup table.
74. The method according to claim 66, in, The first lookup table is received before sending the identification of the at least one downlink reference signal resource to the UE.
75. The method according to claim 66, in, The network entity is the TRP or location server.
76. A user equipment UE, include: means for receiving a first downlink reference signal from a transmission reception point TRP on at least one downlink reference signal resource using a downlink reception 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 reception time of the first downlink reference signal and a transmission time of the uplink reference signal; means for sending said parameters to a positioning entity; as well as Means for sending 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 of the downlink receive beam and / or the uplink transmit beam.
77. A network entity, include: means for sending an identification of at least one downlink reference signal resource to a user equipment UE so that the UE can receive a first downlink reference signal from a transmission reception point TRP on the at least one downlink reference signal resource using a downlink reception beam; for sending an identifier of at least one uplink reference signal resource to a UE so that the UE can send an uplink reference signal component to the TRP on the at least one uplink reference signal resource using an uplink transmit beam; means for receiving a parameter from the UE, the parameter representing a difference between a reception time of the first downlink reference signal at the UE and a transmission time of the uplink reference signal from the UE; 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 component for estimating the position of the UE based in part on a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal and a group delay of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
78. A non-transitory computer readable medium storing computer executable instructions which, when executed by a computer, cause a method comprising: Instructing a user equipment UE to receive a first downlink reference signal from a transmission reception point TRP on at least one downlink reference signal resource using a downlink reception beam; Instructing the UE to send an uplink reference signal to the TRP on at least one uplink reference signal resource using an uplink transmit beam; instructing the UE to determine a parameter, the parameter representing a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal; Instructing the UE to send the parameter to a positioning entity; as well as The UE is guided to send a first lookup table or an identifier of the first lookup table to the positioning entity, wherein the first lookup table represents frequency group delay information of the downlink receive beam and / or the uplink transmit beam.
79. A non-transitory computer readable medium storing computer executable instructions which, when executed by a computer, cause a method comprising: Instructing a network entity to send an identifier of at least one downlink reference signal resource to a user equipment UE so that the UE can receive a first downlink reference signal from a transmission reception point TRP on the at least one downlink reference signal resource using a downlink reception beam; Instructing the network entity to send an identifier of at least one uplink reference signal resource to the UE so that the UE can send an uplink reference signal to the TRP on the at least one uplink reference signal resource using an uplink transmit beam; directing the network entity to receive a parameter from the UE, the parameter representing a difference between a reception time of the first downlink reference signal at the UE and a transmission time of the uplink reference signal from the UE; Instructing the network entity to receive a first lookup table or an identifier of the first lookup table from the UE, wherein the first lookup table represents frequency group delay information of the downlink receive beam and / or the uplink transmit beam; as well as The network entity is directed to estimate the position of the UE based in part on a difference between a reception time of the first downlink reference signal and a transmission time of the uplink reference signal and a group delay of the downlink receive beam and / or the uplink transmit beam retrieved from the first lookup table.
