# US 2025/0093524 A1 · Gnss receivers and methods for operating gnss receivers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0093524 A1
- Document ID: US20250093524A1
- Status: Published application
- Kind: A1
- Application number: 18/889,268
- Filed: 2024-09-18
- Published: 2025-03-20
- Earliest claimed: 2023-09-19
- Assignees: oneNav, Inc.
- Applicants: oneNav, Inc.
- Inventors: Paul A. Conflitti; Stephen Rose
- Web page: https://patentgrep.com/patent/US20250093524A1

## CPC

- G01S 19/21: Interference related issues {; Issues related to cross-correlation, spoofing or other methods of denial of service}
- G01S 19/252: {Employing an initial estimate of location in generating assistance data}
- G01S 19/20: Integrity monitoring, fault detection or fault isolation of space segment
- G01S 19/215: {issues related to spoofing}
- G01S 19/25: involving aiding data received from a cooperating element, e.g. assisted GPS
- G01S 19/37: Hardware or software details of the signal processing chain
- G01S 19/42: Determining position
- G01S 19/015: {Arrangements for jamming, spoofing or other methods of denial of service of such systems}
- G01S 19/33: Multimode operation in different systems which transmit time stamped messages, e.g. GPS/GLONASS
- G01S: RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES

## Abstract

Systems and methods for GNSS receivers are described. A system for processing GNSS signals includes one or more GNSS antennas, one or more GNSS measurement engines, and one or more processing systems. The one or more GNSS measurement engines are coupled to the one or more GNSS antennas. The one or more GNSS measurement engines correlate and process received GNSS signals in an L5 radio frequency band. The one or more processing systems are coupled to a first memory which stores an application programming interface (API) which includes one or more of parameters or instructions for processing GNSS signals. The one or more processing systems use the API to control operation of the one or more GNSS measurement engines.

## Claims

### Claim 1

A system for processing GNSS signals, the system comprising:
one or more GNSS antennas;
one or more GNSS measurement engines coupled to the one or more GNSS antennas, the one or more GNSS measurement engines to correlate and process received GNSS signals in an L5 radio frequency band;
one or more processing systems coupled to a first memory which stores an application programming interface (API) which includes one or more of parameters or instructions for processing GNSS signals, the one or more processing systems using the API to control operation of the one or more GNSS measurement engines.

### Claim 2 (depends on 1)

The system as in claim 1, wherein the one or more GNSS measurement engines comprises a (1) first GNSS measurement engine which correlates GNSS signals in one or more of an L1 or L2 radio frequency bands to produce a first set of one or more pseudoranges from received GNSS signals in the one or more of the L1 or L2 bands and (2) a second GNSS measurement engine which correlates GNSS signals in an L5 radio frequency band to produce a second set of one or more pseudoranges from received GNSS signals in the L5 band.

### Claim 3 (depends on 2)

The system as in claim 2, wherein the second GNSS measurement engine operates without aid from processing of GNSS signals in the L1 band.

### Claim 4 (depends on 3)

The system as in claim 3, wherein the one or more antennas comprises a controlled reception pattern antenna.

### Claim 5 (depends on 3)

The system as in claim 3, wherein the API includes one or more parameters or instructions to mitigate against jamming of GNSS signals.

### Claim 6 (depends on 5)

The system as in claim 5, wherein the API includes one or more parameters or instructions to spatially null signals in a direction of a jamming source.

### Claim 7 (depends on 3)

The system as in claim 3, wherein the first and second GNSS measurement engines operate concurrently.

### Claim 8 (depends on 7)

The system as in claim 7, wherein the first GNSS measurement engine correlates received GNSS signals which include encrypted PRN codes.

### Claim 9 (depends on 7)

The system as in claim 7, wherein the second GNSS measurement engine correlates received GNSS signals which include PRN codes that are not encrypted.

### Claim 10 (depends on 7)

The system as in claim 7, the system further comprising:
an inertial navigation system that comprises one or more inertial navigation sensors, the inertial navigation system coupled to the one or more processing systems to receive position outputs from one or more position solution engines that are coupled to the first and second measurement engines.

### Claim 11 (depends on 10)

The system as in claim 10, wherein the system is contained in a drone which includes a propulsion system to move the drone, and wherein the inertial navigation system is coupled to the propulsion system.

### Claim 12 (depends on 11)

The system as in claim 11, wherein the first memory is non-volatile memory that is electrically re-programmable, and the first memory stores firmware for controlling the operation of at least the second GNSS measurement engine, and the firmware receives calls through the API to configure operation of the second GNSS measurement engine and the firmware is re-programmable.

### Claim 13 (depends on 12)

The system as in claim 12, wherein an updated firmware, updated when the first memory is re-programmed, includes an updated API.

### Claim 14 (depends on 1)

The system as in claim 1, wherein the API is used to select among different processing paths that are available for use in the second GNSS measurement engine.

### Claim 15 (depends on 1)

The system as in claim 1, wherein the one or more GNSS measurement engines comprises a GNSS measurement engine that acquires and determines pseudoranges from received GNSS signals in the L5 band without aid from processing or receipt of GNSS signals in the L1 band, and wherein the system includes an inertial navigation system that comprises one or more inertial navigation sensors, the inertial navigation system coupled to the one or more processing systems to receive position outputs from one or more position solution engines that are coupled to the first and second measurement engines, and wherein the system is contained in a drone which includes a propulsion system to move the drone, and wherein the inertial navigation system is coupled to the propulsion system.

### Claim 16

A method of operating a GNSS receiver, the method comprising:
receiving, through one or more GNSS antennas, GNSS signals from a set of GNSS SVs;
correlating, in one or more GNSS measurement engines, the received GNSS signals to produce a set of one or more pseudoranges, the one or more GNSS measurement engines comprising a first GNSS measurement engine that correlates received GNSS signals in an L5 band to produce pseudoranges from the received GNSS signals in the L5 band;
computing, in one or more processing systems, one or more positions of the GNSS receiver;
controlling, through an application programming interface (API) which includes one or more of parameters or instructions for processing GNSS signals, operation of the first GNSS measurement engine.

### Claim 17 (depends on 16)

The method as in claim 16, wherein the one or more processing systems comprises a first position solution engine, and wherein the one or more GNSS measurement engines comprise a second GNSS measurement engine to correlate received GNSS signals in an L1 band.

### Claim 18 (depends on 17)

The method as in claim 17, wherein the method is performed in a drone which includes an inertial navigation system that is coupled to the first position solution engine.

### Claim 19 (depends on 18)

The method as in claim 18, wherein at least a portion of the API and firmware that receives calls through the API is stored in non-volatile memory which is re-programmable to allow for updating of the firmware.

### Claim 20 (depends on 19)

The method as in claim 19, wherein the API includes one or more parameters or instructions to mitigate the effects of jamming or spoofing.

### Claim 21 (depends on 20)

The method as in claim 20, wherein the API is used by the first position solution engine to select among different processing paths that are available for use in the first GNSS measurement engine.
