TW202303184A - Notch filter codephase impact mitigation - Google Patents

Abstract

Techniques are provided for utilizing notch filters to overcome narrowbandjamming. An example method for determining a range to a satellite vehicle with a receiver includes receiving a signal from the satellite vehicle, determining one or more notch filter configurations, determining a pseudorandom noise code and a doppler frequency associated with the signal, determining a codephase correction value based at least on the one or more notch filter configurations, the pseudorandom noise code and the doppler frequency, and computing the range to the satellite vehicle based at least in part on the signal and the codephase correction value.

Description

Notch Filter Code Phase Effect Mitigation

The present invention is concerned with mitigation of notch filter code phase effects.

Wireless communication systems have been developed for several generations, including the first generation analog wireless telephone service (1G), the second generation (2G) digital wireless telephone service (including 2.5G and 2.75G networks for transition), the third generation (3G ) high-speed data, Internet-enabled wireless services, fourth-generation (4G) services (such as Long-Term Evolution (LTE) or WiMax) and fifth-generation (5G) services, etc. There are many different types of wireless communication systems in use today, including cellular and Personal Communications Service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), A digital cellular system such as the Global System for Mobile Access (GSM) variant of TDMA.

It is often desirable to know the location of a user equipment (UE) (eg, a cellular phone), and the terms "location" and "position" may be used synonymously and interchangeably herein. A location service (LCS) client may wish to know the UE's location and may communicate with a location center to request the UE's location. The location center and the UE may appropriately exchange messages to obtain a location estimate for the UE. The location center may return a location estimate to the LCS client, eg, for one or more applications.

Obtaining the location of a mobile device that is accessing a wireless network can be useful for many applications including, for example, emergency dialing, personal navigation, asset tracking, locating friends or family members, and the like. Existing positioning methods include methods based on the measurement of radio signals emitted from various devices, including satellite vehicles in wireless networks and terrestrial radio sources, such as base stations and access points.

Many UEs include Global Navigation Satellite System (GNSS) receivers and can determine position by precisely measuring the time of arrival of signaling events received from multiple satellites. Satellite vehicles (SVs) in GNSS typically transmit data using a form of spread spectrum coding. For example, the Global Positioning System (GPS) utilizes Code Division Multiple Access (CDMA). Each SV is assigned a pseudo-random noise-like Coarse Acquisition (CA) code, and each SV has a unique CA code. Each SV uses its own CA code to encode data and transmit the coded data on the carrier frequency. Therefore, multiple SVs may simultaneously transmit data on a shared carrier frequency. Each CA code consists of a sequence of 1023 "chips," where each chip is assigned a value of 1 or 0. The CA code is transmitted at a rate of 1.023 MHz, therefore, each chip cycle is approximately 0.977 us. Each SV continuously transmits a repeating pattern consisting of the SV's own CA code. GPS SV can encode navigation or system data by inverting the transmitted CA code. The CA code phase refers to the relationship between the CA code and the reference clock or other CA codes transmitted by other SVs. Although the CA code phase may be synchronized between SVs when transmitted, the CA code may be received with different delays at the GPS receiver due to differences in propagation time. Typically, the GPS receiver determines which CA codes are being received in order to determine which GPS satellites are in view.

There are many obstacles to receiving signals from GPS satellites. In particular, UEs that are also configured to utilize other wireless technologies, such as Wi-Fi, Bluetooth, and other cellular-based technologies, may generate signals that interfere with the spread spectrum used by GNSS receivers. For example, harmonics or other artifacts of an oscillator within the UE may cause localized jamming of one or more regions within the radio spectrum utilized by the GNSS receiver. Notch filtering within a GNSS receiver can be used to reduce the effect of such interfering signals.

An example method for determining the range to a satellite vehicle using a receiver according to the present disclosure includes: receiving a signal from the satellite vehicle; determining one or more notch filter configurations; determining a pseudorandom noise code and correlating with the signal the associated Doppler frequency; determine a code phase correction value based at least on one or more notch filter configurations, a pseudorandom noise code, and the Doppler frequency; Tool distance (range).

Implementations of such a method may include one or more of the following features. Determining a code phase correction value may include obtaining a code phase correction value from a lookup table based on one or more notch filter configurations, a pseudorandom noise code, and a Doppler frequency. Ancillary data may be received from a network entity, where the auxiliary data includes a lookup data table. Auxiliary data may be received via one or more Long Term Positioning Protocol (LPP) messages. The assistance data can be received via one or more radio resource control (RRC) messages. Determining the code phase correction value may include obtaining the code phase correction value based on an interpolation function. The look-up table may be generated by a receiver based on a modeled autocorrelation function of a plurality of notch filter configurations, and wherein determining a code phase correction value includes determining a code phase correction value based on one or more notch filter configurations, pseudorandom noise codes, and both Obtain the code phase correction value from the reference table for the Buller frequency. The one or more notch filter configurations may include one or more notch frequencies and one or more bandwidths associated with the one or more notch frequencies. Calculating the range to the satellite vehicle may include determining a pseudorange to the satellite vehicle based on the signal. The receiver may include one or more notch filters consisting of one or more digital filters with programmable center frequencies and bandwidths.

An example apparatus according to the present disclosure includes: a memory; at least one satellite positioning system receiver configured to receive signals from a satellite vehicle; at least one processor communicatively coupled to the memory and the at least one satellite positioning system receiver and configured to: receive a signal from a satellite vehicle, determine one or more notch filter configurations, determine a pseudorandom noise code and a Doppler frequency associated with the signal, based at least on one or more notch filter configurations , the pseudorandom noise code and the Doppler frequency determine a code phase correction value, and calculate a range to the satellite vehicle based at least in part on the signal and the code phase correction value.

Implementations of such an apparatus may include one or more of the following features. The at least one processor may also be configured to obtain code phase correction values from a look-up table based on one or more notch filter configurations, pseudorandom noise codes, and Doppler frequencies. The apparatus may include at least one transceiver communicatively coupled to at least one processor such that the at least one processor is also configured to receive auxiliary data from a network entity, and wherein the auxiliary data includes a lookup data table. Auxiliary data may be received via one or more Long Term Positioning Protocol (LPP) messages. The assistance data can be received via one or more radio resource control (RRC) messages. The at least one processor may also be configured to obtain a code phase correction value based on an interpolation function. The at least one processor may also be configured to generate a look-up table based on a modeled autocorrelation function of the plurality of notch filter configurations, and based on one or more notch filter configurations, pseudorandom noise codes and Obtain the code phase correction value from the reference table for the Le frequency. The one or more notch filter configurations may include one or more notch frequencies and one or more bandwidths associated with the one or more notch frequencies. The at least one processor may also be configured to determine a pseudorange to a satellite vehicle based on the signal. The one or more notch filter configurations may include one or more digital filters with programmable center frequencies and bandwidths.

An example apparatus for determining a range to a satellite vehicle according to the present disclosure includes means for receiving a signal from the satellite vehicle; means for determining one or more notch filter configurations; means for a code and a Doppler frequency associated with a signal; means for determining a code phase correction value based at least on one or more notch filter configurations, a pseudorandom noise code, and a Doppler frequency; and means for calculating a range to a satellite vehicle based at least in part on signal and code phase correction values.

An example non-transitory processor-readable storage medium including processor-readable instructions for causing one or more processors to determine a distance to a satellite vehicle according to the present disclosure includes a device for receiving signals from a satellite vehicle. code; code for determining one or more notch filter configurations; code for determining a pseudorandom noise code and a Doppler frequency associated with a signal; for filtering based at least on one or more notch filters A code for determining a code phase correction value based on the configuration of the transmitter, a pseudorandom noise code, and a Doppler frequency; and a code for calculating a range to a satellite vehicle based at least in part on the signal and the code phase correction value.

The projects and/or technologies described herein may provide one or more of the following capabilities, as well as others not mentioned. GNSS receivers can receive signals in the radio spectrum from satellite vehicles. Reception may be impaired on one or more frequencies in the spectrum due to local interference. Notch filters can be used to mitigate the effects of interference. The accuracy of the code phase measurement may be reduced due to the use of the notch filter. The effect on the code phase measurement depends on the pseudo random noise code of the received signal, the satellite vehicle Doppler frequency and notch configuration. A look-up table may be generated to select a code phase correction value based on the pseudorandom noise code of the received signal, the satellite vehicle Doppler frequency, and the notch configuration. The lookup data table can be generated locally on the GNSS receiver and/or received from the network as auxiliary data. Code phase correction values can be used to improve distance calculations. The accuracy of GNSS position estimates may be improved. Other capabilities may also be provided, and not every implementation in accordance with the present disclosure is required to provide any, let alone all, of the capabilities discussed.

This article discusses techniques for overcoming narrowband interference using notch filters. A notch filter is defined as any receiver element or process that attenuates or removes a portion of the received signal. For example, a programmable filter can be used to attenuate a portion of the received spectrum around a programmed narrowband interferer frequency. Alternatively, a self-tuning filter that automatically updates its frequency response can be utilized to attenuate the received spectrum around any narrowband jammers that appear dynamically. Alternatively, an interference canceller can be utilized, where narrowband interfering signals are estimated and subtracted from the received signal. Filtering or interference cancellation may be implemented by analog or digital means or any combination thereof. The digital front end (DFE) in a GNSS receiver can utilize notch filters to mitigate the effects of narrowband interference, such as that caused by primary and/or harmonic signals generated by other oscillators in the mobile device. In operation, the notch filter may affect the code phase measurements obtained by the GNSS receiver, and thus may also affect the accuracy of the position estimates based on the measurements. Distortion in code-phase measurements can be based on several factors, such as the number and bandwidth of notch filters, the pseudo-random noise (PRN) code with which the SV is transmitted, and the notch frequency relative to the SV Doppler frequency. In an example, techniques provided herein utilize one or more look-up tables (LUTs) to determine a code phase error value based on a PRN code, notch frequency, notch width, and SV Doppler frequency. The LUT may be provided to the UE via a communication network (eg, as distance assistance data) and/or other device-to-device communication links. In another example, the code phase error value may be generated online (that is, generated locally on the UE) based on the PRN code, notch frequency, notch bandwidth and SV Doppler frequency. On-line generation of code phase error can mitigate dynamic notch filtering. These techniques and configurations are examples, and other techniques and configurations may be used.

Referring to FIG. 1 , an example communication system 100 includes UE 105, radio access network (RAN) 135 (here fifth generation (5G) next generation (NG) RAN (NG-RAN) and 5G core network (5GC) 140. The UE 105 may be, for example, an IoT device, a location tracking device, a cellular phone or other device. The 5G network may also be referred to as a New Radio (NR) network; the NG-RAN 135 may be referred to as 5G RAN or NR RAN; And 5GC 140 may be called NG Core Network (NGC). Standardization of NG-RAN and 5GC is underway by 3rd Generation Partnership Project (3GPP). Therefore, NG-RAN 135 and 5GC 140 may comply with 5G from 3GPP Current or future standards supported. The RAN 135 may be another type of RAN, for example, 3G RAN, 4G Long Term Evolution (LTE) RAN, etc. The communication system 100 may transmit data from satellite vehicles (SV) 190, 191, 192, 193 The information of the cluster 185 is used for satellite positioning systems (SPS) (eg, Global Navigation Satellite System (GNSS)), such as Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Galileo or BeiDou or some other local or Regional SPS, such as Indian Regional Navigation Satellite System (IRNSS), European Geostationary Navigation Overlay Service (EGNOS) or Wide Area Augmentation System (WAAS). Additional components of communication system 100 are described below. Communication system 100 may include additional or alternative part.

As shown in Figure 1, NG-RAN 135 includes NR Node Bs (gNBs) 110a, 110b and Next Generation eNode B (ng-eNB) 114, and 5GC 140 includes Access and Mobility Management Function (AMF) 115, communication Period Management Function (SMF) 117, Location Management Function (LMF) 120 and Gateway Operations Location Center (GMLC) 125. gNBs 110 a , 110 b and ng-eNB 114 are communicatively coupled to each other, each configured for two-way wireless communication with UE 105 , and each communicatively coupled to AMF 115 and configured for two-way communication with AMF 115 . AMF 115 , SMF 117 , LMF 120 , and GMLC 125 are communicatively coupled to each other, and the GMLC is communicatively coupled to an external client 130 . SMF 117 may act as the initial point of contact for a service control function (SCF) (not shown) to establish, control and delete media communication sessions.

Figure 1 provides a general illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated or omitted as desired. Specifically, although only one UE 105 is shown, many UEs (eg, hundreds, thousands, millions, etc.) may be utilized in the communications system 100 . Similarly, communication system 100 may include a greater (or lesser) number of SVs (ie, more or less than the four SVs 190-193 shown), gNBs 110a, 110b, ng-eNBs 114, AMFs 115 , external client 130 and/or other components. The connections shown connecting the various components in the communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and/or wireless connections and/or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and/or omitted depending on desired functions.

Although FIG. 1 shows a 5G-based network, similar network implementations and configurations may be used for other communication technologies, such as 3G, Long Term Evolution (LTE), and the like. Implementations described herein (whether for 5G technology and/or for one or more other communication technologies and/or protocols) can be used to send (or broadcast) directional synchronization signals, received at a UE (eg, UE 105) and/or provide location assistance to the UE 105 (via the GMLC 125 or other location server), and/or based on volume measurements received at the UE 105 for such directional signals, such as at the UE 105 , a location-capable device such as gNB 110a, 110b or LMF 120 calculates the location of UE 105 . Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (eNodeB) 114 and gNB (gNodeB) 110a , 110b are examples, and in various embodiments may be replaced by or include various other location server functions and/or base station functions, respectively.

A UE 105 may include and/or may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), secure user plane positioning (SUPL) enabled terminal (SET), or some other name. Additionally, UE 105 may correspond to cell phones, smartphones, laptops, tablets, PDAs, tracking devices, navigation devices, Internet of Things (IoT) devices, asset trackers, health monitors, security systems, smart city sensors, meter, smart watch, wearable tracker, or some other portable or removable device. Typically, though not necessarily, UE 105 can support wireless communications using one or more Radio Access Technologies (RATs), such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA ), LTE, High Speed Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi), Bluetooth® (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) (for example, using NG -RAN 135 and 5GC 140) etc. UE 105 may support wireless communication using a Wireless Local Area Network (WLAN), which may be connected to other networks (eg, the Internet) using, for example, Digital Subscriber Line (DSL) or packet cable. Use of one or more of these RATs may allow UE 105 to communicate with external clients 130 (e.g., via elements of 5GC 140 not shown in FIG. 1 , or possibly via GMLC 125), and/or allow external clients Peer 130 receives location information about UE 105 (eg, via GMLC 125).

UE 105 may comprise a single entity or may comprise multiple entities, such as in a personal area network, where a user may employ audio, video and/or data I/O (input/output) devices and/or body sensors and separate wired or wireless modem. Estimation of the location of the UE 105 may be referred to as a position fix, location estimate, location decision, decision, location decision, location estimate, or location decision, and may be geographical in scope, thereby providing location coordinates (e.g., latitude and longitude) of the UE 105 and longitude), which may or may not include an altitude component (eg, height above sea level, height above ground level, or depth below ground level, floor level, or basement level). Alternatively, the location of the UE 105 may be represented as a city location (eg, as a postal address or as a marker of a point or small area in a building, such as a specific room or floor). The location of the UE 105 may be expressed as an area or volume (defined in geographic or urban form) within which the UE 105 is expected to be located with a certain probability or confidence level (eg, 67%, 95%, etc.). The location of UE 105 may be expressed as a relative location, including, for example, distance and direction from known locations. A relative location may be expressed as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to some origin at a known location, for example, geographically, in municipal terms, or by reference For example, points, areas or volumes indicated on maps, floor plans or building plans. In the description contained herein, use of the term position may include any of these variations unless otherwise indicated. When computing the UE's position, it is common to solve for local x, y and possibly z coordinates, and then, if necessary, convert the local coordinates to absolute coordinates (e.g. latitude, longitude and altitude above or below mean sea level) .

UE 105 may be configured to communicate with other entities using one or more of a variety of techniques. The UE 105 may be configured to connect indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. The D2D P2P link may be supported by any suitable D2D radio access technology (RAT), such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and the like. One or more of a group of UEs utilizing D2D communication may be within the geographic coverage area of a transmission/reception point (TRP), such as one or more gNBs 110 a , 110 b and/or ng-eNB 114 . Other UEs in the group may be outside such geographic coverage areas, or may not otherwise be able to receive transmissions from the base station. A group of UEs communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE may transmit to other UEs in the group. TRP may help to schedule resources for D2D communication. In other cases, D2D communication can take place between UEs without involving TRP.

The base stations (BSs) in the NG-RAN 135 shown in Figure 1 include NR Node Bs, referred to as gNBs 110a and 110b. The paired gNBs 110a, 110b in the NG-RAN 135 may be interconnected via one or more other gNBs. providing access to the 5G network to the UE 105 via wireless communication between the UE 105 and one or more gNBs 110a, 110b, wherein the gNBs 110a, 110b may provide wireless communication access to the 5GC 140 on behalf of the UE 105 using 5G . In FIG. 1, it is assumed that the serving gNB of UE 105 is gNB 110a, although another gNB (e.g., gNB 110b) may act as a serving gNB if UE 105 moves to another location, or may act as a secondary gNB to provide UE 105 with additional throughput and bandwidth.

A base station (BS) in the NG-RAN 135 shown in FIG. 1 may include an ng-eNB 114, also known as a next-generation evolved Node B. The ng-eNB 114 may be connected to one or more gNBs 110a, 110b in the NG-RAN 135, possibly via one or more other gNBs and/or one or more other ng-eNBs. The ng-eNB 114 can provide LTE radio access and/or evolved LTE (eLTE) radio access to the UE 105 . One or more of gNBs 110a, 110b, and/or ng-eNB 114 may be configured to act as location-only beacons, which may transmit signals to assist in determining the location of UE 105, but may not receive signals from UE 105 or other UEs Signal.

Base stations, such as gNB 110a, gNB 110b, and ng-eNB 114, may each include one or more TRPs. For example, each sector within a cell of a BS may include a TRP, but multiple TRPs may share one or more components (eg, share a processor but have separate antennas). System 100 may include macro TRPs, or system 100 may have different types of TRPs, such as macro, pico, and/or femto TRPs, among others. A macro TRP may cover a relatively large geographic area (eg, several kilometers in radius) and may allow unrestricted access by terminals with service subscriptions. A pico TRP may cover a relatively small geographic area (eg, a pico cell) and may allow unrestricted access by terminals with service subscriptions. A femto or home TRP may cover a relatively small geographic area (eg, a femto cell) and may allow restricted access by terminals associated with the femto cell (eg, a terminal of a user in a home).

As noted, although FIG. 1 depicts nodes configured to communicate in accordance with the 5G protocol, nodes configured to communicate in accordance with other protocols may be used, such as, for example, the LTE protocol or the IEEE 802.11x protocol. For example, in an Evolved Packet System (EPS) that provides LTE radio access to UE 105, the RAN may include an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), which may include base stations, the Base stations include evolved Node Bs (eNBs). The core network of the EPS may include the Evolved Packet Core (EPC). The EPS may include E-UTRAN plus EPC, where E-UTRAN corresponds to NG-RAN 135 and EPC corresponds to 5GC 140 in FIG. 1 .

The gNBs 110a, 110b and ng-eNB 114 may communicate with the AMF 115, which communicates with the LMF 120 for positioning functions. AMF 115 may support UE 105 mobility, including cell change and handover, and may participate in supporting signaling connections to UE 105, and may support UE 105 data and voice bearers. LMF 120 may communicate directly with UE 105, eg, via wireless communication. LMF 120 may support positioning of UE 105 when UE 105 accesses NG-RAN 135 and may support positioning procedures/methods such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AOA), Angle of Departure (AOD) and/or other positioning methods. LMF 120 may handle location service requests for UE 105 received, eg, from AMF 115 or GMLC 125 . LMF 120 may be connected to AMF 115 and/or GMLC 125 . LMF 120 may be called other names such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF) or Value Added LMF (VLMF). Nodes/systems implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as Enhanced Service Action Location Center (E-SMLC) or Secure User Plane Location (SUPL) Location Platform (SLP). At least part of the positioning functionality, including deriving the location of the UE 105, may be performed at the UE 105 (e.g., using signal measurements obtained by the UE 105 for signals transmitted by wireless nodes such as gNB 110a, 110b and ng-eNB 114, and/or assistance data, such as provided by the LMF 120 to the UE 105).

GMLC 125 may support positioning requests for UE 105 received from external client 130, and may forward such positioning requests to AMF 115 for forwarding by AMF 115 to LMF 120, or may forward positioning requests directly to LMF 120. A location response (eg, containing a location estimate for UE 105 ) from LMF 120 may be returned to GMLC 125 directly or via AMF 115 , which may then return a location response (eg, containing a location estimate) to external client 130 . GMLC 125 is shown connected to AMF 115 and LMF 120, but in some implementations 5GC 140 may only support one of these connections.

As further shown in FIG. 1, LMF 120 may communicate with gNBs 110a, 110b and/or ng-eNB 114 using New Radio Location Protocol A (which may be referred to as NPPa or NRPPa), which may be described in the 3GPP Technical Specification (TS ) as defined in 38.455. NRPPa can be the same as, similar to or an extension of LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, NRPPa messages are communicated between gNB 110a (or gNB 110b) and LMF 120 via AMF 115 and/or at ng-eNB 114 and LMF 120 transfers. As further shown in Figure 1, LMF 120 and UE 105 may communicate using the LTE Positioning Protocol (LPP) defined in 3GPP TS 36.355. LMF 120 and UE 105 may also or instead communicate using New Radiolocation Protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of LPP. Here, LPP and/or NPP messages may be communicated between UE 105 and LMF 120 via AMF 115 and serving gNB 110a, 110b or serving ng-eNB 114 for UE 105 . For example, LPP and/or NPP messages may be communicated between LMF 120 and AMF 115 using the 5G Location Services Application Protocol (LCS AP), and may be communicated between AMF 115 and UE 105 using the 5G Non-Access Stratum (NAS) protocol . LPP and/or NPP protocols may be used to support positioning of the UE 105 using UE-assisted and/or UE-based positioning methods such as A-GNSS, RTK, OTDOA, and/or E-CID. The NRPPa protocol can be used to support positioning of UE 105 using network-based positioning methods, such as E-CID (e.g., when used with measurements obtained by gNB 110a, 110b or ng-eNB 114), and/or can be used by LMF 120 is used to obtain location related information from gNB 110a, 110b and/or ng-eNB 114, such as parameters defining directed SS transmissions from gNB 110a, 110b and/or ng-eNB 114.

Using UE-assisted positioning methods, the UE 105 can obtain location measurements and send the measurements to a network entity, such as a base station or a location server (eg, LMF 120 ), for computing a location estimate for the UE 105 . For example, location measurements may include Received Signal Strength Indication (RSSI), Round Trip Signal Travel Time (RTT), Reference Signal Time Difference (RSTD), Reference Signal Received One or more of Power (RSRP) and/or Reference Signal Received Quality (RSRQ). Position measurements may also or alternatively include GNSS pseudorange, code phase and/or carrier phase measurements of SVs 190-193.

With UE-based positioning methods, the UE 105 can obtain location measurements (e.g., which can be the same or similar to those of the UE-assisted positioning method), and can calculate the location of the UE 105 (e.g., by means of (Auxiliary data received by network entities such as LMF 120) or broadcast by gNB 110a, 110b, ng-eNB 114 or other base stations or APs).

Using network-based positioning methods, one or more base stations (e.g., gNB 110a, 110b and/or ng-eNB 114) or APs can obtain location measurements (e.g., RSSI, RTT, Measurements of RSRP, RSRQ, or Time of Arrival (TOA)) and/or measurements obtained by UE 105 may be received. One or more base stations or APs may send measurements to a network entity, such as a location server (eg, LMF 120 ), for computing a location estimate for UE 105 .

The information provided by gNB 110a, 110b and/or ng-eNB 114 to LMF 120 using NRPPa may include timing and configuration information and location coordinates for directional SS transmissions. LMF 120 may provide some or all of this information to UE 105 via NG-RAN 135 and 5GC 140 in LPP and/or NPP messages as auxiliary data.

Depending on the desired functionality, an LPP or NPP message sent from a network entity such as LMF 120 to UE 105 may instruct UE 105 to do any of a variety of things. For example, an LPP or NPP message may include instructions for the UE 105 to obtain measurements of GNSS (or A-GNSS), WLAN, E-CID, and/or OTDOA (or some other positioning method). In the case of E-CID, the LPP or NPP message may instruct UE 105 to obtain support from one or more of gNB 110a, 110b and/or ng-eNB 114 (or by some other type of base such as eNB or WiFi AP One or more quantity measurements (eg, beam ID, beam width, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a particular cell supported by a station). UE 105 may send volume measurements back to LMF 120 via serving gNB 110a (or serving ng-eNB 114 ) and AMF 115 in an LPP or NPP message (eg, within a 5G NAS message).

As mentioned, although the communication system 100 is described with respect to 5G technology, the communication system 100 can be implemented to support other communication technologies, such as GSM, WCDMA, LTE, etc., for supporting and interacting with mobile devices such as UE 105 (for example, to implement voice, data, location and other functions). In some such embodiments, 5GC 140 may be configured to control various air interfaces. For example, the 5GC 140 may connect to the WLAN using a non-3GPP interworking function (N3IWF, not shown in FIG. 1 ) in the 5GC 150 . For example, a WLAN may support IEEE 802.11 WiFi access for UE 105 and may include one or more WiFi APs. Here, the N3IWF may connect to the WLAN and other elements in the 5GC 140 , such as the AMF 115 . In some embodiments, both NG-RAN 135 and 5GC 140 may be replaced by one or more other RANs and one or more other core networks. For example, in EPS, NG-RAN 135 can be replaced by E-UTRAN including eNB, and 5GC 140 can be replaced by EPC, EPC contains Mobility Management Entity (MME) instead of AMF 115, E-SMLC instead of LMF 120, And a GMLC that can be similar to GMLC 125. In such EPS, E-SMLC can use LPPa instead of NRPPa to send and receive location information to and from eNB in E-UTRAN, and can use LPP to support UE 105 positioning. In these other embodiments, positioning of UE 105 using directional PRS may be supported in a manner similar to that described here for 5G networks, except here for gNB 110a, 110b, ng-eNB 114, AMF 115 The functions and procedures described with LMF 120 may in some cases be applied instead to other network elements, such as eNBs, WiFi APs, MMEs and E-SMLCs.

As noted, in some embodiments, positioning functionality may be implemented at least in part using directional SS beams transmitted by base stations (such as gNB 110a, 110b and/or ng-eNB 114) that are to determine their The location is within range of the UE (eg, UE 105 of FIG. 1 ). In some cases, the UE may use directional SS beams from a plurality of base stations (such as gNB 110a, 110b, ng-eNB 114, etc.) to calculate the UE's position.

Referring also to FIG. 2, UE 200 is an example of UE 105 and includes a computing platform including a processor 210, memory 211 including software (SW) 212, one or more sensors 213, for transceiver 215 (including wireless transceiver 240 and/or wired transceiver 250 ), user interface 214 , satellite positioning system (SPS) receiver 217 , camera 218 and location (motion) device 219 . Processor 210, memory 211, sensor(s) 213, transceiver interface 214, user interface 216, SPS receiver 217, camera 218, and position (motion) device 219 may be connected via bus 220 (which may configured for eg optical and/or electrical communication) are communicatively coupled to each other. One or more of the illustrated processor-readable instruction devices (eg, camera 218 , position (motion) device 219 , and/or one or more sensors 213 , etc.) may be omitted from UE 200 . The processor 210 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), and the like. The processor 210 may include multiple processors, including a general purpose/application processor 230 , a digital signal processor (DSP) 231 , a modem processor 232 , a video processor 233 and/or a sensor processor 234 . One or more of processors 230-234 may include multiple devices (eg, multiple processors). The modem processor 232 can support dual SIM/dual connectivity (or even more SIMs). For example, a SIM (Subscriber Identity Module or Subscriber Identity Module) may be used by an original equipment manufacturer (OEM), while another SIM may be used by an end user of the UE 200 for the connection. The memory 211 is a non-transitory storage medium, which may include random access memory (RAM), flash memory, optical disk memory, and/or read only memory (ROM). The memory 211 stores software 212, which may be processor-readable and processor-executable software code, comprising instructions configured to cause the processor 210 to perform various functions described herein when executed. Alternatively, the software 212 may not be directly executed by the processor 210, but may be configured such that the processor 210, for example, when compiled and executed, performs the functions. The description may refer to processor 210 performing a function, but this includes other implementations, such as processor 210 executing software and/or firmware. The description may refer to processor 210 performing a function as shorthand for one or more processors 230-234 performing that function. This description may refer to UE 200 performing a function as shorthand for one or more appropriate components of UE 200 performing that function. In addition to and/or instead of memory 211 , processor 210 may include a memory having stored instructions. The functionality of processor 210 will be discussed more fully below.

The configuration of UE 200 shown in FIG. 2 is an example of the present disclosure including claims and not limitation, and other configurations may be used. For example, an example configuration of a UE includes one or more processors 230 - 234 of processor 210 , memory 211 and wireless transceiver 240 . Other example configurations include one or more processors 230-234 of processor 210, memory 211, wireless transceiver 240, and sensor(s) 213, user interface 216, SPS receiver 217, camera 218, One or more of PMD 219 and/or wired transceiver 250 .

UE 200 may include a modem processor 232 capable of performing baseband processing on signals received and down-converted by transceiver 215 and/or SPS receiver 217 . The modem processor 232 may perform baseband processing on the signal to be upconverted for transmission by the transceiver 215 . Additionally or alternatively, baseband processing may be performed by general purpose processor 230 and/or DSP 231 . However, other configurations may be used to perform baseband processing.

UE 200 may include sensor(s) 213 which may include, for example, an inertial measurement unit (IMU) 270, one or more magnetometers 271, and/or one or more environmental sensing device 272. IMU 270 may include one or more inertial sensors, eg, one or more accelerometers 273 (eg, collectively responsive to three-dimensional acceleration of UE 200 ) and/or one or more gyroscopes 274 . The magnetometer(s) may provide measurements to determine an orientation (eg, relative to magnetic north and/or true north), which may be used for any of a variety of purposes, eg, to support one or more compass applications. Environmental sensor(s) 272 may include, for example, one or more temperature sensors, one or more barometric pressure sensors, one or more ambient light sensors, one or more camera imagers, and/or One or more microphones, etc. Sensor(s) 213 may generate analog and/or digital signals, indications of which may be stored in memory 211 and processed by DSP 231 and/or general purpose processor 230 to support one or more applications, such as, For example, applications for positioning and/or navigation operations.

The sensor(s) 213 may be used for relative position measurement, relative position determination, motion determination, and the like. Information detected by the sensors 213 may be used for motion detection, relative displacement, dead reckoning, sensor-based position determination, and/or sensor-assisted position determination. The sensor(s) 213 may be used to decide whether the UE 200 is stationary (stationary) or mobile, and/or whether to report some useful information about the mobility of the UE 200 to the LMF 120 . For example, based on the information obtained/measured by the sensor(s) 213, the UE 200 may notify/report to the LMF 120 that the UE 200 has detected movement or that the UE 200 has moved, and report the relative displacement/distance (e.g., via dead reckoning, or sensor based position determination, or sensor assisted position determination enabled by sensor(s) 213 ). In another example, for relative positioning information, the sensor/IMU can be used to determine the angle and/or orientation of another device relative to the UE 200 , etc.

The IMU 270 may be configured to provide measurements regarding the direction of motion and/or speed of motion of the UE 200, which may be used for relative position determination. For example, one or more accelerometers 273 and/or one or more gyroscopes 274 of the IMU 270 can detect the linear acceleration and rotational velocity of the UE 200, respectively. The linear acceleration and rotational velocity measurements of UE 200 can be integrated over time to determine the transient motion direction and displacement of UE 200 . The transient motion direction and displacement can be integrated to track the UE 200 position. For example, a reference position of UE 200 may be determined, such as using SPS receiver 217 (and/or by some other means) at a certain moment, and after that moment from accelerometer(s) 273 and gyro(s) Measurements obtained by meter 274 may be used in dead reckoning to determine the current location of UE 200 based on the movement (direction and distance) of UE 200 relative to a reference location.

The magnetometer(s) 271 can determine magnetic field strengths in different directions, which can be used to determine the orientation of the UE 200 . For example, the bearing can be used to provide the UE 200 with a digital compass. Magnetometer(s) 271 may include a two-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in two orthogonal dimensions. Additionally or alternatively, magnetometer 271 may comprise a three-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in three orthogonal dimensions. Magnetometer(s) 271 may provide means for sensing a magnetic field and providing an indication of the magnetic field to, eg, processor 210 .

Transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 240 may include a transmitter 242 and a receiver 244 coupled to one or more antennas 246 for transmitting (e.g., on one or more uplink channels and/or one or more sidelink channel) and/or receive (e.g., on one or more downlink channels and/or one or more sidelink channels) wireless signals 248, and convert signals from wireless signals 248 to wired (e.g., electrical and/or optical) signals, and convert 248 from wired (eg, electrical and/or optical) signals to wireless signals. Accordingly, transmitter 242 may comprise multiple transmitters which may be individual components or combined/integrated components, and/or receiver 244 may comprise multiple receivers which may be individual components or combined/integrated components. Integrated components. The wireless transceiver 240 may be configured to transmit signals (eg, utilizing TRP and/or one or more other devices) according to various radio access technologies (RATs), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), ), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Phone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE Vehicle to Everything (V2X) (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, WiFi Direct (WiFi-D), Bluetooth®, Zigbee, etc. New radios may use millimeter wave frequencies and/or frequencies below 6 GHz. The wired transceiver 250 may include a transmitter 252 and a receiver 254 configured for wired communication, eg, with the network 135, eg, to send communications to and receive communications from the gNB 110a. Transmitter 252 may include multiple transmitters, which may be individual components or combined/integrated components, and/or receiver 254 may include multiple receivers, which may be individual components or combined/integrated components . Wired transceiver 250 may be configured for optical communication and/or electrical communication, for example. Transceiver 215 may be communicatively coupled to transceiver interface 214, eg, by optical and/or electrical connections. The transceiver interface 214 may be at least partially integrated with the transceiver 215 .

User interface 216 may include one or more of several devices such as, for example, speakers, microphones, display devices, vibration devices, keyboards, touch screens, and the like. User interface 216 may include more than one device of any of these devices. User interface 216 may be configured to enable a user to interact with one or more applications hosted by UE 200 . For example, the user interface 216 may store analog and/or digital signal indications in the memory 211 for processing by the DSP 231 and/or the general processor 230 in response to user actions. Similarly, an application hosted on UE 200 may store indications of analog and/or digital signals in memory 211 for presenting output signals to the user. User interface 216 may include audio input/output (I/O) devices including, for example, speakers, microphones, digital analog circuits, analog digital circuits, amplifiers, and/or gain control circuits (including any of these devices) more than one device). Other configurations of audio I/O devices may be used. Additionally or alternatively, the user interface 216 may include one or more touch sensors to respond to touch and/or pressure on, for example, the keypad and/or touch screen of the user interface 216 .

SPS receiver 217 (eg, a global positioning system (GPS) receiver) is capable of receiving and acquiring SPS signals 260 via SPS antenna 262 . Antenna 262 is configured to convert wireless SPS signal 260 into a wired signal, such as an electrical or optical signal, and may be integrated with antenna 246 . The SPS receiver 217 may be configured to process the acquired SPS signal 260 in whole or in part for estimating the position of the UE 200 . For example, the SPS receiver 217 may be configured to determine the location of the UE 200 by using trilateration of the SPS signal 260 . The general-purpose processor 230, the memory 211, the DSP 231, and/or one or more special-purpose processors (not shown) may be used to process all or part of the acquired SPS signals, and/or in conjunction with the SPS receiver 217 to calculate the UE 200 the estimated location of . The memory 211 may store indications (eg, measurements) of the SPS signal 260 and/or other signals (eg, signals obtained from the wireless transceiver 240 ) for use in performing positioning operations. The general purpose processor 230 , DSP 231 and/or one or more special purpose processors and/or memory 211 may provide or support a positioning engine for processing measurements to estimate the position of the UE 200 .

UE 200 may include a camera 218 for capturing still or moving images. The camera 218 may include, for example, an imaging sensor (eg, a charge-coupled device or CMOS imager), a lens, analog-to-digital circuitry, a frame buffer, and the like. Additional processing, conditioning, encoding and/or compression of signals representing captured images may be performed by general purpose processor 230 and/or DSP 231 . Additionally or alternatively, video processor 233 may perform conditioning, encoding, compression, and/or manipulation on signals representing captured images. The video processor 233 can decode/decompress the stored image data for presentation on a display device (not shown) such as the user interface 216 .

A position (motion) device (PMD) 219 may be configured to determine the location and possible motion of the UE 200 . For example, PMD 219 may communicate with and/or include some or all of SPS receiver 217 . PMD 219 may also or alternatively be configured to use ground-based signals for trilateration (e.g., at least some of signals 248) to determine the location of UE 200, to assist in obtaining and using SPS signals 260, or both Both. PMD 219 may be configured to determine the location of UE 200 using one or more other techniques (e.g., relying on UE self-reported location (e.g., part of a UE location beacon)), and may use a combination of techniques (e.g., SPS and ground positioning signals) to determine the location of UE 200. The PMD 219 may include one or more sensors 213 (eg, gyroscope(s), accelerometer(s), magnetometer(s), etc.), which may sense the orientation and/or motion of the UE 200, And provide an indication that the processor 210 (eg, the general purpose processor 230 and/or the DSP 231 ) may be configured to determine the motion (eg, the velocity vector and/or the acceleration vector) of the UE 200 . PMD 219 may be configured to provide an indication of uncertainty and/or error in the determined position and/or motion. In an example, PMD 219 may be referred to as a Positioning Engine (PE), and may be executed by a general purpose processor 230 . For example, PMD 219 may be a logical entity and may be integrated with general purpose processor 230 and memory 211 .

Referring also to FIG. 3 , an example of a TRP 300 for gNB 110a, gNB 110b, and ng-eNB 114 includes a computing platform that includes a processor 310, memory 311 including software (SW) 312, a transceiver 315, and (optionally ground) SPS receiver 317. Processor 310, memory 311, transceiver 315, and SPS receiver 317 may be communicatively coupled to each other by bus 320 (which may be configured for, eg, optical and/or electrical communication). One or more of the devices shown (eg, wireless interface and/or SPS receiver 317 ) may be omitted from TRP 300 . SPS receiver 317 may be configured similarly to SPS receiver 217 to be capable of receiving and acquiring SPS signal 360 via SPS antenna 362 . The processor 310 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), and the like. The processor 310 may include multiple processors (eg, including a general purpose/application processor, a DSP, a modem processor, a video processor, and/or a sensor processor, as shown in FIG. 2 ). The memory 311 is a non-transitory storage medium, which may include random access memory (RAM), flash memory, optical disk memory, and/or read only memory (ROM). The memory 311 stores software 312, which may be processor-readable and processor-executable software code comprising instructions configured to cause the processor 310 to perform various functions described herein when executed. Alternatively, the software 312 may not be directly executed by the processor 310, but may be configured such that the processor 310, for example, when compiled and executed, performs the functions. The description may refer to processor 310 performing a function, but this includes other implementations, such as processor 310 executing software and/or firmware. The description may use the processor performing a function 310 as shorthand for one or more processors included in the processor performing the function 310 . The description may refer to TRP 300 performing a function as shorthand for one or more appropriate components of TRP 300 (and thus one of gNB 110a, gNB 110b, ng-eNB 114) performing that function. In addition to and/or instead of memory 311 , processor 310 may include memory with stored instructions. The functionality of processor 310 will be discussed more fully below.

Transceiver 315 may include a wireless transceiver 340 and a wired transceiver 350 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 340 may include a transmitter 342 and a receiver 344 coupled to one or more antennas 346 for transmitting (e.g., on one or more uplink channels, downlink channels, and/or sidechain road channel) and/or receive (e.g., on one or more downlink channels, uplink channels, and/or sidelink channels) wireless signals 348, and convert signals from wireless signals 348 to wired (e.g., , electrical and/or optical) signals, and convert 348 from wired (eg, electrical and/or optical) signals to wireless signals. Accordingly, transmitter 342 may comprise multiple transmitters which may be individual components or combined/integrated components, and/or receiver 344 may comprise multiple receivers which may be individual components or combined/integrated components. Integrated components. Wireless transceiver 340 may be configured to transmit signals (eg, with UE 200, one or more other UEs, and/or one or more other devices) according to various radio access technologies (RATs), such as 5G New Radio (NRAT) ), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Phone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct Connect (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, WiFi Direct (WiFi-D), Bluetooth®, Zigbee, etc. Wired transceiver 350 may include a transmitter 352 and a receiver 354 configured for wired communication, such as with network 140 , to send and receive communications to and from LMF 120 , for example. Transmitter 352 may include multiple transmitters, which may be individual components or combined/integrated components, and/or receiver 354 may include multiple receivers, which may be individual components or combined/integrated components . Wired transceiver 350 may be configured for optical communication and/or electrical communication, for example.

The configuration of TRP 300 shown in FIG. 3 is an example and not limiting of the present disclosure including claim items, and other configurations may be used. For example, the description herein discusses that TRP 300 is configured to perform several functions, but one or more of these functions may be performed by LMF 120 and/or UE 200 (i.e., LMF 120 and/or UE 200 may be configured to perform one or more of these functions).

Referring also to FIG. 4 , the server 400 , exemplified by the LMF 120 , includes a computing platform including a processor 410 , a memory 411 including software (SW) 412 , and a transceiver 415 . Processor 410, memory 411, and transceiver 415 may be communicatively coupled to each other by bus 420 (which may be configured for, eg, optical and/or electrical communication). One or more of the devices shown (eg, the wireless interface) may be omitted from server 400 . The processor 410 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), and the like. The processor 410 may include multiple processors (eg, including a general purpose/application processor, a DSP, a modem processor, a video processor, and/or a sensor processor, as shown in FIG. 2 ). The memory 411 is a non-transitory storage medium, which may include random access memory (RAM), flash memory, optical disk memory, and/or read only memory (ROM). The memory 411 stores software 412 which may be processor-readable and processor-executable software code comprising instructions configured to cause the processor 410 to perform various functions described herein when executed. Alternatively, the software 412 may not be directly executed by the processor 410, but may be configured such that the processor 410 performs the functions, for example when compiled and executed. The description may refer to processor 410 performing a function, but this includes other implementations, such as processor 410 executing software and/or firmware. The description may use the processor performing a function 410 as shorthand for one or more processors included in the processor performing the function 410 . This description may refer to server 400 (or LMF 120 ) performing a function as shorthand for one or more appropriate components of server 400 (eg, LMF 120 ) performing that function. In addition to and/or instead of memory 411 , processor 410 may include memory with stored instructions. The functionality of processor 410 will be discussed more fully below.

Transceiver 415 may include a wireless transceiver 440 and a wired transceiver 450 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 440 may include a transmitter 442 and a receiver 444 coupled to one or more antennas 446 for transmitting (e.g., on one or more downlink channels) and/or receiving (e.g., on on one or more uplink channels) wireless signals 448, and convert signals from wireless signals 448 to wired (e.g., electrical and/or optical) signals, and from wired (e.g., electrical and/or optical) signals to Wireless signal 448. Accordingly, transmitter 442 may comprise multiple transmitters, which may be separate components or combined/integrated components, and/or receiver 444 may comprise multiple receivers, which may be separate components or combined/integrated components. Integrated components. Wireless transceiver 440 may be configured to transmit signals (eg, with UE 200, one or more other UEs, and/or one or more other devices) according to various radio access technologies (RATs), such as 5G New Radio (NRAT) ), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Phone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct Connect (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, WiFi Direct (WiFi-D), Bluetooth®, Zigbee, etc. Wired transceiver 450 may include a transmitter 452 and a receiver 454 configured for wired communication, such as with network 135 , to send and receive communications to and from TRP 300 , for example. Transmitter 452 may include multiple transmitters, which may be individual components or combined/integrated components, and/or receiver 454 may include multiple receivers, which may be individual components or combined/integrated components . Wired transceiver 450 may be configured for optical communication and/or electrical communication, for example.

The configuration of server 400 shown in FIG. 4 is an example and not limiting of the present disclosure including request items, and other configurations may be used. For example, wireless transceiver 440 may be omitted. Also or alternatively, the description herein discusses that server 400 is configured to perform several functions, but one or more of these functions may be performed by TRP 300 and/or UE 200 (i.e., TRP 300 and/or UE 200 may be configured to perform one or more of these functions).

的偽距量測

可以被模型化為：

（1） 其中

是衛星-

和使用者位置之間的真實距離。

是使用者設備中的共同偏差。

是衛星-

的衛星時鐘偏差，包括頻率 f ₁上的任何衛星群延遲。 c是光速。 B ₁是在頻率 f ₁上進行量測時使用者設備中共同的附加偏差。

是電離層延遲，影響頻率 f ₁上來自衛星-

的信號。

是對流層引入來自衛星-

的信號的延遲，與頻率無關。

是考慮噪音和任何未模型化的影響。 Referring to FIG. 5 , a schematic diagram of an example GNSS receiver 500 is illustrated. The SPS receivers 217 , 317 in the UE 200 and TRP 300 may include one or more components of the GNSS receiver 500 and thus may be instances of the GNSS receiver 500 . In an example, the GNSS receiver 500 includes, but is not limited to, an antenna 501 , an analog part 502 , a digital part 503 and a processor 504 . Antennas 262 , 362 on UE 200 and TRP 300 are examples of antenna 501 . GNSS satellite signals are received by antenna 501 and coupled to the input of analog section 502 . The analog section 502 is configured to process GNSS satellite signals and generate digital intermediate frequency (IF) signals by sampling the GNSS satellite signals with an analog-to-digital converter (ADC). In one embodiment, the sampling rate may be approximately 83 megasamples per second (Ms/s). The digital IF signal is coupled to an input of digital section 503 . The digital section 503 is configured to acquire and track satellites from within the constellation of GNSS satellites using digital IF signals by generating acquisition and tracking data coupled to the processor 504 . The digital portion 503 may be configured to implement one or more notch filters based on the presence of narrow-band jamming signals in the GNSS spectrum. In an example, the digital section 503 may configure the one or more notch filters as one or more digital filters with programmable center frequencies and bandwidths. Processor 504 may be a central processing unit CPU, a microprocessor, a digital signal processor, or any other such device that can read and execute programmed instructions. Processor 504 is configured to analyze acquisition and tracking data to determine navigational information, such as position and velocity. The SV may transmit signals on a plurality of frequencies, and the processor 504 may be configured to determine pseudorange and carrier phase measurements based on GNSS models known in the art. For example, typically, frequency f ₁ up to the satellite

pseudorange measurement

can be modeled as:

(1) of which

is a satellite -

The real distance from the user's location.

is a common deviation in user equipment.

is a satellite -

The satellite clock bias of , including any constellation delay at frequency f ₁ . c is the speed of light. B ₁ is the common additional deviation in the UE when the measurement is performed at frequency f ₁ .

is the ionospheric delay, affecting frequency f ₁ from the satellite -

signal of.

is the tropospheric introduction from the satellite-

The delay of the signal is independent of the frequency.

is to account for noise and any unmodeled effects.

Other GNSS models and variables can also be used to determine the distance to SV.

Referring to FIG. 6A , a diagram 600 of an example GNSS spectrum 602 is illustrated. In operation, a radio carrier can be modulated in various ways. For example, a GPS system can utilize three different frequency bands (eg, L1, L2, and L5) and utilize phase modulation to deliver codes from the SV to the receiver. GPS signals can utilize spread spectrum, making the overall bandwidth of the GPS signal much wider than the bandwidth of the information it carries. Specifically, L1 is centered at 1575.42 MHz, L2 is centered at 1227.60 MHz, and L5 is centered at 1176.45 MHz, and the width of the GPS signal on these frequencies is wider than expected. For example, on L1, the CA code signal spreads over a width of about 2.046 MHz, and the P(Y) code signal spreads over a width of about 20.46 MHz. Spectrum 602 depicts approximately 2 MHz (ie, +/- 1 MHz) around the Doppler frequency of the SV. A digital front end (DFE) (eg, digital section 503 ) of a GNSS receiver is configured to perform an autocorrelation process on the received signal in frequency spectrum 602 to obtain code phase measurements. Local interference caused by other transmitters or oscillators (eg harmonic signals) can significantly affect or impair the autocorrelation process. GNSS receivers can be configured to implement one or more notch filters to reduce the effects of interference. For example, a +0.5 MHz notch filter on spectrum 602 will reduce the received power in spectrum 602 as depicted by signal dip 604 . The notch filter and corresponding signal drop 604 may affect the received autocorrelation function and corresponding code phase measurement. For example, referring to FIG. 6B , there is illustrated a graph 610 comparing an example autocorrelation function (ACF) with and without a notch filter. Typical ACF 612 provides relatively higher amplitude peaks compared to notch filtered ACF 614 . Distortion of the overall ACF shape, and in some cases loss of amplitude in the ACF due to one or more notch filters, may reduce the accuracy of GNSS position calculations. That is, distortion of the ACF shape may cause peaks to be detected in the wrong code phase, which may lead to measurement bias. Therefore, since the accuracy of a GNSS position estimate is partly based on the accuracy of its measured code phase, the use of a notch filter will also affect the position accuracy. The degree of positioning error (ie, code phase impact) depends on the PRN code, SV Doppler, notch frequency and notch bandwidth. For example, referring to FIG. 6C , a graph 620 of code phase error values 622 based on example notch filter frequencies is illustrated. Graph 620 depicts the code phase of the SV (i.e., SV ID 5) as the notch filter frequency varies from -1 MHz to +1 MHz around the SV Doppler frequency (i.e., zero in FIG. 6C ) Error in centimeters. Each error value 622 is based on a 100 kilohertz step from -1 MHz to +1 MHz. Example error values 622 vary from about -50 centimeters to +25 centimeters. Other SVs (eg, PRN codes), SV Doppler values, and notch bandwidths (which may include multiple notch filters) may have different error distance values and different error value distributions.

Referring to FIG. 7 , with further reference to FIGS. 5 and 6A-6C , there is illustrated a block diagram of an example process 700 for off-line phase compensation based on notch filter configurations. Process 700 utilizes one or more offline look-up tables (LUTs) 702 to apply code phase correction based on notch filter configuration 704 and SV PRN and Doppler frequency information 706 at stage 710 . Typically, the code phase correction value in LUT 702 depends on three parameters: SVID (e.g., SV PRN), SV Doppler frequency, and notch configuration information (i.e., number of notches, frequency per notch, and frequency per notch). notch bandwidth). In an example, for each notch configuration, a two-dimensional array of LUTs can be calculated and stored. Different LUTs for different notch combinations can also be utilized, and each LUT can be a two-dimensional array such that the { i , j }th element will be the Doppler corresponding to the i -th SVID and the j -th SV (where SVID is a finite number) of code phase correction values. Different notch filter configurations 704 and SV Doppler resolution in the LUT grid can be selected based on operational requirements. For example, in a bandwidth of 2 MHz, the SV Doppler can be varied in steps of 1 kHz to provide 2001 grid points, or in steps of 100 kHz to provide 21 grid points. The size of the corresponding LUT can thus be multiplied.

In an embodiment, processor 504 may be configured to access local memory module(s) including one or more LUTs 702 that store data based on PRN code, notch frequency, notch bandwidth, and SV Code phase error value of Doppler information. For example, notch filter configuration 704 may indicate a notch frequency (eg, +/- 1 megahertz from the SV Doppler value) and notch bandwidth (eg, 1, 2, 5, 10 kilohertz, etc.). The SV PRN and Doppler frequency information 706 is associated with the SV transmitting the signal that the GNSS receiver 500 is receiving. LUT 702 includes error measurement data points as depicted in Figure 6C. The code phase correction decision at stage 708 may be based on selection, sorting and/or matching functions or algorithms or other stored procedures executed on processor 504 to base notch filter configuration 704 and SV PRN and Doppler frequency information 706 selects a code phase error value from LUT 702 . The code phase correction value may be a distance (e.g., 1 cm, 5 cm, 10 cm, 100 cm, etc.), and the processor 504 is configured to apply the correction to the distance measurement (e.g., pseudorange, carrier phase measurement). Offline LUT 702 offers the advantage of relatively fast code phase error resolution at the cost of memory usage, since different changes in notch filter configuration and SV information must be stored. Some memory efficiency can be gained by increasing the quantization of the values in the LUT 702 and using an interpolation routine to estimate the code phase error.

Referring to FIG. 8, an example process 800 for calculating code phase correction values is illustrated. Based on the notch filter configuration 704 and the SV PRN and Doppler frequency information 706 (i.e., SVID 706a and SV Doppler 706b) that the GNSS receiver 500 is receiving, smoothing between values in the LUT 702 interpolated to calculate the code phase correction. In general, code phase values in LUT 702 are known at finite and discrete points in two-dimensional space, and interpolation functions can be used to compute values at other arbitrary points in that space. For example, at stage 802, the processor 504 may be configured to receive an input from the digital portion 503 associated with the received SV signal. Inputs may include SVID 706a , SV Doppler 706b , and notch configuration 704 . The processor 504 is configured to obtain the nearest "k" neighbors of the input value in the LUT 702, and then at stage 804 calculate a weighted average "y" of the code phase errors for each neighbor. At stage 806, the weighted average "y" may be used as the code phase correction value. Process 800 is an example, not a limitation, as other multivariate interpolation techniques can also be used to determine the final code phase correction value.

Referring to FIG. 9 , an example process 900 for in-line phase calculation based on a notch filter configuration is illustrated. In contrast to the offline process 700 in FIG. 7 which depends on the LUT 702, the online process 900 locally calculates LUT values when the configuration of the GNSS receiver 500 changes (eg, when a new interference signal is detected). For example, processor 504 may receive notch filter configuration information 902 and SV PRN and Doppler frequency information 904 from digital portion 503 as previously described. At stage 906, the processor 504 may calculate a LUT table value for the SV via a simulation with discrete points as described in FIGS. 6A-6C. At stage 908 , the processor 504 may use the notch filter configuration information 902 and the SV PRN and Doppler frequency information 904 and an interpolation technique such as that described in FIG. 8 to obtain a code phase correction value based on the locally generated LUT. At stage 910, the processor 504 may apply a code phase correction to a range measure (eg, pseudorange, carrier phase measure) calculated for the received SV signal.

Referring to FIGS. 10A-10D , example graphs of code phase error for a plurality of satellite vehicles and notch filter configurations are illustrated. These graphs are examples and are provided to illustrate that different SV PRNs may have different notch frequency error distributions. The depicted error values represent discrete values in the LUT, which can be generated offline (as in process 700 ) or online (as in process 900 ). The error values plotted represent the notch frequency in 100 kHz steps between -1 MHz and +1 MHz relative to the SV Doppler frequency (eg, zero Doppler in the graph). By way of example and not limitation, typical code phase correction values for GPS L1 CA signals are between +1 meter and -1 meter. Other signal types may have different ranges of correction values. FIG. 10A depicts a first example SV (SV: 14) with a first error distribution between -60 centimeters and +30 centimeters. FIG. 10B depicts a second example SV (SV: 25) with a second error distribution between -90 centimeters and +10 centimeters. FIG. 10C depicts a third example SV (SV: 17) with a third error distribution between -60 centimeters and +30 centimeters. Figure 10D depicts a fourth example SV (SV: 08) with a fourth error distribution between -70 centimeters and +20 centimeters. SVs, graphs, and sample sizes (eg, notch filter step values) are examples and not limitations. Other simulations can be run with other SVs and larger or smaller notch filter step sizes.

Referring to FIG. 11 , with further reference to FIGS. 1-10D , a method 1100 for calculating a distance to a satellite vehicle includes the stages shown. However, method 1100 is an example and not a limitation. Method 1100 may be changed, for example, by adding, removing, rearranging, combining, executing stages concurrently, and/or breaking a single stage into multiple stages.

At stage 1102, the method includes receiving a signal from a satellite vehicle. The analog portion 502 of the GNSS receiver 500 is a means for receiving signals from the SV. Generally, GNSS SV transmits navigation signals on two or more frequencies in the L-band. These signals contain ranging codes and navigation data to allow the GNSS receiver 500 to calculate the travel time from the satellite to the receiver and the satellite coordinates for any epoch. The signal may include a carrier, ranging code (e.g., SVID, PRN sequence, or PRN code), and other navigation data (e.g., information about SV ephemeris, clock bias parameters, almanac information, SV information, and other associated navigation information).

At stage 1104, the method includes determining one or more notch filter configurations. The digital section 503 and the processor 504 are components used to determine one or more notch filter configurations. Notch filters can be based on the presence of narrowband interfering signals generated locally or by external RF sources. In an example, one or more interfering signals may be known based on the state of the UE (ie, when the Wi-Fi or Bluetooth transmitter is on). In an embodiment, the processor 504 may be configured to perform spectral analysis to find interfering signals. The notch filter configuration may include frequency components and bandwidth components to mitigate interference from one or more interfering signals. In an embodiment, the notch filter configuration may include a plurality of frequencies, each notch filter having the same or a different bandwidth.

At stage 1106, the method includes determining a pseudorandom noise code and a Doppler frequency associated with the signal. Processor 504 is the means for determining the PRN code and Doppler frequency. The PRN code is included in the signal received at stage 1102 . The Doppler frequency corresponds to the Doppler shift of the received signal based primarily on the relative velocity between the antenna on the SV and the GNSS receiver. Other clock frequency error offsets can also be included in the Doppler frequency. In general, the Doppler shift of a signal is the time derivative of the carrier phase.

At stage 1108, the method includes determining a code phase correction value based at least on one or more notch filter configurations, a pseudorandom noise code, and a Doppler frequency. The processor 504 is a means for determining a code phase correction value. In operation, processor 504 may utilize one or more LUTs including notch filter configuration information, SV PRN and Doppler frequency information, and associated code phase correction values. For example, query tools such as sort, select, match, etc. can be used to determine code phase correction values based on notch filter and SV configuration information. LUTs may be provided to the UE via assistance data (ie, an offline solution) and/or one or more LUTs may be generated locally on the UE (ie, an online solution). In the offline solution, the communication network 100 can provide the auxiliary data to the UE via the wireless transceiver 240 with LUT. Assistance data can be sent via network protocols, such as LPP and Radio Resource Control (RRC) messaging. Other messaging, such as sidelink techniques, can also be used to propagate the LUT to other UEs in the network. One or more LUT tables include code phase correction values for various combinations of PRN code (eg, SV ID), Doppler frequency, and notch filter configuration. The code phase correction value may be a distance such as the values in FIG. 6C and FIGS. 10A-10D . Interpolation techniques such as those described in FIG. 8 can also be used to obtain code phase correction values from the LUT.

At stage 1110, the method includes calculating a range to the satellite vehicle based at least in part on the signal and code phase correction values. Processor 504 is means for calculating the distance to the SV. In an example, processor 504 may determine the pseudorange to the SV based on the signal, and apply appropriate biases and corrections known in the art and described in Equation 1 . The code phase values determined at stage 1108 may be applied to pseudoranges to generate distance values.

Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software and computers, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing functions may also be physically located at different locations, including being distributed such that some functions are implemented at different physical locations.

Unless otherwise indicated, functional or other components shown in the figures and/or discussed herein that are connected or in communication with each other are communicatively coupled. That is, they can be directly or indirectly connected to enable communication therebetween.

As used herein, the singular forms "a", "an" and "the" also include plural forms unless the context clearly dictates otherwise. For example, "a processor" may include one processor or multiple processors. The terms "comprises", "comprising", "includes" and/or "including" when used herein designate stated features, integers, steps, operations, elements and The presence of/or a component does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.

As used herein, unless otherwise stated, a statement that a function or operation is "based on" an item or condition means that the function or operation is based on that item or condition, and may be based on one or more conditions other than the stated item or condition. Multiple items and/or conditions.

Also, as used herein, "or" when used in a list of items (which may begin with "at least one" or with "one or more") indicates a list of predicates such that, for example, "of A, B, or C A list of at least one or a list of "one or more of A, B or C" or a list of "A or B or C" means A or B or C or AB (A and B) or AC (A and C) or BC (B and C) or ABC (that is, A and B and C), or a combination of more than one characteristic (for example, AA, AAB, ABBC, etc.). Thus, an item (e.g., a processor) configured to perform a statement about at least one of A or B's functions, or an item configured to perform function A or function B, means that the item can be configured to perform about The function of A may either be configured to perform functions with respect to B, or may be configured to perform functions with respect to both A and B. For example, the phrase "a processor configured to measure at least one of A or B" or "a processor configured to measure A or B" means that the processor can be configured to measure A ( and may or may not be configured to measure B), or may be configured to measure B (and may or may not be configured to measure A), or may be configured to measure A and Measurement B (and can be configured to select which or both of Measurements A and B). Similarly, a statement of means for measuring at least one of A or B includes means for measuring A (which may or may not measure B), or means for measuring B (which may or may not Can be configured as a measurement A), or a component for measurement A and B (it can choose which one or both of A and B to measure). As another example, an item (eg, a processor) configured to perform at least one of function X or function Y means that the item may be configured to perform function X, or may be configured to perform function Y, or may be Configured to perform function X and perform function Y. For example, the phrase "a processor configured to at least one of measure X or measure Y" means that the processor may be configured to measure X (and may or may not be configured to measure Y) configured to measure Y), or can be configured to measure Y (and can be configured to measure X, or not configured to measure X), or can be configured to measure X and measure Y (can configured to select which one or both of X and Y to measure).

Substantial changes may be made based on specific requirements. For example, custom hardware could also be used, and/or particular elements could be implemented in hardware, software (including portable software, such as applets, etc.) executed by a processor, or both. Additionally, connections to other computing devices such as network input/output devices may be employed.

The systems and devices discussed above are examples. Various configurations may omit, substitute, or add various programs or components as appropriate. For example, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of configuration can be combined in a similar fashion. In addition, technology evolves and, therefore, many of the elements are examples and do not limit the scope of the disclosure or claims.

A wireless communication system is a system in which communications are delivered wirelessly, that is, by electromagnetic and/or acoustic waves propagating through atmospheric space, rather than via wires or other physical connections. A wireless communication network may not have all communications sent wirelessly, but be configured to have at least some communications sent wirelessly. In addition, the term "wireless communication device" or similar terms do not require that the function of the device is exclusively or primarily for communication, or that the device is a mobile device, but rather indicate that the device includes wireless communication capabilities (one-way or two-way), for example, Include at least one radio device (each radio device being part of a transmitter, receiver or transceiver) for wireless communication.

Specific details are provided in the description to provide a thorough understanding of example configurations including implementation. However, configurations may be practiced without these specific details. For example, well-known circuits, procedures, algorithms, structures and techniques have been illustrated without unnecessary detail in order to avoid obscuring the configuration. This description provides an example configuration only, and does not limit the scope, applicability, or configuration of the requested item. Rather, the preceding description of the configurations provides a description of implementing the described techniques. Various changes may be made in the function and arrangement of elements without departing from the scope of the disclosure.

The terms "processor-readable medium", "machine-readable medium" and "computer-readable medium" are used herein to refer to any medium that participates in providing information that causes a machine to operate in a specific manner. Using a computing platform, various processor-readable media can participate in providing instructions/code to the processor for execution and/or can be used to store and/or carry such instructions/code (eg, as signals). In many implementations, the processor-readable medium is a physical and/or tangible storage medium. Such media can take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media include, for example, optical and/or magnetic disks. Volatile media includes, but is not limited to, dynamic memory.

A statement that a value exceeds (or is greater than or higher than) a first threshold is equivalent to a statement that a value meets or exceeds a second threshold that is slightly greater than the first threshold, e.g., the second threshold is higher than the first threshold in the resolution of the computing system a value. A statement that a value is less than (or within or within the range of) a first threshold is equivalent to a statement that a value is less than or equal to a second threshold slightly lower than the first threshold, e.g., in the resolution of the computing system, the second threshold is less than The first threshold is lower by one value.

The following numbered clauses describe implementation examples:

1. A method for determining the range to a satellite vehicle using a receiver comprising:

receive signals from the satellite vehicle;

determining one or more notch filter configurations;

determining a pseudorandom noise code and a Doppler frequency associated with the signal;

determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and

The distance to the satellite vehicle is calculated based at least in part on the signal and the code phase correction value.

2. The method of clause 1, wherein determining the code phase correction value comprises obtaining the code from a lookup table based on the one or more notch filter configurations, the pseudorandom noise code, and the Doppler frequency Phase correction value.

3. The method of clause 2, further comprising receiving auxiliary data from a network entity, wherein the auxiliary data includes the lookup data table.

4. The method of clause 3, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages.

5. The method of clause 3, wherein the assistance data is received via one or more radio resource control (RRC) messages.

6. The method of clause 2, wherein determining the code phase correction value comprises obtaining the code phase correction value based on an interpolation function.

7. The method of clause 1, further comprising generating a look-up table with the receiver based on a modeled autocorrelation function of the plurality of notch filter configurations, and wherein determining the code phase correction value comprises: based on the one or more A notch filter configuration, the pseudo-random noise code and the Doppler frequency obtain the code phase correction value from the look-up table.

8. The method of clause 1, wherein the one or more notch filter configurations include one or more notch frequencies and one or more bandwidths associated with the one or more notch frequencies.

9. The method of clause 1, wherein calculating the distance to the satellite vehicle comprises determining a pseudorange to the satellite vehicle based on the signal.

10. The method of clause 1, wherein the receiver includes one or more notch filters composed of one or more digital filter filters with programmable center frequency and bandwidth device composition.

11. A device comprising:

Memory;

at least one satellite positioning system receiver configured to receive signals from satellite vehicles;

at least one processor communicatively coupled to the memory and the at least one satellite positioning system receiver and configured to:

receiving the signal from the satellite vehicle;

determining one or more notch filter configurations;

determining a pseudorandom noise code and a Doppler frequency associated with the signal;

determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and

A range to the satellite vehicle is calculated based at least in part on the signal and the code phase correction value.

12. The apparatus of clause 11, wherein the at least one processor is further configured to obtain from a lookup table based on the one or more notch filter configurations, the pseudorandom noise code, and the Doppler frequency The code phase correction value.

13. The apparatus of clause 12, further comprising at least one transceiver communicatively coupled to the at least one processor such that the at least one processor is further configured to receive assistance data from a network entity, and wherein the Auxiliary data includes the lookup data sheet.

14. The device of clause 13, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages.

15. The device of clause 13, wherein the assistance data is received via one or more radio resource control (RRC) messages.

16. The apparatus of clause 12, wherein the at least one processor is further configured to obtain the code phase correction value based on an interpolation function.

17. The apparatus of clause 11, wherein the at least one processor is further configured to generate a look-up table based on a modeled autocorrelation function of the plurality of notch filter configurations, and based on the one or more notch filter The configuration, the pseudo-random noise code and the Doppler frequency obtain the code phase correction value from the look-up table.

18. The apparatus of clause 11, wherein the one or more notch filter configurations comprise one or more notch frequencies and one or more bandwidths associated with the one or more notch frequencies.

19. The apparatus of clause 11, wherein the at least one processor is further configured to determine a pseudorange to the satellite vehicle based on the signal.

20. The apparatus of clause 11, wherein the one or more notch filter configurations comprise one or more digital filters having programmable center frequencies and bandwidths.

21. An apparatus for determining a distance to a satellite vehicle comprising:

means for receiving signals from the satellite vehicle;

means for determining one or more notch filter configurations;

means for determining the pseudorandom noise code and the Doppler frequency associated with the signal;

means for determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and

means for calculating the distance to the satellite vehicle based at least in part on the signal and the code phase correction value.

22. The apparatus of clause 21, wherein the means for determining the code phase correction value comprises: for The code phase correction value is obtained from the frequency reference table.

23. The apparatus of clause 22, further comprising means for receiving auxiliary data from a network entity, wherein the auxiliary data includes the lookup data table.

24. The device of clause 23, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages.

25. The device of clause 23, wherein the assistance data is received via one or more radio resource control (RRC) messages.

26. The apparatus of clause 22, wherein the means for determining the code phase correction value comprises means for obtaining the code phase correction value based on an interpolation function.

27. The apparatus of clause 21, further comprising means for generating a look-up table based on a modeled autocorrelation function of the plurality of notch filter configurations, wherein the means for determining the code phase correction value comprises: using means for obtaining the code phase correction value from the look-up table based on the one or more notch filter configurations, the pseudo-random noise code and the Doppler frequency.

28. The apparatus of clause 21, wherein the one or more notch filter configurations comprise one or more notch frequencies and one or more bandwidths associated with the one or more notch frequencies.

29. The apparatus of clause 21, wherein the means for calculating the distance to the satellite vehicle comprises means for determining a pseudorange to the satellite vehicle based on the signal.

30. The apparatus of clause 21, further comprising one or more notch filters consisting of one or more digital filters with programmable center frequencies and bandwidths.

31. A non-transitory processor readable storage medium comprising processor readable instructions for causing one or more processors to determine a distance to a satellite vehicle, comprising:

the code used to receive signals from the satellite vehicle;

code for determining the configuration of one or more notch filters;

the code used to determine the pseudorandom noise code and the Doppler frequency associated with the signal;

a code for determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and

A code for calculating the range to the satellite vehicle based at least in part on the signal and the code phase correction value.

32. The non-transitory processor-readable storage medium of clause 31, wherein the code for determining the code phase correction value includes a method for determining the code phase correction value based on the one or more notch filter configurations, the pseudo-random The noise code and the Doppler frequency code are obtained from a reference table for the phase correction value of the code.

33. The non-transitory processor-readable storage medium of clause 32, further comprising code for receiving auxiliary data from a network entity, wherein the auxiliary data includes the lookup data table.

34. The non-transitory processor-readable storage medium of clause 33, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages.

35. The non-transitory processor-readable storage medium of clause 33, wherein the assistance data is received via one or more radio resource control (RRC) messages.

36. The non-transitory processor-readable storage medium of clause 32, wherein the code for determining the code phase correction value comprises code for obtaining the code phase correction value based on an interpolation function.

37. The non-transitory processor-readable storage medium of clause 31, further comprising code for generating a look-up table based on a modeled autocorrelation function of the plurality of notch filter configurations, and wherein for determining the The code for a code phase correction value includes code for obtaining the code phase correction value from the lookup table based on the one or more notch filter configurations, the pseudo random noise code, and the Doppler frequency.

38. The non-transitory processor-readable storage medium of clause 31, wherein the one or more notch filter configurations include one or more notch frequencies and One or more bandwidths of .

39. The non-transitory processor-readable storage medium of clause 31, wherein the code for calculating the distance to the satellite vehicle includes a code for determining a pseudorange to the satellite vehicle based on the signal code.

40. The non-transitory processor-readable storage medium of clause 31, further comprising one or more notch filters composed of one or more and bandwidth digital filters.

100: Communication system 105:UE 110a: NR Node B (gNB) 110b: NR Node B (gNB) 114: Next Generation eNode B (ng-eNB) 115: Access and Mobility Management Function (AMF) 117: Communication period management function (SMF) 120: Location management function (LMF) 125: Gateway Operations Location Center (GMLC) 130: external client 135: Radio Access Network (RAN) 140: 5G core network (5GC) 185: cluster 190:Satellite Vehicle (SV) 191:Satellite Vehicle (SV) 192:Satellite Vehicle (SV) 193:Satellite Vehicle (SV) 200:UE 210: Processor 211: Memory 212: Software (SW) 213: sensor 214: transceiver interface 215: Transceiver 216: User interface 217: Satellite Positioning System (SPS) Receiver 218: camera 219: Position (Motion) Devices 220: busbar 230: General/Application Processor 231:Digital signal processor (DSP) 232: Modem processor 233: video processor 234: sensor processor 240: wireless transceiver 242: Transmitter 244: Receiver 246: Antenna 248: wireless signal 250: wired transceiver 252: Transmitter 254: Receiver 260: SPS signal 262: SPS antenna 270: Inertial Measurement Unit (IMU) 271: Magnetometer 272: Environmental sensor 273: Accelerometer 274: Gyroscope 300:TRP 310: Processor 311: memory 312: Software (SW) 315: Transceiver 317: SPS receiver 320: busbar 340: wireless transceiver 342: Transmitter 344: Receiver 346: Antenna 348: wireless signal 350: wired transceiver 352: Transmitter 354: Receiver 360: SPS signal 362:SPS Antenna 400: server 410: Processor 411: Memory 412: Software (SW) 415: Transceiver 420: busbar 440: wireless transceiver 442: Transmitter 444: Receiver 446: Antenna 448: wireless signal 450: wired transceiver 452: sender 454: Receiver 500: GNSS receiver 501: Antenna 502: Analogy part 503: digital part 504: Processor 600: figure 602:GNSS Spectrum 604: signal drop 610: figure 612: Typical ACF 614:ACF 620: chart 622: code phase error value 700: process 702: Offline lookup table (LUT) 704: Notch filter configuration 706: SV PRN and Doppler frequency information 706a: SVID 706b: SV Doppler 708: stage 710: stage 800: process 802: stage 804: stage 806: stage 900: process 902: Notch filter configuration information 904: SV PRN and Doppler frequency information 906: stage 908: stage 910: stage 1100: method 1102: stage 1104: stage 1106: stage 1108: stage 1110: stage

Figure 1 is a simplified diagram of an example wireless communication system.

FIG. 2 is a block diagram of components of the example UE shown in FIG. 1 .

Figure 3 is a block diagram of components of an example transmit/receive point.

FIG. 4 is a block diagram of components of an example server, various embodiments of which are illustrated in FIG. 1 .

5 is a diagram of an example GNSS receiver in a user device.

6A is a graph of an example GNSS spectrum with a notch filter applied.

Figure 6B is a comparison graph of an example autocorrelation function with and without a notch filter.

6C is a graph of code phase error values based on example notch filter frequencies.

7 is a block diagram of an example process for off-line phase compensation based on a notch filter configuration.

8 is a block diagram of an example process for calculating code phase correction values.

9 is a block diagram of an example process for in-line phase calculation based on a notch filter configuration.

10A-10D include example graphs of code phase error for a plurality of satellite vehicles and notch filter configurations.

11 is a process flow diagram of an example method for calculating distance to a satellite vehicle.

Domestic deposit information (please note in order of depositor, date, and number) none Overseas storage information (please note in order of storage country, institution, date, and number) none

700: process

702: Offline lookup table (LUT)

704: Notch filter configuration

706: SV PRN and Doppler frequency information

706a: SVID

706b: SV Doppler

708: stage

710: stage

Claims (40)

A method for determining a distance to a satellite vehicle using a receiver, comprising the steps of: receiving a signal from the satellite vehicle; determining one or more notch filter configurations; determining a pseudorandom noise code and a Doppler frequency associated with the signal; determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and The distance to the satellite vehicle is calculated based at least in part on the signal and the code phase correction value. The method as recited in claim 1, wherein determining the code phase correction value comprises the steps of: based on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency, from a lookup data Table to obtain the code phase correction value. The method of claim 2, further comprising receiving auxiliary data from a network entity, wherein the auxiliary data includes the lookup data table. The method of claim 3, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages. The method of claim 3, wherein the assistance data is received via one or more radio resource control (RRC) messages. The method as claimed in claim 2, wherein determining the code phase correction value comprises the following steps: obtaining the code phase correction value based on an interpolation function. The method as claimed in claim 1, further comprising generating a look-up table using the receiver based on the modeled autocorrelation function of the plurality of notch filter configurations, and wherein determining the code phase correction value comprises the steps of: based on the or a plurality of notch filter configurations, the pseudo-random noise code and the Doppler frequency, the code phase correction value is obtained from the look-up table. The method of claim 1, wherein the one or more notch filter configurations include: one or more notch frequencies, and one or more bandwidths associated with the one or more notch frequencies. The method of claim 1, wherein calculating the distance to the satellite vehicle comprises the step of: determining a pseudorange to the satellite vehicle based on the signal. The method as claimed in claim 1, wherein the receiver includes one or more notch filters, the one or more notch filters are composed of one or more digital filters with programmable center frequency and bandwidth composition. A device comprising: a memory; at least one satellite positioning system receiver configured to receive a signal from a satellite vehicle; and at least one processor, communicatively coupled to the memory and the at least one satellite positioning system receiver, and configured to: receiving the signal from the satellite vehicle; determining one or more notch filter configurations; determining a pseudorandom noise code and a Doppler frequency associated with the signal; determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and A distance to the satellite vehicle is calculated based at least in part on the signal and the code phase correction value. The apparatus of claim 11, wherein the at least one processor is further configured to obtain from a lookup table based on the one or more notch filter configurations, the pseudorandom noise code, and the Doppler frequency The code phase correction value. The apparatus of claim 12, further comprising at least one transceiver communicatively coupled to the at least one processor, wherein the at least one processor is further configured to receive assistance data from a network entity, and wherein the assistance data includes The lookup table. The device of claim 13, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages. The device of claim 13, wherein the assistance data is received via one or more radio resource control (RRC) messages. The device of claim 12, wherein the at least one processor is further configured to obtain the code phase correction value based on an interpolation function. The device as claimed in claim 11, wherein the at least one processor is further configured to generate a look-up table based on the modeled autocorrelation function of the plurality of notch filter configurations, and based on the one or more notch filters The configuration, the pseudo-random noise code and the Doppler frequency, and the code phase correction value are obtained from the look-up table. The apparatus of claim 11, wherein the one or more notch filter configurations comprise: one or more notch frequencies, and one or more bandwidths associated with the one or more notch frequencies. The apparatus of claim 11, wherein the at least one processor is further configured to determine a pseudorange to the satellite vehicle based on the signal. The apparatus of claim 11, wherein the one or more notch filter configurations comprise one or more digital filters with programmable center frequencies and bandwidths. An apparatus for determining a distance to a satellite vehicle comprising: means for receiving a signal from the satellite vehicle; means for determining one or more notch filter configurations; means for determining a pseudorandom noise code and a Doppler frequency associated with the signal; means for determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and means for calculating the distance to the satellite vehicle based at least in part on the signal and the code phase correction value. The device as claimed in claim 21, wherein the means for determining the code phase correction value comprises: for determining the code phase correction value based on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency , and obtain the code phase correction value from a look-up data table. The apparatus of claim 22, further comprising means for receiving auxiliary data from a network entity, wherein the auxiliary data includes the lookup data table. The device of claim 23, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages. The device of claim 23, wherein the assistance data is received via one or more radio resource control (RRC) messages. The apparatus of claim 22, wherein the means for determining the code phase correction value comprises: means for obtaining the code phase correction value based on an interpolation function. The apparatus of claim 21, further comprising means for generating a look-up table based on the modeled autocorrelation function of the plurality of notch filter configurations, and wherein the means for determining the code phase correction value comprises: means for obtaining the code phase correction value from the look-up table based on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency. The apparatus of claim 21, wherein the one or more notch filter configurations comprise: one or more notch frequencies, and one or more bandwidths associated with the one or more notch frequencies. The apparatus of claim 21, wherein the means for calculating the distance to the satellite vehicle comprises means for determining a pseudorange to the satellite vehicle based on the signal. The device according to claim 21, further comprising one or more notch filters, the one or more notch filters are composed of one or more digital filters with programmable center frequency and bandwidth. A non-transitory processor readable storage medium comprising processor readable instructions for causing one or more processors to determine a distance to a satellite vehicle, comprising: a code for receiving a signal from the satellite vehicle; code for determining the configuration of one or more notch filters; a code for determining a pseudorandom noise code and a Doppler frequency associated with the signal; code for determining a code phase correction value based at least on the one or more notch filter configurations, the pseudo random noise code and the Doppler frequency; and A code for calculating the distance to the satellite vehicle based at least in part on the signal and the code phase correction value. The non-transitory processor-readable storage medium as recited in claim 31, wherein the code for determining the code phase correction value includes: for determining the code phase correction value based on the one or more notch filter configurations, the pseudo-random Noise code and the Doppler frequency, and the code of the code phase correction value is obtained from a look-up table. The non-transitory processor-readable storage medium of claim 32, further comprising code for receiving auxiliary data from a network entity, wherein the auxiliary data includes the lookup data table. The non-transitory processor-readable storage medium of claim 33, wherein the assistance data is received via one or more Long Term Positioning Protocol (LPP) messages. The non-transitory processor-readable storage medium of claim 33, wherein the auxiliary data is received via one or more radio resource control (RRC) messages. The non-transitory processor-readable storage medium as claimed in claim 32, wherein the code for determining the code phase correction value comprises: code for obtaining the code phase correction value based on an interpolation function. The non-transitory processor-readable storage medium of claim 31, further comprising code for generating a look-up table based on the modeled autocorrelation function of the plurality of notch filter configurations, and wherein for determining the The code for a code phase correction value includes: for obtaining the code phase correction value from the look-up table based on the one or more notch filter configurations, the pseudo random noise code, and the Doppler frequency code. The non-transitory processor-readable storage medium as described in claim 31, wherein the one or more notch filter configurations include: one or more notch frequencies, and One or more bandwidths associated. The non-transitory processor-readable storage medium of claim 31, wherein the code for calculating the distance to the satellite vehicle comprises: determining a pseudorange to the satellite vehicle based on the signal code. The non-transitory processor-readable storage medium as described in claim 31, further comprising one or more notch filters, the one or more notch filters are composed of one or more programmable center frequencies and Bandwidth digital filter composition.

Images