Position estimation based on time bias between base station and reference user equipment

Abstract

Disclosed are techniques for wireless communication. In an aspect, a position estimation entity, obtains first timing information that is associated with a first time-of-arrival (TOA) measurement of a first reference signal for positioning (RS-P) as communicated between a target user equipment (UE) and a base station with a first time basis, obtains second timing information that is associated with a second TOA measurement of a second RS-P as communicated between the target UE and a reference UE associated with a known location and having a second time basis that is different than the first time basis, determines a bias between the first time basis and the second time basis, and determines a position estimate of the target UE via a time differential of arrival (TDOA) positioning technique based at least in part upon the first timing information, the second timing information, and the bias.

Description

[Technical Field]

[0001] The various aspects of this case are generally related to wireless communication. [Previous Technology]

[0002] Wireless communication systems have evolved through several generations, including first-generation analog wireless telephony (1G), second-generation (2G) digital wireless telephony (including 2.5G and 2.75G networks for the transition), third-generation (3G) high-speed data, wireless services supporting the Internet, and fourth-generation (4G) services (such as Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include the Cellular Analog Advanced Mobile Telephone System (AMPS) and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and Global System for Mobile Communications (GSM).

[0003] The fifth-generation (5G) wireless standard, also known as New Radio (NR), demands higher data transmission speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard aims to provide tens of megabits per second (Mbps) of data rate for each of tens of thousands of users, and gigabits per second (Gbps) of data rate for dozens of employees on an office floor. To support large-scale sensor deployments, it should support hundreds of thousands of simultaneous connections. Therefore, the spectral efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G standard. Furthermore, signal transmission efficiency should be improved and latency significantly reduced compared to the current standard. [Summary of the Invention]

[0004] The following is a simplified overview related to one or more states disclosed herein. This overview should not be considered a broad overview related to all anticipated states, nor should it be considered an identification of key or important elements related to all anticipated states or a description of categories related to any particular state. Therefore, the sole purpose of the following overview is to provide, in a simplified form, certain concepts related to one or more states of the mechanism disclosed herein before the specific implementations provided below.

[0005] In one embodiment, a method for operating a location estimation entity includes the following steps: acquiring first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquiring second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE associated with a known location and having a second time base different from the first time base; determining a deviation between the first time base and the second time base; and determining a location estimation of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

[0006] In some embodiments, the method includes the following steps: acquiring third timing information associated with a third TOA measurement of a third RS-P communicating between a target UE and a first radio node; and acquiring fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between a target UE and a second radio node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

[0007] In some cases, the first wireless node and the second wireless node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0008] In some cases, the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to the downlink positioning reference signal (DL-PRS), and the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0009] In some cases, the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to the uplink detection reference (UL-SRS-P) used for positioning, and wherein the second RS-P corresponds to the UL-SRS-P or the sidelink PRS (SL-PRS).

[0010] In some cases, the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0011] In some cases, the bias decision is triggered by combining the positioning estimation decision.

[0012] In some states, the bias decision is triggered independently of the triggering location estimation decision and within the threshold time period of the triggering location estimation decision.

[0013] In some cases, the bias is determined based on the first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0014] In some cases, the bias is also determined based on a second difference between the estimated propagation time between another base station and the reference UE based on their respective known locations and the measured propagation time between the other base station and the reference UE.

[0015] In one embodiment, the location estimation entity includes: a memory; at least one transceiver; and at least one processor, communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to: acquire first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquire second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE associated with a known location and having a second time base different from the first time base; determine a deviation between the first time base and the second time base; and determine a location estimate of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

[0016] In some embodiments, at least one processor is also configured to: acquire third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and the first wireless node; and acquire fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and the second wireless node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

[0017] In some cases, the first wireless node and the second wireless node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0018] In some cases, the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to the downlink positioning reference signal (DL-PRS), and the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0019] In some cases, the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to the uplink detection reference (UL-SRS-P) used for positioning, and wherein the second RS-P corresponds to UL-SRS-P or sidelink PRS (SL-PRS).

[0020] In some cases, the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0021] In some cases, the bias decision is triggered by combining the positioning estimation decision.

[0022] In some states, the bias decision is triggered independently of the triggering location estimation decision and within the threshold time period of the triggering location estimation decision.

[0023] In some cases, the bias is determined based on a first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0024] In some cases, the bias is also determined based on a second difference between the estimated propagation time between another base station and the reference UE based on the corresponding known location and the measured propagation time between the other base station and the reference UE.

[0025] In one embodiment, a location estimation entity includes: means for acquiring first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; means for acquiring second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE associated with a known location and having a second time base different from the first time base; means for determining a deviation between the first time base and the second time base; and means for determining a location estimate of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

[0026] In some embodiments, the method includes the following steps: a component for acquiring third timing information associated with a third TOA measurement of a third RS-P communicating between a target UE and a first wireless node; and a component for acquiring fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between a target UE and a second wireless node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

[0027] In some cases, the first wireless node and the second wireless node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0028] In some cases, the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to the downlink positioning reference signal (DL-PRS), and the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0029] In some cases, the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to the uplink detection reference (UL-SRS-P) used for positioning, and wherein the second RS-P corresponds to UL-SRS-P or sidelink PRS (SL-PRS).

[0030] In some cases, the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0031] In some cases, the bias decision is triggered by combining the positioning estimation decision.

[0032] In some states, the bias decision is triggered independently of the triggering location estimation decision and within the threshold time period of the triggering location estimation decision.

[0033] In some cases, the bias is determined based on a first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0034] In some cases, the bias is also determined based on a second difference between the estimated propagation time between another base station and the reference UE based on their respective known locations and the measured propagation time between the other base station and the reference UE.

[0035] In one embodiment, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location estimation entity, cause the location estimation entity to: acquire first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquire second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE associated with a known location and having a second time base different from the first time base; determine a deviation between the first and second time bases; and determine a location estimate of the target UE via time difference of arrival (TDOA) positioning technology, at least in part based on the first timing information, the second timing information, and the deviation.

[0036] In some cases, the one or more instructions also cause the location estimation entity to: acquire third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and the first radio node; and acquire fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and the second radio node, wherein the location estimation decision is also based on the third timing information and the fourth timing information.

[0037] In some cases, the first wireless node and the second wireless node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0038] In some cases, the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to the downlink positioning reference signal (DL-PRS), and the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0039] In some cases, the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to the uplink detection reference (UL-SRS-P) used for positioning, and wherein the second RS-P corresponds to UL-SRS-P or sidelink PRS (SL-PRS).

[0040] In some cases, the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0041] In some cases, the bias decision is triggered by combining the positioning estimation decision.

[0042] In some states, the bias decision is triggered independently of the triggering location estimation decision and within the threshold time period of the triggering location estimation decision.

[0043] In some cases, the bias is determined based on the first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0044] In some cases, the bias is also determined based on a second difference between the estimated propagation time between another base station and the reference UE based on their respective known locations and the measured propagation time between the other base station and the reference UE.

[0045] Other objects and advantages associated with the embodiments disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed descriptions.

Implementation Method

[0057] Various forms of this invention are provided in the following description and related drawings, which are for illustrative purposes and represent various examples. Alternative forms may be designed without departing from the scope of this invention. Furthermore, well-known elements of this invention will not be described in detail or will be omitted so as not to obscure the relevant details of this invention.

[0058] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance or illustration.” Any manner described herein as “exemplary” and / or “example” is not necessarily to be construed as being superior to other manners. Similarly, the term “manner of this case” does not require that all manner of this case include the features, advantages or modes of operation discussed.

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

[0060] Furthermore, many states are described according to sequences of actions to be performed by, for example, elements of a computing device. It should be understood that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), program instructions executed by one or more processors, or a combination of both. Furthermore, the sequences of actions described herein can be considered entirely contained in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions, which, upon execution, cause or instruct the relevant processor of the device to perform the functionality described herein. Therefore, the various states of this application can be embodied in many different forms, all of which are considered to be within the scope of the claimed object. Furthermore, for each state described herein, any corresponding form of such state can be described herein as, for example, "logic configured to" perform the described actions.

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

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

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

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

[0065] An "RF signal" includes electromagnetic waves of a given frequency that transmit information through space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the multipath propagation characteristics of RF signals, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal," or simply as "signal" when the context clearly indicates that the term "signal" refers to a wireless signal or an RF signal.

[0066] Figure 1 illustrates an exemplary wireless communication system 100 according to various embodiments of the present invention. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one embodiment, macrocell base stations may include eNBs and / or ng-eNBs when the wireless communication system 100 corresponds to an LTE network, or gNBs when the wireless communication system 100 corresponds to an NR network, or a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

[0067] Base station 102 may collectively form a RAN and is connected to core network 170 (e.g., Evolved Packet Core (EPC) or 5G Core (5GC)) via backhaul link 122, and to one or more location servers 172 (e.g., Location Management Function (LMF) or Secure User Plane Location (SUPL) Location Platform (SLP)) via core network 170. The location servers 172 may be part of core network 170 or may be outside core network 170. Among other functions, base station 102 may perform functions associated with one or more of the following: 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, distribution of Non-Access Layer (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), user and device tracking, RAN Information Management (RIM), paging, location, and warning message delivery. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC / 5GC) via backhaul link 134, which can be wired or wireless.

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

[0069] Although the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in delivery areas), some geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' (small cells are labeled "SC") may have geographic coverage areas 110' that substantially overlap with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both 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 called a Closed Subscriber Group (CSG).

[0070] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be transmitted via one or more carrier frequencies. Carrier allocation may be asymmetrical relative to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0071] The wireless communication system 100 may also include a wireless local area network (WLAN) access point (AP) 150, which communicates with a WLAN station (STA) 152 in unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform an idle channel assessment (CCA) or listen-before-talk (LBT) procedure before communication to determine whether the channel is available.

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

[0073] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). The EHF band ranges from 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band can be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. The ultra-high frequency (SHF) band extends between 3 GHz and 30 GHz and is also known as centimeter waves. Communication using mmW / near-mmW RF bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can compensate for the extremely high path loss and short range via the mmW communication link 184 using beamforming (transmission and / or reception). Furthermore, it will be understood that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing description is merely an example and should not be interpreted as limiting the various states disclosed herein.

[0074] Transmission beamforming is a technique for focusing RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectional). In the case of transmission beamforming, the network node determines the location of a given target device (e.g., a UE) (relative to the transmission 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 (multiple) receiving devices. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal on each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (called a "phased array" or "antenna array") that generates RF beams that can be "guided" to be pointed in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to the individual antennas with the correct phase relationship, such that radio waves from the separate antennas are added together to increase radiation in the desired direction while canceling out radiation in the undesired direction.

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

[0076] In receive beamforming, the receiver uses a receive beam to amplify the RF signal 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 specific direction to amplify (e.g., increase the gain level) the RF signal received from that direction. Therefore, when the receiver is considered to be beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a higher received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-noise ratio (SINR), etc.) of the RF signal received from that direction.

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

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

[0079] In 5G, the spectrum on which wireless nodes (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). The mmW band typically includes the FR2, FR3, and FR4 frequency ranges. Therefore, the terms "mmW" and "FR2" or "FR3" or "FR4" are often used interchangeably.

[0080] In multi-carrier systems, such as 5G, one carrier frequency is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," while the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182 and the cell, in which UE 104 / 182 performs the initial Radio Resource Control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all shared and UE-specific control channels and can be a carrier in a licensed frequency (but not always). The secondary carrier is the carrier operating on a second frequency (e.g., FR2), which can be configured once an RRC connection is established between UE 104 and the anchor carrier, and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only the necessary signal transmission information and signals. For example, UE-specific information and signals may not exist in the secondary carrier, since both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time, for example, to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier that a base station is communicating on, the terms "cell," "serving cell," "component carrier," and "carrier frequency" are used interchangeably.

[0081] For example, still referring to Figure 1, one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), while other frequencies used by macrocell base station 102 and / or mmW base station 180 may be subcarriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers enables UE 104 / 182 to significantly improve its data transmission and / or reception rates. For example, compared to a single 20 MHz carrier, two aggregated 20 MHz carriers in a multicarrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz).

[0082] The wireless communication system 100 may also include a UE 164, which can communicate with the macrocell base station 102 via the communication link 120 and / or with the mmW base station 180 via the mmW communication link 184. For example, the macrocell base station 102 can support one PCell and one or more SCells for the UE 164, while the mmW base station 180 can support one or more SCells for the UE 164.

[0083] In the example of Figure 1, any illustrated UE (shown as a single UE 104 in Figure 1 for simplicity) can receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one instance, SV 112 may be part of a satellite positioning system, which UE 104 may use as a separate source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitter. Such a transmitter typically transmits signals marked with a set number of repeating pseudo-random noise (PN) codes. Although typically located in SV 112, the transmitter may sometimes be located at a ground-based control station, base station 102, and / or other UE 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 for exporting geolocation information from SV 112.

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

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

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

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

[0088] Another alternative configuration may include a location server 230, which can communicate with the 5GC 210 to provide location assistance to (multiple) UEs 204. The location server 230 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, which may connect to the location server 230 via the core network 5GC 210 and / or via the Internet (not shown). Furthermore, the location server 230 may be integrated into a component of the core network, or it may be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0089] Figure 2B illustrates another exemplary wireless network structure 250. 5GC 260 (which may correspond to 5GC 210 in Figure 2A) can be functionally considered as control plane functions provided by Access and Mobility Management Function (AMF) 264 and user plane functions provided by User Plane Function (UPF) 262, which cooperate to form the core network (i.e., 5GC 260). The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transmission of Period Management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and Period Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of SMS service messages between UE 204 and SMS Service Function (SMSF) (not shown), and Security Anchor Functionality (SEAF). The AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204, receiving an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the Universal Mobile Telecommunications System (UMTS) Subscriber Identity Module (USIM), the AMF 264 obtains security material from the AAUSF. The AMF 264's functionality also includes Security Context Management (SCM). The SCM receives a key from the SEAF for exporting the specific key for network access. The AMF 264's functionality also includes location service management for regulatory services, transmission of location service messages between UE 204 and the Location Management Function (LMF) 270 (acting as the location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, EPS bearer identifier allocation for interoperability with the Evolved Packet System (EPS), and UE 204 mobility event notification. Furthermore, the AMF 264 also supports functionality for non-3GPP (3rd Generation Partnership Project) access networks.

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

[0091] The functions of SMF 266 include communication period management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic bootstrapping at UPF 262 to route traffic to the correct destination, control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0092] Another alternative configuration may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204, which may connect to the LMF 270 via the core network 5GC 260 and / or via the Internet (not shown). SLP 272 can support similar functions to LMF 270, but LMF 270 can communicate with AMF 264, NG-RAN 220 and UE 204 via the control plane (e.g., using interfaces and protocols intended to transmit signals instead of voice or data), while SLP 272 can communicate with UE 204 and external clients (not shown in Figure 2B) via the user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0093] The user plane interface 263 and the control plane interface 265 connect the 5GC 260 to (specifically, connect the UPF 262 and AMF 264 to) one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNBs 222 and / or the ng-eNBs 224 and the AMF 264 is referred to as the "N2" interface, while the interface between the gNBs 222 and / or the ng-eNBs 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or the ng-eNBs 224 in the NG-RAN 220 can communicate directly with each other via the backload connection 223 (referred to as the "Xn-C" interface). One or more gNB 222 and / or ng-eNB 224 can communicate with one or more UE 204 via a wireless interface called "Uu".

[0094] The functionality of gNB 222 is divided between gNB Central Unit (gNB-CU) 226 and one or more gNB Distributed Units (gNB-DU) 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. gNB-CU 226 is a logical node that includes base station functions such as transmitting user data, mobility control, radio access network sharing, location, and communication period management, in addition to the functions specifically assigned to gNB-DU(228) 228. More specifically, gNB-CU 226 hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of gNB 222. gNB-DU 228 is a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer (PHY) of gNB 222. The operation of gNB-DU 228 is controlled by gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. Therefore, UE 204 communicates with gNB-CU 226 via RRC, SDAP, and PDCP layers, and with gNB-DU 228 via RLC, MAC, and PHY layers.

[0095] Figures 3A, 3B, and 3C illustrate several exemplary elements (represented by corresponding blocks) that can be included in UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure described in Figures 2A and 2B, such as a private network) to support file transfer operations as taught herein. It should be understood that such elements can be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.). The illustrated elements can also be included in other devices in the communication system. For example, other devices in the system may include elements similar to those described to provide similar functionality. Furthermore, a given device may include one or more elements. For example, an apparatus may include multiple transceiver elements that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

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

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

[0098] In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may each provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378. When satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. When satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 may be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may, as appropriate, request information and operations from other systems, and in at least some cases, perform calculations to determine the positions of UE 302 and base station 304, respectively, using measurements acquired via any suitable satellite positioning system algorithm.

[0099] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, providing components (e.g., components for transmission, components for reception, etc.) for communicating with other network entities (e.g., other base station 304, other network entity 306). For example, base station 304 may employ one or more network transceivers 380 to communicate with other base station 304 or network entity 306 via one or more wired or wireless backhaul links. As another example, network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

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

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

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

[0103] UE 302, base station 304, and network entity 306 include memory circuitry systems that respectively implement memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Memories 340, 386, and 396 can therefore provide components for storage, components for retrieval, components for maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may respectively include location estimation modules 342, 388, and 398. Location estimation modules 342, 388, and 398 may be hardware circuitry that is part of processing systems 332, 384, and 394, or hardware circuitry coupled to processors 332, 384, and 394, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other configurations, location estimation modules 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, location estimation modules 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A illustrates possible locations for location estimation module 342, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone element. Figure 3B illustrates the possible locations of the location estimation module 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C illustrates the possible locations of the location estimation module 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a standalone component.

[0104] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide means for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite receivers 330. For example, the sensors 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, the sensors 344 may include a plurality of different types of devices and combine their outputs to provide motion information. For example, the sensors 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

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

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

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

[0108] At UE 302, receiver 312 receives signals via its respective antenna(s) 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 332. Transmitter 314 and receiver 312 implement Level 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial streams destined for UE 302. If multiple spatial streams are destined for UE 302, these multiple spatial streams can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes separate OFDM symbol streams for each subcarrier of the OFDM signal. By determining the most probable signal clustering point transmitted by base station 304, reference signals and symbols on each subcarrier are recovered and demodulated. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement Layer 3 (L3) and Layer 2 (L2) functionality.

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

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

[0111] Transmitter 314 can use the channel estimate derived from the reference signal or feedback transmitted from base station 304 by the channel estimator to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by transmitter 314 can be provided to (multiple) different antennas 316. Transmitter 314 can use the corresponding spatial stream to modulate an RF carrier for transmission.

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

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

[0114] For convenience, UE 302, base station 304, and / or network entity 306 are shown in Figures 3A, 3B, and 3C as including various elements that can be configured according to the various instances described herein. However, it should be understood that the elements shown may have different functionalities in different designs. In particular, the various elements in Figures 3A through 3C are optional in alternative configurations, and each configuration includes configurations that may vary due to design choices, cost, device usage, or other considerations. For example, in the case of Figure 3A, a particular implementation of UE 302 may omit (multiple) WWAN transceivers 310 (e.g., wearable devices, tablets, PCs, or laptops may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or (multiple) short-range transceivers 320 (e.g., cellular only), or (multiple) satellite receivers 330, or (multiple) sensors 344, etc. In another example, as shown in Figure 3B, a specific implementation of base station 304 may omit (multiple) WWAN transceivers 350 (e.g., a Wi-Fi "hotspot" access point without cellular capability), or (multiple) short-range wireless transceivers 360 (e.g., cellular only), or (satellite receiver 370), and so on. For the sake of simplicity, illustrations of various alternative configurations are not provided in this document, but will be readily understood by those familiar with the technology.

[0115] The various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one configuration, data buses 334, 382, ​​and 392 can form, or be part of, the communication interface for UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are contained in the same device (e.g., gNB and location server functionally merged into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between these logical entities.

[0116] The elements of Figures 3A, 3B, and 3C can be implemented in various ways. In some implementations, the elements of Figures 3A, 3B, and 3C can be implemented in one or more circuits, such as one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or include at least one memory element for storing information or executable code used by the circuit to provide that functionality. For example, some or all of the functions represented by blocks 310 to 346 can be implemented by the processor(s) and memory elements of UE 302 (e.g., via executing appropriate code and / or via appropriate configuration of the processor elements). Similarly, some or all of the functions represented by blocks 350 to 388 can be implemented by the processor(s) and memory elements of base station 304 (e.g., via executing appropriate code and / or via appropriate configuration of the processor elements). Furthermore, some or all of the functions represented by blocks 390 to 398 can be implemented by the processor(s) and memory elements of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor elements). For simplicity, this document describes various operations, actions, and / or functions as being performed by "UE", "base station", "network entity", etc. However, it is understood that such operations, actions, and / or functions can actually be performed by specific elements or combinations of elements of UE 302, base station 304, network entity 306, etc., such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memory 340, 386 and 396, positioning estimation modules 342, 388 and 398, etc.

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

[0118] Figure 4 is a block diagram illustrating the various elements of an exemplary UE 400 according to various states of this invention. In one state, UE 400 may correspond to any UE described herein. As a specific example, UE 400 may be a V-UE, such as V-UE 160 in Figure 1. For simplicity, the various features and functions illustrated in the block diagram of Figure 4 are connected together using a common data bus, which indicates that such various features and functions are operatively coupled together. Those skilled in the art will recognize that other connections, mechanisms, features, functions, etc., can be provided and modified as needed to operatively couple and configure the actual UE. Furthermore, it is also recognized that one or more features or functions illustrated in the example of Figure 4 may be further subdivided, or two or more features or functions illustrated in Figure 4 may be combined.

[0119] UE 400 may include at least one transceiver 404, which is connected to one or more antennas 402 and provides components (e.g., components for transmission, components for reception, components for measurement, components for tuning, components for suppressing transmission, etc.) for communicating with other network nodes via one or more communication links (e.g., communication link 120, side links 162, 166, 168, mmW communication link 184) via at least one designated RAT (e.g., cV2X or IEEE 802.11p). Other network nodes include V-UE (e.g., V-UE 160), infrastructure access points (e.g., roadside access point 164), P-UE (e.g., UE 104), base stations (e.g., base station 102), etc. The at least one transceiver 404 can be configured differently to transmit and encode signals (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals (e.g., messages, indications, information, boot signals, etc.). In one configuration, at least one transceiver 404 and (a plurality of) antennas 402 can form a (wireless) communication interface of UE 400.

[0120] As used herein, a "transceiver" may, in some implementations, include at least one transmitter and at least one receiver in an integrated device (e.g., embodied as transmitter and receiver circuitry in a single communication device), in some implementations include separate transmitter and separate receiver devices, or in other implementations may be embodied in other ways. In one instance, the transmitter may include or be coupled to a plurality of antennas (e.g., multiple antennas 402), such as an antenna array, which allows the UE 400 to perform transmission "beamforming," as described herein. Similarly, the receiver may include or be coupled to a plurality of antennas (e.g., multiple antennas 402), such as an antenna array, which allows the UE 400 to perform receive beamforming, as described herein. In one instance, the multiple transmitters and multiple receivers may share the same multiple antennas (e.g., multiple antennas 402), such that the UE 400 can only receive or transmit at a given time, and not simultaneously. In some cases, the transceiver may not provide both transmission and reception capabilities simultaneously. For example, in some designs, when full communication is not required, low-functionality receiver circuitry can be used to reduce costs (e.g., receiver chips or similar circuit systems that only provide low-level sniffing).

[0121] UE 400 may also include a Satellite Positioning Service (SPS) receiver 406. SPS receiver 406 may be connected to one or more antennas 402 and may provide components for receiving and / or measuring satellite signals. SPS receiver 406 may include any suitable hardware and / or software for receiving and processing SPS signals, such as Global Positioning System (GPS) signals. SPS receiver 406 may request information and operations from other systems as needed and perform calculations required to determine the positioning of UE 400 using measurements acquired by any suitable SPS algorithm.

[0122] One or more sensors 408 may be coupled to at least one processor 410 and may provide components for sensing or detecting information related to the state and / or environment of the UE 400, such as speed, heading (e.g., compass heading), headlight status, fuel mileage, etc. For example, one or more sensors 408 may include speedometers, tachometers, accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), etc.

[0123] At least one processor 410 may include one or more central processing units (CPUs), microprocessors, microcontrollers, ASICs, processing cores, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), etc., that provide processing functions as well as other computing and control functions. At least one processor 410 may therefore provide components for processing, such as components for decision-making, components for calculation, components for receiving, components for transmission, components for indication, etc. At least one processor 410 may include any form of logic adapted to perform or cause elements of UE 400 to perform at least the techniques described herein.

[0124] At least one processor 410 may also be coupled to memory 414, which provides components for storing data and software instructions (including components for retrieval, components for maintenance, etc.) for performing programming functions within UE 400. Memory 414 may be on at least one processor 410 (e.g., within the same integrated circuit (IC) package), and / or memory 414 may be external to at least one processor 410 and functionally coupled via a data bus.

[0125] UE 400 may include a user interface 450, which provides any suitable interface system that allows a user to interact with UE 400, such as a microphone / speaker 452, a keypad 454, and a display 456. The microphone / speaker 452 may provide voice communication services with UE 400. The keypad 454 may include any suitable buttons for the user to input to UE 400. The display 456 may include any suitable display, such as, for example, a backlit liquid crystal display (LCD), and may also include a touch screen display for adding user input modes. Therefore, the user interface 450 may be a component for providing instructions to the user (e.g., auditory and / or visual instructions) and / or for receiving user input (e.g., via user actuation of sensing devices such as a keypad, touch screen, microphone, etc.).

[0126] In one embodiment, UE 400 may include a side link manager 470 coupled to at least one processor 410. The side link manager 470 may be a hardware, software, or firmware element that, when executed, causes UE 400 to perform the operations described herein. For example, the side link manager 470 may be a software module stored in memory 414 and executable by at least one processor 410. As another example, the side link manager 470 may be hardware circuitry within UE 400 (e.g., an ASIC, a field-programmable gate array (FPGA), etc.).

[0127] Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 5A is Figure 500 illustrating an example of a downlink frame structure according to various embodiments of the present invention. Figure 5B is Figure 530 illustrating an example of a channel within a downlink frame structure according to various embodiments of the present invention. Figure 5C is Figure 550 illustrating an example of an uplink frame structure according to various embodiments of the present invention. Figure 5D is Figure 580 illustrating an example of a channel within an uplink frame structure according to various embodiments of the present invention. Other wireless communication technologies may have different frame structures and / or different channels.

[0128] LTE (and in some cases NR) uses OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR can also choose to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as tones or bins. Each subcarrier can be modulated with data. Typically, OFDM is used to transmit modulation symbols in the frequency domain, and SC-FDM is used to transmit modulation symbols in the time domain. 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 between subcarriers can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. System bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

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

[0130] In the examples of Figures 5A to 5D, a parameter set of 15 kHz was used. Therefore, in the time domain, a 10 ms frame is divided into 10 equal-sized sub-frames, each 1 ms long, and each sub-frame includes a time slot. In Figures 5A to 5D, time is represented horizontally (on the X-axis), increasing from left to right, while frequency is represented vertically (on the Y-axis), increasing (or decreasing) from bottom to top.

[0131] The resource grid can be used to represent time slots, each of which includes one or more concurrent time resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is also divided into multiple resource elements (REs). An RE can correspond to a symbol length in the time domain and a subcarrier in the frequency domain. In the parameter sets of Figures 5A to 5D, for a normal cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0132] Some REs carry downlink reference (bootstrapping) signals (DL-RS). DL-RS may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), etc. Figure 5A illustrates an exemplary location of an RE carrying a PRS (labeled "R").

[0133] A batch of resource elements (REs) used for transmitting PRS is called "PRS resources". This batch of resource elements can span multiple PRBs in the frequency domain and "N" (such as 1 or more) consecutive symbols in a time slot in the time domain. In a given OFDM symbol in the time domain, the PRS resources occupy consecutive PRS in the frequency domain.

[0134] The transmission of PRS resources within a given PRB has a specific comb size (also known as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for a comb size "N", the PRS is transmitted in every Nth subcarrier of a PRB symbol. For example, for comb-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS resource. Currently, DL-PRS supports comb sizes of comb-2, comb-4, comb-6, and comb-12. Figure 5A illustrates an exemplary PRS resource configuration of comb-6 (spanning six symbols). That is, the location of the shaded RE (labeled "R") indicates the comb-6 PRS resource configuration.

[0135] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within time slots with a fully frequency-domain interleaved pattern. DL-PRS resources can be configured in downlink or flexible (FL) symbols in any higher-level configuration of the time slot. For all REs of a given DL-PRS resource, each resource element (EPRE) may have a constant energy. Below are the frequency offsets between symbols with comb sizes of 2, 4, 6, and 12 over 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 6-symbol comb-2: {0, 1, 0, 1, 0, 1}; 12-symbol comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3}; 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

[0136] A "PRS resource set" is a collection of PRS resources used for transmitting PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by its PRS resource set ID and associated with a specific TRP (identified by its TRP ID). Additionally, PRS resources in a PRS resource set share the same periodicity, a common silence pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The periodicity is the time from the first repetition of the first PRS resource in the first PRS example to the same first repetition of the same first PRS resource in the next PRS example. The periodicity can have the length of 2^µ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} time slots, where µ = 0, 1, 2, 3. The repetition factor can have the length of a time slot selected from {1, 2, 4, 6, 8, 16, 32}.

[0137] The PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where the TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can be transmitted on a different beam; therefore, "PRS resource," or simply "resource," can also be referred to as a "beam." Note that this does not affect whether the UE knows the TRP and the beam transmitting the PRS.

[0138] "PRS example" or "PRS timing" is an example of a periodic repetitive time window (such as a group of one or more consecutive time slots) in which PRS is expected to be transmitted. PRS timing may also be referred to as "PRS positioning timing", "PRS positioning example", "positioning timing", "positioning example", "positioning repetition" or simply "timing", "example" or "repetition".

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

[0140] The concept of a frequency layer is somewhat similar to that of component carriers and bandwidth portions (BWP), but the difference is that component carriers and BWPs are used by one base station (or macrocell base station and smallcell base station) to transmit data channels, while a frequency layer is used by several (usually three or more) base stations to transmit PRS. When a UE sends its positioning capabilities to the network, such as during LTE Positioning Protocol (LPP) communication, the UE can indicate the number of frequency layers it can support. For example, the UE can indicate whether it can support one or four positioning frequency layers.

[0141] Figure 5B illustrates examples of various channels within a downlink time slot of a radio communication frame. In NR, channel bandwidth or system bandwidth is divided into multiple BWPs. A BWP is a set of consecutive PRBs selected from consecutive subsets of shared RBs with a given set of parameters on a given carrier. Typically, up to four BWPs can be specified for both downlink and uplink. That is, a UE can configure up to four BWPs on the downlink and up to four BWPs on the uplink. Only one BWP (uplink or downlink) is active at a given time, meaning that the UE can only receive or transmit via one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

[0142] Referring to Figure 5B, the Primary Synchronization Signal (PSS) is used by the UE to determine the subframe / symbol timing and entity layer identification. The UE uses the Secondary Synchronization Signal (SSS) to determine the entity layer cell identification group number and radio frame timing. Based on the entity layer identification and entity layer cell identification group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The Entity Broadcast Channel (PBCH) carrying the MIB can be logically classified with the PSS and SSS to form an SSB (also known as SS / PBCH). The MIB provides the System Frame Number (SFN) and several RBs in the downlink system bandwidth. The Entity Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) not transmitted via the PBCH, and paging messages.

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

[0144] In the example of Figure 5B, each BWP has a CORESET, and this CORESET spans three symbols in the time domain (although it may only have one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is confined to a specific region (i.e., the CORESET) in the frequency domain. Therefore, the frequency components of the PDCCH shown in Figure 5B are shown as smaller than a single BWP in the frequency domain. Note that although the illustrated CORESET is continuous in the frequency domain, it does not need to be continuous. Furthermore, the CORESET may span fewer than three symbols in the time domain.

[0145] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and a description of downlink data transmitted to the UE, referred to as uplink and downlink permissions, respectively. More specifically, the DCI indicates resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., PUSCH). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmission power control (TPC), etc. The PDCCH can be transmitted via 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or decoding rates.

[0146] As shown in Figure 5C, some REs (labeled "R") carry DMRS for channel estimation at the receiver (e.g., base station, another UE, etc.). The UE can also transmit SRS, for example, in the last symbol of a time slot. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. In the example of Figure 5C, the SRS shown is comb-2 on one symbol. The base station can use this SRS to obtain Channel State Information (CSI) for each UE. CSI describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, fading, and power attenuation with distance. The system uses SRS for resource scheduling, link self-adjustment, massive MIMO, beam management, etc.

[0147] Currently, SRS resources can span 1, 2, 4, 8, or 12 consecutive symbols within a time slot, with comb sizes of comb-2, comb-4, or comb-8. The following are the frequency offsets between symbols for the currently supported SRS comb patterns. 1-symbol comb-2: {0}; 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3}; 8-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3}; 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 4-symbol comb-8: {0, 4, 2, 6}; 8-symbol comb-8: {0, 4, 2, 6, 1, 5, 3, 7}; and 12-symbol comb-8: {0, 4, 2, 6, 1, 5, 3, 7, 0, 4, 2, 6}.

[0148] A batch of resource elements used for transmitting SRS is called an "SRS resource" and can be identified by the parameter "SRS-ResourceId". This batch of resource elements can span multiple PRBs in the frequency domain and N (e.g., one or more) consecutive symbols in a time slot in the time domain. In a given OFDM symbol, SRS resources occupy consecutive PRBs. An "SRS resource set" is a collection of SRS resources used for transmitting SRS signals and is identified by the SRS resource set ID ("SRS-ResourceSetId").

[0149] Typically, the UE transmits an SRS so that the receiving base station (serving base station or neighboring base station) can measure the channel quality between the UE and the base station. However, the SRS can also be specifically configured as an uplink positioning reference signal for uplink-based positioning procedures, such as uplink time difference of arrival (UL-TDOA), round-trip time (RTT), uplink angle of arrival (UL-AoA), etc. As used herein, the term "SRS" can refer to an SRS configured for channel quality measurement or an SRS configured for positioning purposes. When it is necessary to distinguish between the two types of SRS, the former may be referred to herein as "SRS for communication" and / or the latter may be referred to herein as "SRS for positioning".

[0150] Several enhancements to the previous SRS definition have been proposed for the SRS used for positioning (also known as "UL-PRS"), such as new interleaving patterns within SRS resources (except for single-symbol / comb-2), new comb types for SRS, new sequences for SRS, a greater number of SRS resource sets per component carrier, and a greater number of SRS resources per component carrier. Furthermore, the parameters "SpatialRelationInfo" and "PathLossReference" will be configured based on the downlink reference signal or SSB from the adjacent TRP. Additionally, an SRS resource can be transmitted outside the active BWP, and an SRS resource can span multiple component carriers. Furthermore, the SRS can be configured in RRC connected state and transmitted only within the active BWP. Furthermore, there may be no frequency hopping, no repetition factor, a single antenna port, and new SRS lengths (e.g., 8 and 12 symbols). Open-loop power control instead of closed-loop power control is also possible, and comb-8 (i.e., SRS transmitted every eighth subcarrier in the same symbol) can be used. Finally, the UE can transmit from multiple SRS resources used for UL-AoA via the same transmission beam. All of these are additional features of the current SRS framework, which is configured via higher-level RRC signaling (and may be triggered or enabled via MAC control element (CE) or DCI).

[0151] Figure 5D illustrates examples of various channels within the uplink time slots of a frame according to the present invention. A Random Access Channel (RACH) (also known as a Physical Random Access Channel (PRACH)) can be configured within one or more time slots in the frame based on the PRACH. A PRACH can include six consecutive RB pairs within a time slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. A Physical Uplink Control Channel (PUCCH) can be located at the edge of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. A Physical Uplink Shared Channel (PUSCH) carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0152] Please note that the terms "location reference signal" and "PRS" generally refer to the specific reference signal used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, and PRS as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink or uplink positioning reference signals unless the context otherwise indicates. If further distinction is needed regarding the type of PRS, a downlink positioning reference signal can be called "DL-PRS," and an uplink positioning reference signal (e.g., SPS, PTRS used for positioning) can be called "UL-PRS." Additionally, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), "UL" or "DL" can be added before the signal to distinguish the direction. For example, "UL-DMRS" can be different from "DL-DMRS."

[0153] NR supports many cellular network-based positioning technologies, including downlink-based, uplink-based, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. In an OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the times of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from a pair of base stations, referred to as the Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurement, and reports it to the positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations from auxiliary data. Subsequently, the UE measures the RSTD between the reference base station and each non-reference base station. Based on the RSTD measurement and the known locations of the base stations involved, the positioning entity can estimate the UE's location.

[0154] For DL-AoD positioning, the positioning entity uses beam reports of received signal strength measurements from multiple downlink transmission beams of the UE to determine multiple angles between the UE and (multiple) transmission base stations. The positioning entity can then estimate the UE's location based on the determined (multiple) angles and (multiple) known locations of the transmission base stations.

[0155] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE. For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurement and the angles of(the) receive beams(s) to determine(the) angles between the UE and(the) base stations(s). Based on the determined angles(s) and the(the) known locations of(the) base stations(s), the positioning entity can then estimate the location of the UE.

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

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

[0158] To assist in the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide auxiliary data to the UE. For example, the auxiliary data may include the identifier of the base station (or the cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive positioning sub-frames, the periodicity of the positioning sub-frames, silence sequences, frequency hopping sequences, reference signal identifiers, reference signal bandwidth, etc.), and / or other parameters applicable to a specific positioning method. Alternatively, the auxiliary data may be derived directly from the base station itself (e.g., in periodically broadcast management burden messages, etc.). In some cases, the UE may be able to detect neighboring network nodes itself without using auxiliary data.

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

[0160] Location estimation can be represented by other names, such as location estimation, location, positioning, fixed location, etc. Location estimation can be at the measurement level, including coordinates (e.g., latitude, longitude, and possible altitude); or it can be at the municipal level, including street address, postal address, or some other verbal description of the location. Location estimation can also be defined relative to another known location, or in absolute terms (e.g., using latitude, longitude, and possible altitude). Location estimation can include anticipated errors or uncertainties (e.g., by including an area or volume, the location is expected to be included within that area or volume at a specified or preset confidence level).

[0161] Figure 6 illustrates a Time Difference of Arrival (TDOA)-based positioning procedure in an exemplary wireless communication system 600 according to various embodiments of this invention. The TDOA-based positioning procedure can be an Observed Time Difference of Arrival (OTDOA) positioning procedure, such as in LTE, or a Downlink Time Difference of Arrival (DL-TDOA) positioning procedure, such as in 6G NR. In the example of Figure 6, UE 604 (e.g., any UE described herein) attempts to calculate an estimate of its location (referred to as "UE-based" positioning) or assists another entity (e.g., a base station or core network element, another UE, a location server, a third-party application, etc.) in calculating an estimate of its location (referred to as "UE-assisted" positioning). UE 604 can communicate (e.g., send information to and receive information from) one or more of a plurality of base stations 602 (e.g., any combination of base stations described herein), labeled "BS1" 602-1, "BS2" 602-2, and "BS3" 602-3.

[0162] To support location estimation, base station 602 can be configured to broadcast location reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) to UE 604 in its coverage area, enabling UE 604 to measure the characteristics of such reference signals. In a TDOA-based location procedure, UE 604 measures the time difference between specific downlink reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) transmitted by different pairs of base stations 602, referred to as Reference Signal Time Difference (RSTD) or TDOA, and either reports such RSTD measurements to a location server (e.g., location server 230, LMF 270, SLP 272) or calculates its own location estimate based on the RSTD measurements.

[0163] Typically, RSTD is measured between a reference cell (e.g., the cell supported by base station 602-1 in the example of Figure 6) and one or more neighboring cells (e.g., the cells supported by base stations 602-2 and 602-3 in the example of Figure 6). For any single location use of TDOA, the reference cell remains identical for all RSTDs measured by UE 604 and will typically correspond to either the serving cell of UE 604 or another nearby cell with good signal strength at UE 604. In one case, neighboring cells are typically cells supported by base stations different from the reference cell and may have good or poor signal strength at UE 604. Location calculations may be based on the measured RSTDs and knowledge of the locations and relative transmission timings of the base stations 602 involved (e.g., whether the base stations 602 are precisely synchronized, or whether each base station 602 transmits with a known time deviation relative to other base stations 602).

[0164] To assist TDOA-based positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide UE 604 with reference cells and auxiliary data of neighboring cells relative to the reference cells. For example, the auxiliary data may include identifiers (e.g., PCI, VCI, CGI, etc.) of each cell in the set of cells that UE 604 expects to measure (here, cells supported by base station 602). The auxiliary data may also provide the center channel frequency of each cell, various reference signal configuration parameters (e.g., the number of consecutive positioning slots, the periodicity of the positioning slots, silence sequence, frequency jump sequence, reference signal identifier, reference signal bandwidth), and / or other cell-related parameters applicable to the TDOA-based positioning procedure. The auxiliary data may also designate the UE 604's serving cell as the reference cell.

[0165] In some cases, the auxiliary data may also include an "expected RSTD" parameter, which provides the UE 604 with information about the RSTD values ​​that the UE 604 expects to measure between the reference cell and each adjacent cell in its current positioning measurement, as well as the uncertainty of the expected RSTD parameter. The expected RSTD, together with the associated uncertainty, can define a search window for the UE 604 within which the UE 604 expects to measure RSTD values. In some cases, the expected RSTD value range may be + / - 600 microseconds (µs). In some cases, when any resources used for positioning measurement are in FR1, the expected RSTD uncertainty value range may be + / - 32 µs. In other cases, when all resources used for positioning measurement(s) are in FR2, the expected RSTD uncertainty value range may be + / - 8 µs.

[0166] TDOA auxiliary information may also include positioning reference signal configuration information parameters, which allow UE 604 to determine the positioning reference signal timing relative to the reference cell, when the positioning reference signal timing will appear on the signals received from each adjacent cell, and to determine the reference signal sequence transmitted from each cell to measure the reference signal arrival time (ToA) or RSTD.

[0167] In one scenario, although the location server (e.g., location server 230, LMF 270, SLP 272) can send auxiliary data to the UE 604, alternatively, the auxiliary data can originate directly from the base station 602 itself (e.g., in periodically broadcast management burden messages, etc.). Alternatively, the UE 604 can detect neighboring base stations itself without using auxiliary data.

[0168] UE 604 (e.g., based in part on auxiliary data, if provided) can measure and (optionally) report the RSTD between reference signals received from the pair of base stations 602. Using the RSTD measurement, the known absolute or relative transmission timing of each base station 602, and the known locations of the reference and adjacent base stations(s) 602, the network (e.g., location server 230 / LMF 270 / SLP 272, base station 602) or UE 604 can estimate the location of UE 604. More specifically, the RSTD of the adjacent cell "k" relative to the reference cell "Ref" can be given as (ToA_k – ToA_Ref). In the example of Figure 6, the RSTD measurement between the reference cell of base station 602-1 and the cells of adjacent base stations 602-2 and 602-3 can be represented as T2-T1 and T3-T1, where T1, T2, and T3 represent the ToA of the reference signals from base stations 602-1, 602-2, and 602-3, respectively. UE 604 (if it is not a positioning entity) can then send the RSTD measurement to the location server or other positioning entity. Using (i) the RSTD measurement, (ii) the known absolute or relative transmission timing of each base station 602, (iii) the known location(s) of base station 602, and / or (iv) the characteristics of the directional reference signal, such as the transmission direction, the location of UE 604 (determined by UE 604 or the location server) can be determined.

[0169] In one scenario, the location estimation can specify the position of UE 604 in a two-dimensional (2D) coordinate system; however, the scenario disclosed herein is not limited to this, and if additional dimensions are required, it can also be applied to use a three-dimensional (3D) coordinate system to determine the location estimation. Furthermore, although Figure 6 illustrates one UE 604 and three base stations 602, it should be understood that there can be more UEs 604 and more base stations 602.

[0170] Still referring to Figure 6, when UE 604 uses RSTD to obtain a location estimate, the location server can provide UE 604 with necessary additional information (e.g., the location of base station 602 and relative transmission timing). In some implementations, the location estimate of UE 604 can be obtained from RSTD and other measurements performed by UE 604 (e.g., signal timing measurements from Global Positioning System (GPS) or other Global Navigation Satellite System (GNSS) satellites) (e.g., by UE 604 itself or by the location server). In these implementations, referred to as hybrid positioning, RSTD measurements can help obtain the location estimate of UE 604, but may not completely determine the location estimate.

[0171] In addition to downlink-based, uplink-based, and downlink-and-uplink-based positioning methods, NR also supports various sidelink positioning technologies. For example, link-level ranging signals can be used to estimate the distance between pairs of V-UEs or between a V-UE and a roadside unit (RSU), similar to round-trip time (RTT) positioning procedures.

[0172] Figure 7 illustrates an exemplary wireless communication system 700 according to various embodiments of this invention, wherein V-UE 704 is exchanging ranging signals with RSU 710 and another V-UE 706. As shown in Figure 7, broadband (e.g., FR1) ranging signals (e.g., Zadoff-Chu sequences) are transmitted by two endpoints (e.g., V-UE 704 and RSU 710, and V-UE 704 and V-UE 706). In one embodiment, the ranging signal may be a sidelink positioning reference signal (SL-PRS) transmitted by the involved V-UEs 704 and 706 on uplink resources. After receiving a ranging signal from a transmitter (e.g., V-UE 704), a receiver (e.g., RSU 710 and / or V-UE 706) responds by transmitting a ranging signal that includes a measurement of the difference between the time of receiving the ranging signal and the time of transmitting the responding ranging signal, which is referred to as the receiver's receive-transmit (Rx-Tx) time difference measurement.

[0173] Upon receiving a response ranging signal, the transmitter (or other positioning entity) can calculate the RTT between the transmitter and the receiver based on the receiver's Rx-Tx time difference measurement and a measurement of the difference between the transmission time of the first ranging signal and the reception time of the response ranging signal (referred to as the transmitter's transmission-reception (Tx-Rx) time difference measurement). The transmitter (or other positioning entity) uses the RTT and the speed of light to estimate the distance between the transmitter and the receiver. If one or both of the transmitter and the receiver are capable of beamforming, the angle between V-UEs 704 and 706 can also be determined. Furthermore, if the receiver provides its Global Positioning System (GPS) position in the response ranging signal, the transmitter (or other positioning entity) can determine the absolute position of the transmitter, rather than its relative position to the receiver.

[0174] It is understandable that ranging accuracy improves with the bandwidth of the ranging signal. Specifically, higher bandwidth can better separate different multipath paths of the ranging signal.

[0175] Note that this positioning procedure assumes that the V-UE involved is time-synchronized (i.e., its system frame time is the same as (multiple) other V-UEs, or has a known deviation relative to (multiple) other V-UEs). Furthermore, although Figure 7 illustrates two V-UEs, it should be understood that they do not have to be V-UEs, but can be any other type of UE capable of sidelink communication.

[0176] Traditionally, sidelink ranging (RTT) between UEs is used to provide additional constraints for positioning. As mentioned above, this requires the UE to accurately estimate the Rx-Tx turnaround time. If the UE cannot be calibrated to determine the sidelink ranging (RTT), the RTT measurement will be inaccurate. Many SL UEs do not support Rx-Tx time measurement functionality.

[0177] In some designs, a reference UE associated with a known location (e.g., from the nearest fixed location with a threshold accuracy level) can be used instead of a fixed device (e.g., a GNB) to assist various positioning procedures. However, gNBs are typically highly synchronized, and the timing drift between the gNB time base and the reference UE time base may be unknown. This unknown timing drift may make it difficult to use the reference UE in TDOA-based positioning schemes.

[0178] The various forms of this case are therefore aimed at hybrid SL-based TDOA technologies (e.g., a combination of SL and DL TDOA, or a combination of SL and UL TDOA), whereby the positioning estimate is based on the time deviation between the base station and the reference UE. In some designs, incorporating the time deviation into the positioning estimate can facilitate the inclusion of the reference UE in the TDOA positioning procedure, which can increase the positioning accuracy of the target UE and / or facilitate the positioning of the target UE when other positioning schemes (e.g., RTT-based positioning schemes) are unavailable (e.g., due to the lack of support from one or more UEs involved in the TDOA positioning procedure, or an insufficient number of GNBs, etc.).

[0179] Figure 8 illustrates an exemplary process 800 of wireless communication according to various embodiments of the present invention. In one embodiment, process 800 may be performed by a location estimation entity, such as UE 302 (e.g., for UE-based location), or an LMF integrated with BS 304 or network entity 306 (e.g., location server, core network element, etc.).

[0180] Referring to FIG8, at 810, a positioning estimation entity (e.g., receiver 312 or 322 or 352 or 362, (multiple) network interfaces 380 or 390, data bus 382, ​​etc.) acquires first timing information associated with a first time of arrival (TOA) measurement of a first positioning reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base.

[0181] Referring to FIG8, at 820, the location estimation entity (e.g., receiver 312 or 322 or 352 or 362, (multiple) network interfaces 380 or 390, data bus 382, ​​etc.) acquires second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE, the reference UE being associated with a known location and having a second time base different from the first time base.

[0182] Referring to Figure 8, at 830, the positioning estimation entity (e.g., (multiple) processors 332 or 384 or 394, positioning estimation module 342 or 388 or 398, etc.) determines the deviation between the first time base and the second time base.

[0183] Referring to FIG8, at 840, the positioning estimation entity (e.g., (multiple) processors 332 or 384 or 394, positioning estimation module 342 or 388 or 398, etc.) determines the positioning estimation of the target UE via TDOA positioning technology based at least in part on the first timing information, the second timing information and the deviation.

[0184] Referring to FIG8, in some designs, the location estimation entity may also acquire third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and the first radio node, and acquire fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and the second radio node. In this case, the location estimation decision is also based on the third and fourth timing information. In some designs, the first and second radio nodes include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof. In other words, the TDOA location procedure of FIG8 may involve one gNB and multiple reference UEs (1:N), or multiple gNBs and one reference UE (N:1), or multiple gNBs and multiple reference UEs (N:N).

[0185] Referring to Figure 8, in some designs, the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, whereby the first RS-P corresponds to the DL-PRS and the second RS-P corresponds to the sidelink PRS (SL-PRS). In other designs, the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, whereby the first RS-P corresponds to the uplink detection reference (UL-SRS-P) used for positioning, and the second RS-P corresponds to either the UL-SRS-P or the sidelink PRS (SL-PRS).

[0186] Referring to Figure 8, in some designs, the offset decision at 830 is triggered in conjunction with the triggering of the positioning estimation decision at 840. In other words, when the positioning estimation procedure involving (multiple) reference UEs is triggered, the time offset calibration procedure is also triggered. In other designs, the offset decision at 830 is triggered independently of the triggering of the positioning estimation decision at 840 and is triggered within a threshold time period of that triggering. In other words, as long as a fairly recent offset calibration has been performed, it is not necessary to trigger the offset calibration procedure by triggering the positioning estimation procedure involving (multiple) reference UEs.

[0187] Referring to Figure 8, in some designs, the bias is determined based on a first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE. In some designs, the bias is also determined based on a second difference between the estimated propagation time between another base station and the reference UE based on their respective known locations and the measured propagation time between the other base station and the reference UE.

[0188] The following describes in detail, with reference to Figures 9-10, a detailed exemplary implementation of process 800 in Figure 8.

[0189] Figure 9 illustrates a communication system 900 according to various embodiments of the present invention. In Figure 9, the communication system 900 includes gNB1, gNB2, a reference UEa associated with a first known location, a reference UEb associated with a second known location, and target UE0 and UE1 with unknown locations. In Figure 9, it is assumed that the gNB timing between gNB1 and gNB2 is highly calibrated (e.g., the timing basis difference is below a threshold), and the distance from each gNB to each reference UE is known.

[0190] Regarding Figure 9, the RS-P-based ranging measurement (r) from the source device to the target device can be represented as (r, source device ID, target device ID). Therefore, as an example, the ranging measurement based on DL-PRS from gNB1 to UEa is represented as "r1a". This ranging measurement is based on the actual propagation delay between the source device and the target device, and the corresponding deviation, which can be represented as b, for example: where r1a is based on the propagation delay () from gNB1 to UEa plus the deviation (), and so on.

[0191] The corresponding deviation can be calculated as follows:

[0192] Figure 10 illustrates an isochronous line 1000 of an exemplary implementation of the process based on Figure 8 according to one aspect of this case. In Figure 10, gNB (e.g., which may correspond to gNB1 or gNB2 in Figure 9) transmits DL-PRS 1010 measured by UE0. The propagation time from gNB to UE0 is denoted as _(_L_0 - _L_0). Reference UEa transmits UL-SRS-P or SL-PRS, also measured by UE0, at 1020. The propagation time from reference UEa to UE0 is denoted as _(_L_0 - _L_0). The deviation between gNB and reference UEa is expressed as Δ_(gNB-gNB), and the TDOA between the TOA of DL-PRS 1010 measured at UE0 and the TOA of UL-SRS or SL-PRS 1020 is expressed as Δ_(gNB-gNB-gNB0). Although not explicitly illustrated in Figure 10, the TOA of DL-PRS 1010 and the TOA of UL-SRS or SL-PRS 1020 can also be measured at UE1, and the TOA or the UL-SRS or SL-PRS from UEb (not explicitly illustrated in Figure 10) can also be measured at both UE0 and UE1. In this case: each delta (Δ) is related to the observation from gNB1 at UE0 and UE1, and each (b) variable represents the estimated deviation between UEa or UEb and gNB1. A similar procedure can be performed for gNB2.

[0193] For each UE (UE0 or UE1) with an unknown location, the following set of observations from nodes (gNB1, gNB2, UEa, and UEb) with known locations can be aggregated, for example:

[0194] In some designs, if only one reference UE (e.g., UEa) is available, then we only have the first three equations relating to UEa. Because the equations are not linearly independent, this may result in two available equations. The addition of a second reference UE (UEb) can thus provide additional equations (three of the five equations mentioned above are available). In some TDOA techniques, three equations are required to solve for the location of UE0. Therefore, using four reference nodes, three equations can be obtained to solve for the location of UE0. As mentioned above, these four reference nodes can be used in any combination, as long as at least one of the four reference nodes is a gNB associated with a known timing sequence.

[0195] Although Figures 9-10 are related to the hybrid SL+DL-TDOA technology, other forms can be used for SL+UL-TDOA technology. In this case, UE0 can transmit UL-SRS-P instead of DL-PRS 1010 shown in Figure 10, and 𝑇_(𝑔𝑁𝐵-𝑈𝐸0) instead of 𝑇_(𝑈𝐸0-𝑔𝑁𝐵), etc.

[0196] As can be seen from the detailed description above, different features are combined together in the examples. This manner of disclosure should not be construed as an intention for the exemplary clauses to have more features than expressly mentioned in each clause. Rather, the various forms of this document may include fewer features than those of the individual exemplary clauses disclosed. Therefore, the following clauses should be considered as included in the specification, where each clause may be considered a separate example on its own. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the form(s) of that dependent clause is not limited to that specific combination. It should be understood that other exemplary clauses may also include combinations of the form(s) of dependent clauses with the subject matter of any other dependent or independent clause, or any feature combined with other dependent and independent clauses. The various forms disclosed herein expressly include such combinations unless expressly stated or it can be readily inferred that a specific combination is not intended (e.g., contradictory forms, such as defining an element as both an insulator and a conductor). Furthermore, it is also intended that the form of a clause be included in any other independent clause, even if that clause is not directly subordinate to an independent clause.

[0197] The following numbered clauses describe implementation examples:

[0198] Clause 1. A method for operating a location estimation entity, comprising the steps of: acquiring first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquiring second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE, the reference UE being associated with a known location and having a second time base different from the first time base; determining a deviation between the first time base and the second time base; and determining a location estimation of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

[0199] Clause 2. The method according to Clause 1 also includes the following steps: acquiring third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and the first radio node; and acquiring fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and the second radio node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

[0200] Clause 3. The method according to Clause 2, wherein the first wireless node and the second wireless node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0201] Article 4. The method according to any one of Articles 1 to 3, wherein the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to the downlink positioning reference signal (DL-PRS), and wherein the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0202] Clause 5. The method according to any one of Clauses 1 to 4, wherein the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) used for positioning, and wherein the second RS-P corresponds to UL-SRS-P or sidelink PRS (SL-PRS).

[0203] Article 6. The method according to any one of Articles 1 to 5, wherein the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0204] Clause 7. The method of any one of Clauses 1 to 6, wherein the deviation decision is triggered in conjunction with the triggering of the positioning estimation decision.

[0205] Clause 8. The method of any one of Clauses 1 to 7, wherein the deviation decision is triggered independently of the location estimation decision and within the threshold time period for triggering the location estimation decision.

[0206] Clause 9. The method of any one of Clauses 1 to 8, wherein the bias is determined based on a first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0207] Clause 10. The method of any one of Clauses 1 to 9, wherein the deviation is also determined based on a second difference between the estimated propagation time between the other base station and the reference UE based on the respective known location and the measured propagation time between the other base station and the reference UE.

[0208] Clause 11. A location estimation entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: acquire first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquire second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE, the reference UE being associated with a known location and having a second time base different from the first time base; determine a deviation between the first time base and the second time base; and determine a location estimate of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

[0209] Clause 12. The location estimation entity pursuant to Clause 11, wherein at least one processor is also configured to: acquire third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and the first radio node; and acquire fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and the second radio node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

[0210] Clause 13. The location estimation entity pursuant to Clause 12, wherein the first radio node and the second radio node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0211] Clause 14. A location estimation entity according to any one of Clauses 11 to 13, wherein the TDOA location technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) location technology, wherein the first RS-P corresponds to the downlink location reference signal (DL-PRS), and wherein the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0212] Clause 15. A location estimation entity according to any one of Clauses 11 to 14, wherein the TDOA location technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) location technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) used for location, and wherein the second RS-P corresponds to either UL-SRS-P or a sidelink PRS (SL-PRS).

[0213] Article 16. A location estimation entity pursuant to any one of Articles 11 to 15, wherein the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0214] Article 17. A positioning estimation entity pursuant to any of Articles 11 to 16, wherein a deviation decision is triggered in conjunction with the triggering of a positioning estimation decision.

[0215] Clause 18. A location estimation entity pursuant to any of Clauses 11 to 17, wherein a bias decision is triggered independently of the location estimation decision and within the threshold time period for triggering the location estimation decision.

[0216] Clause 19. A location estimation entity pursuant to any of Clauses 11 to 18, wherein the bias is determined based on a first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0217] Clause 20. The location estimation entity pursuant to any of Clauses 11 to 19, wherein the bias is also determined based on a second difference between the estimated propagation time between the other base station and the reference UE based on the respective known location and the measured propagation time between the other base station and the reference UE.

[0218] Clause 21. A location estimation entity, comprising: means for acquiring first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; means for acquiring second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE, the reference UE being associated with a known location and having a second time base different from the first time base; means for determining a deviation between the first time base and the second time base; and means for determining a location estimate of the target UE via a time difference of arrival (TDOA) location technique, based at least in part on the first timing information, the second timing information, and the deviation.

[0219] Clause 22. The location estimation entity pursuant to Clause 21 also includes: a component for acquiring third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and the first radio node; and a component for acquiring fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and the second radio node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

[0220] Article 23. The location estimation entity pursuant to Article 22, wherein the first radio node and the second radio node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0221] Clause 24. A location estimation entity according to any one of Clauses 21 to 23, wherein the TDOA location technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) location technology, wherein the first RS-P corresponds to the downlink location reference signal (DL-PRS), and wherein the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0222] Clause 25. A location estimation entity according to any one of Clauses 21 to 24, wherein the TDOA location technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) location technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) used for location, and wherein the second RS-P corresponds to either UL-SRS-P or a sidelink PRS (SL-PRS).

[0223] Article 26. A location estimation entity pursuant to any one of Articles 21 to 25, wherein the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0224] Clause 27. A positioning estimation entity pursuant to any of Clauses 21 to 26, wherein a deviation decision is triggered in conjunction with the triggering of a positioning estimation decision.

[0225] Clause 28. A location estimation entity pursuant to any of Clauses 21 to 27, wherein a bias decision is triggered independently of the location estimation decision and within a threshold time period for triggering the location estimation decision.

[0226] Clause 29. A location estimation entity pursuant to any of Clauses 21 to 28, wherein the bias is determined based on a first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0227] Clause 30. The location estimation entity pursuant to any of Clauses 21 to 29, wherein the bias is also determined based on a second difference between the estimated propagation time between the other base station and the reference UE based on the respective known location and the measured propagation time between the other base station and the reference UE.

[0228] Clause 31. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: acquire first timing information associated with a first time of arrival (TOA) measurement of a first positioning reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquire second timing information associated with a second TOA measurement of a second RS-P communicating between a target UE and a reference UE, the reference UE being associated with a known location and having a second time base different from the first time base; determine a deviation between the first time base and the second time base; and determine a positioning estimate of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

[0229] Clause 32. A non-transitory computer-readable medium pursuant to Clause 31, wherein one or more instructions also cause the location estimation entity to: acquire third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and the first radio node; and acquire fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and the second radio node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

[0230] Clause 33. Non-transitory computer-readable media pursuant to Clause 32, wherein the first wireless node and the second wireless node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

[0231] Article 34. A non-transitory computer-readable medium pursuant to any one of Articles 31 to 33, wherein the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to the downlink positioning reference signal (DL-PRS), and wherein the second RS-P corresponds to the sidelink PRS (SL-PRS).

[0232] Clause 35. A non-transitory computer-readable medium pursuant to any of Clauses 31 to 34, wherein the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) used for positioning, and wherein the second RS-P corresponds to either UL-SRS-P or a sidelink PRS (SL-PRS).

[0233] Article 36. Non-transitory computer-readable media pursuant to any one of Articles 31 to 35, wherein the location estimation entity corresponds to a base station, a reference UE, a location management function (LMF), a location server, a target UE, or a combination thereof.

[0234] Clause 37. Non-transitory computer-readable media pursuant to any of Clauses 31 to 36, wherein a bias decision is triggered in conjunction with the triggering of a positioning estimation decision.

[0235] Clause 38. A non-transitory computer-readable medium pursuant to any of Clauses 31 to 37, wherein a bias decision is triggered independently of the location estimation decision and within a threshold time period for triggering the location estimation decision.

[0236] Clause 39. Non-transitory computer-readable media pursuant to any of Clauses 31 to 38, wherein the bias is determined based on a first difference between the estimated propagation time between the base station and the reference UE based on their respective known locations and the measured propagation time between the base station and the reference UE.

[0237] Clause 40. Non-transitory computer-readable media pursuant to any of Clauses 31 to 39, wherein the deviation is also determined based on a second difference between the estimated propagation time between the other base station and the reference UE based on the respective known locations and the measured propagation time between the other base station and the reference UE.

[0238] Those familiar with this technology will understand that information and signals can be represented using a variety of different technologies and processes. For example, the data, instructions, commands, information, signals, bits, symbols, and chips described above can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0239] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the various forms disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative elements, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether this functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as leading outside the scope of this work.

[0240] The various illustrative logic blocks, modules, and circuits described herein can be implemented or executed using a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

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

[0242] In one or more exemplary embodiments, the described functionality can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, such functionality can be stored or transferred as one or more instructions or code to a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, with communication media including any media that facilitates the transfer of computer programs from one place to another. Storage media can be any available media accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection is properly referred to as computer-readable media. 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 technology (such as infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) are included in the definition of media. The magnetic disks and optical disks used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0243] Although the foregoing disclosure presents an illustrative sample of the content of this case, it should be noted that various changes and modifications may be made herein without departing from the scope of the content of this case as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the disclosed sample described herein do not need to be performed in any particular order. Furthermore, although elements of this case may be described or claimed in the singular form, the plural form may be expected unless explicitly limited to the singular. [Simplified Explanation of the Diagram]

[0046] The accompanying drawings are provided to help describe the various states of this case, and the drawings are only for illustrating the states and not for limiting them.

[0047] Figure 1 illustrates an exemplary wireless communication system according to various aspects of this case.

[0048] Figures 2A and 2B illustrate exemplary wireless network structures according to various aspects of this case.

[0049] Figures 3A, 3B and 3C respectively illustrate simplified block diagrams of several exemplary states of elements that can be used in user equipment (UE), base station and network entity and configured to support the communications taught herein.

[0050] Figure 4 is a block diagram illustrating various components of an exemplary user equipment (UE) according to various aspects of this case.

[0051] Figures 5A to 5D are diagrams illustrating exemplary frame structures and channels within the frame structures according to various forms of this case.

[0052] Figure 6 illustrates a positioning procedure based on Time Difference of Arrival (TDOA) in an exemplary wireless communication system according to various aspects of this case.

[0053] Figure 7 illustrates an exemplary wireless communication system according to various aspects of this case, wherein a vehicle user equipment (V-UE) is exchanging ranging signals with a roadside unit (RSU) and another V-UE.

[0054] Figure 8 illustrates an exemplary process 800 of wireless communication according to various forms of this case.

[0055] Figure 9 illustrates a communication system 900 according to various forms of this case.

[0056] Figure 10 illustrates an isochronous line 1000 of an exemplary implementation of the process based on Figure 8 according to one aspect of this case. [Biomaterial Storage]

[0245] Domestic storage information (please note in order of storage institution, date, and number): None. International storage information (please note in order of storage country, institution, date, and number): None.

Claims

1. A method of operating a location estimation entity, comprising the steps of: acquiring first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquiring second timing information associated with a second TOA measurement of a second RS-P communicating between the target UE and a reference UE associated with a known location and having a second time base different from the first time base; determining a deviation between the first time base and the second time base; and determining a location estimate of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

2. The method according to claim 1 also includes the following steps: obtaining third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and a first radio node; and obtaining fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and a second radio node, wherein the decision of the location estimation is also based on the third timing information and the fourth timing information.

3. The method according to claim 2, wherein the first radio node and the second radio node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

4. The method according to request item 1, wherein the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to a downlink positioning reference signal (DL-PRS), and wherein the second RS-P corresponds to a sidelink PRS (SL-PRS).

5. The method according to Request 1, wherein the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) for positioning, and wherein the second RS-P corresponds to the UL-SRS-P or a sidelink PRS (SL-PRS).

6. The method according to request item 1, wherein the location estimation entity corresponds to the base station, the reference UE, a location management function (LMF), a location server, the target UE, or a combination thereof.

7. According to the method of request item 1, wherein the deviation decision is triggered in conjunction with a trigger of the positioning estimation decision.

8. The method of request item 1, wherein the deviation decision is triggered independently of the location estimation decision and within a threshold time period during which the location estimation decision is triggered.

9. The method of request item 1, wherein the deviation is determined based on a first difference between an estimated propagation time between the base station and the reference UE based on their respective known locations and a measured propagation time between the base station and the reference UE.

10. The method of claim 1, wherein the deviation is also determined based on a second difference between an estimated propagation time between the other base station and the reference UE based on their respective known locations and a measured propagation time between the other base station and the reference UE.

11. A location estimation entity, comprising: One memory; At least one transceiver; The system includes at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: acquire first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquire second timing information associated with a second TOA measurement of a second RS-P communicating between the target UE and a reference UE associated with a known location and having a second time base different from the first time base; determine a deviation between the first time base and the second time base; and determine a location estimate of the target UE via a time difference of arrival (TDOA) positioning technique, at least in part based on the first timing information, the second timing information, and the deviation.

12. The location estimation entity according to request item 11, wherein the at least one processor is also configured to: acquire third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and a first radio node; and acquire fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and a second radio node, wherein the decision of the location estimation is also based on the third timing information and the fourth timing information.

13. The location estimation entity according to request item 12, wherein the first radio node and the second radio node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

14. The location estimation entity according to request item 11, wherein the TDOA location technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) location technology, wherein the first RS-P corresponds to a downlink location reference signal (DL-PRS), and wherein the second RS-P corresponds to a sidelink PRS (SL-PRS).

15. The location estimation entity according to request item 11, wherein the TDOA location technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) location technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) for location, and wherein the second RS-P corresponds to the UL-SRS-P or a sidelink PRS (SL-PRS).

16. The location estimation entity according to request item 11, wherein the location estimation entity corresponds to the base station, the reference UE, a location management function (LMF), a location server, the target UE, or a combination thereof.

17. The location estimation entity according to request item 11, wherein the deviation decision is triggered in conjunction with a trigger of the location estimation decision.

18. The location estimation entity according to request item 11, wherein the deviation decision is triggered independently of the location estimation decision and within a threshold time period during which the location estimation decision is triggered.

19. The location estimation entity according to request item 11, wherein the deviation is determined based on a first difference between an estimated propagation time between the base station and the reference UE based on their respective known locations and a measured propagation time between the base station and the reference UE.

20. The location estimation entity according to request item 11, wherein the deviation is also determined based on a second difference between an estimated propagation time between the other base station and the reference UE based on their respective known locations and a measured propagation time between the other base station and the reference UE.

21. A location estimation entity, comprising: The components include: components for acquiring first timing information associated with a first time of arrival (TOA) measurement of a first positioning reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; components for acquiring second timing information associated with a second TOA measurement of a second RS-P communicating between the target UE and a reference UE associated with a known location and having a second time base different from the first time base; components for determining a deviation between the first time base and the second time base; and components for determining a location estimate of the target UE via a time difference of arrival (TDOA) positioning technique, based at least in part on the first timing information, the second timing information, and the deviation.

22. The location estimation entity according to request item 21 also includes: The component for acquiring third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and a first radio node; and the component for acquiring fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and a second radio node, wherein the determination of the positioning estimation is also based on the third timing information and the fourth timing information.

23. The location estimation entity according to request item 22, wherein the first radio node and the second radio node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

24. The location estimation entity according to request item 21, wherein the TDOA location technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) location technology, wherein the first RS-P corresponds to a downlink location reference signal (DL-PRS), and wherein the second RS-P corresponds to a sidelink PRS (SL-PRS).

25. The location estimation entity according to request item 21, wherein the TDOA location technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) location technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) for location, and wherein the second RS-P corresponds to the UL-SRS-P or a sidelink PRS (SL-PRS).

26. The location estimation entity according to request item 21, wherein the location estimation entity corresponds to the base station, the reference UE, a location management function (LMF), a location server, the target UE, or a combination thereof.

27. The location estimation entity according to request item 21, wherein the deviation decision is triggered in conjunction with a trigger of the location estimation decision.

28. The location estimation entity according to request item 21, wherein the deviation decision is triggered independently of the location estimation decision and within a threshold time period during which the location estimation decision is triggered.

29. The location estimation entity according to request item 21, wherein the deviation is determined based on a first difference between an estimated propagation time between the base station and the reference UE based on their respective known locations and a measured propagation time between the base station and the reference UE.

30. The location estimation entity according to request item 21, wherein the deviation is also determined based on a second difference between an estimated propagation time between the other base station and the reference UE based on their respective known locations and a measured propagation time between the other base station and the reference UE.

31. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a location estimation entity, cause the location estimation entity to: acquire first timing information associated with a first time of arrival (TOA) measurement of a first location reference signal (RS-P) communicating between a target user equipment (UE) and a base station having a first time base; acquire second timing information associated with a second TOA measurement of a second RS-P communicating between the target UE and a reference UE associated with a known location and having a second time base different from the first time base; determine a deviation between the first time base and the second time base; and determine a location estimate of the target UE via a time difference of arrival (TDOA) location technique, at least in part based on the first timing information, the second timing information, and the deviation.

32. The non-transitory computer-readable medium pursuant to request item 31, wherein the one or more instructions also cause the location estimation entity to: acquire third timing information associated with a third TOA measurement of a third RS-P communicating between the target UE and a first radio node; and acquire fourth timing information associated with a fourth TOA measurement of a fourth RS-P communicating between the target UE and a second radio node, wherein the determination of the location estimation is also based on the third timing information and the fourth timing information.

33. The non-transitory computer-readable medium according to claim 32, wherein the first wireless node and the second wireless node include at least one other base station, at least one other reference UE associated with at least one other known location, or a combination thereof.

34. The non-transitory computer-readable medium according to claim 31, wherein the TDOA positioning technology is a hybrid sidelink and downlink TDOA (SL+DL-TDOA) positioning technology, wherein the first RS-P corresponds to a downlink positioning reference signal (DL-PRS), and wherein the second RS-P corresponds to a sidelink PRS (SL-PRS).

35. The non-transitory computer-readable medium according to claim 31, wherein the TDOA positioning technology is a hybrid sidelink and uplink TDOA (SL+UL-TDOA) positioning technology, wherein the first RS-P corresponds to an uplink detection reference (UL-SRS-P) for positioning, and wherein the second RS-P corresponds to the UL-SRS-P or a sidelink PRS (SL-PRS).

36. The non-transitory computer-readable medium according to request item 31, wherein the location estimation entity corresponds to the base station, the reference UE, a location management function (LMF), a location server, the target UE, or a combination thereof.

37. The non-transitory computer-readable medium according to request item 31, wherein the deviation decision is triggered in conjunction with a trigger of the positioning estimation decision.

38. The non-transitory computer-readable medium according to request item 31, wherein the deviation decision is triggered independently of the location estimation decision and within a threshold time period for triggering the location estimation decision.

39. The non-transitory computer-readable medium according to claim 31, wherein the deviation is determined based on a first difference between an estimated propagation time between the base station and the reference UE based on their respective known locations and a measured propagation time between the base station and the reference UE.

40. The non-transitory computer-readable medium according to request item 31, wherein the deviation is also determined based on a second difference between an estimated propagation time between the other base station and the reference UE based on the respective known locations and a measured propagation time between the other base station and the reference UE.

Images