Method and apparatus for generating and distributing orbital elements for doppler, altitude, and pseudorange estimation - Patents.com

The ephemeris server provides long-lasting Keplerian ephemeris to GNSS receivers, addressing inaccuracies in satellite predictions by updating only when error thresholds are met, enhancing accuracy and efficiency in low-power devices.

JP7584519B2Active Publication Date: 2024-11-15XINGMENG INT CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2022537236
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-12-19
Filing Date
2020-12-07
Publication Date
2024-11-15
Estimated Expiration
2040-12-07

AI Technical Summary

Technical Problem

GNSS receivers face increased acquisition and tracking times due to inaccuracies in satellite ephemeris predictions, leading to errors in Doppler, pseudorange, and altitude estimation, especially in low-power IoT devices with limited bandwidth and power constraints.

Method used

An ephemeris server provides long-lasting Keplerian ephemeris (LK ephemeris) to GNSS receivers, updating only when predetermined error thresholds are exceeded, using a real-time database and efficient communication to minimize updates and conserve power and bandwidth.

Benefits of technology

The LK ephemeris extends the lifespan of satellite ephemeris data, reducing frequent updates and maintaining accurate Doppler and pseudorange estimates for extended periods, thus optimizing power and bandwidth usage in low-power devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584519000011
    Figure 0007584519000011
  • Figure 0007584519000012
    Figure 0007584519000012
  • Figure 0007584519000013
    Figure 0007584519000013
Patent Text Reader

Abstract

The ephemeris server performs a method comprising: (a) (i) obtaining broadcast ephemeris information by accessing a source of broadcast information on a wide area communication network; (ii) extracting orbital information for each satellite's orbit from the broadcast ephemeris information; (iii) creating corrected orbital information for each satellite from the extracted orbital information and storing the corrected orbital information in a real-time database; (b) at each of a plurality of specified times, updating the corrected orbital information in the real-time database based on an evaluation of an update criterion; and (c) providing the corrected orbital information to each of a plurality of devices, each device having a GNSS receiver capable of processing the satellite's broadcast signal using the corrected orbital information.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to the Global Navigation Satellite System (GNSS). The present invention relates to the processing and processing of ephemeris data used in determining position, velocity and time (PVT) using GNSS. [Background technology]

[0002] To reduce acquisition time, GNSS receivers are provided with prior information (e.g., position and velocity, or "ephemeris") about the orbits of satellites in the GNSS. For example, such information can be obtained from terrestrial sources or from navigation messages broadcast by each satellite in the GNSS. A satellite's ephemeris allows the receiver to estimate the satellite's altitude, Doppler, and pseudorange at any time, which allows the receiver to narrow the frequency and delay search space for the satellite when it appears above the receiver's horizon. In that respect, a relatively narrow frequency bin of 200 Hz allows for a Doppler estimation error of about 100 Hz. However, because the satellite's orbit is not perfectly predictable, the provided ephemeris becomes inaccurate over time. For a GNSS receiver, as the accuracy of a satellite's provided ephemeris decreases, the estimation errors due to Doppler, pseudorange, and altitude increase. As a result, the time and energy required to acquire and track a satellite can increase significantly over time. Typically, GNSS updates the broadcast ephemeris information in each satellite's navigation message ("system update") every 1-2 hours.

[0003] As with Doppler, pseudorange, and altitude estimation, a typical GNSS Medium Earth Orbit ("MEO") satellite takes approximately 120 seconds to fly one degree around the center of the Earth (i.e., the satellite's elevation angle ("altitude") changes in the order of 1 / 2 degree per minute), so altitude estimation errors are relatively insignificant. However, during that time the satellite's velocity changes by 60 m / s (i.e., approximately 1%), so both Doppler and pseudorange estimation errors can be significant.

[0004] To determine the satellite's orbit in the geocentric Earth-fixed (ECEF) coordinate system, the six Keplerian orbital elements and the Earth's rotation rate (Ω e The Kepler orbital elements are: (i) eccentricity (e), (ii) semi-major axis length (A), (iii) inclination at the reference epoch (i0), (iv) longitude of ascending node of the orbital plane at the reference epoch (Ω0), (v) argument of perigee (ω), and (vi) mean anomaly at the reference epoch (M0).

[0005] For the NAVSTAR Global Positioning System ("GPS"), the ECEF Coordination System definitions, data formats, and corrections for ephemeris parameters are listed in Tables 20-II, 20-III, and 20-IV in Section 20.3.4 of publication "NAVSTAR GPS Space Segment / Navigation User Segment Interfaces" (IS-GPS-200D; "Interface Specification"). Most of these ephemeris parameters are related to Keplerian orbital parameters. In GPS, the ephemeris parameter values ​​provided by the ECEF coordinate system provide the best fit of the orbit for each specific fit interval.

[0006] The interface specification adds nine ephemeris parameters: (i) the mean motion difference from the computed value (Δn), (ii) the rate of change of right ascension (Ω), (iii) the rate of change of inclination (IDOT), and (iv) the amplitude of the sine and cosine harmonic correction terms for the latitude argument (c us ,c uc ), (v) the amplitude of the sine and cosine harmonic correction terms versus orbit radius (c rs ,c rc ), and (vi) the amplitude of the sine and cosine harmonic correction terms versus tilt angle (c is ,c ic). These additional ephemeris parameters are called "gravitational harmonic correction terms, rates and rate corrections" to the Keplerian parameters. These additional GPS parameters are also used by China's Beidou System (BDS), Europe's Galileo System (GAL), and Japan's QZSS. In GPS, the length of the navigation message is 1500 bits long, and the ephemeris transmitted in the navigation message is often only valid for a few days or less.

[0007] In recent years, many applications have been developed for small mobile devices or sensors where the location of such devices is relevant. In many such applications (e.g., "Internet of Things" (IoT) applications), the location of such devices is obtained by an on-board GNSS receiver module. Inevitably, IoT devices operate on battery power and communicate using wireless communication. Indeed, in many such applications, IoT devices must operate with very low power requirements and communicate using long-range, very low data rate wireless communication systems. Summary of the Invention [Means for solving the problem]

[0008] According to an embodiment of the present disclosure, an ephemeris server performs a method for providing ephemeris information of satellites from at least one GNSS, the method according to the present disclosure includes the steps of: (a) (i) obtaining broadcast ephemeris information by accessing a source of broadcast information on a wide area communication network, (ii) extracting orbit information for each satellite's orbit from the broadcast ephemeris information, (iii) creating and storing corrected orbit information for each satellite from the extracted orbit information in a real-time database, (b) updating the corrected orbit information in the real-time database at each of a plurality of designated times based on an evaluation of an update criterion, and (c) providing the corrected orbit information to each of a plurality of devices, each of the devices having a GNSS receiver capable of processing the satellite's broadcast signal using the corrected orbit information.

[0009] The present invention is better understood upon consideration of the following detailed description and the accompanying drawings. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 shows a system 100 having an ephemeris server 101 and devices 102-1 to 102-n, each having a GNSS receiver, according to one embodiment of the present invention. [Diagram 2] 4 is a table showing each field of the LK ephemeris according to one embodiment of the present invention. [Diagram 3] 13 is a table showing the number of updates and the average length per bitstream obtained from various simulation results under Strategy 1, Strategy 2, or neither strategy ("Current Strategy"), respectively. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The present invention is illustrated in this detailed description by the system 100 of FIG. 1. FIG. 1 illustrates the system 100 having an ephemeris server 101 and devices 102-1 to 102-n, each having a GNSS receiver, according to one embodiment of the present invention. In the system 100, each of the devices 102-1, 102-n uses its on-board GNSS receiver to perform satellite navigation-related tasks (e.g., determining position, velocity, or time), satellite positioning-related, or other suitable tasks, but relies on the ephemeris server 101 to provide satellite ephemeris information to the GNSS receiver to facilitate the navigation-related tasks. For example, the ephemeris server 101 accesses or receives system updates from a conventional source 103 (e.g., NASA's CDDIS) via a wide area network 104 (e.g., the Internet). Devices 102-1 to 102-n, some of which may be mobile devices and sensors, communicate with the ephemeris server 101 via one or more wide area communication networks 105 (e.g., low power wide area networks (LPWANs) such as LoRa-based networks). For these devices, efficient use of power savings and low bandwidth is of paramount importance. It is therefore highly desirable that the ephemeris information provided by the ephemeris server 101 is updated infrequently, and each update message should have as few bits as feasible.

[0012] As mentioned above, the duration for which the ephemeris remains valid in a system update depends on the subsequent operation of the satellite. For high performance applications, the valid life of the ephemeris in a system update is at least a few hours. The present invention extends the life of satellite ephemeris used in the on-board GNSS receiver of a low power device by providing device-selected ephemeris parameter values ​​that are modified to have a longer life ("long-lasting Kepler ephemeris" or "LK ephemeris") and updated in the GNSS receiver on demand or based on one or more performance criteria, but not always when a system update is available. For example, the ephemeris server 101 monitors the Doppler or pseudorange estimation error between the Doppler or pseudorange estimate obtained using the latest system update and the Doppler or pseudorange obtained using the LK ephemeris. The ephemeris server 101 re-evaluates the LK ephemeris only if the monitored quantity exceeds a predefined threshold ("update criteria").

[0013] Typically, the Doppler estimation error threshold is set to 100 Hz (i.e., a valid ephemeris is expected to produce a Doppler estimation error within about ±50 Hz). To reduce communication costs, the LK ephemeris contains only selected ephemeris parameters of the system update. The ephemeris server 101 transmits the LK ephemeris to each GNSS receiver in a message coded in an efficient manner.

[0014] We observe the following: (i) The perturbations in the satellite motion do not result in significant Doppler estimation errors, so the harmonic terms (i.e., the latitude argument (c us ,c uc ), orbital radius (c rs ,c rc ), and the inclination angle (c is ,c ic ) does not need to be included in the LK ephemeris. (ii) The mean difference of motion Δn, the rate of change of right ascension Ω, and the rate of change of obliquity IDOT are related. The three terms are related to the Earth's rotational speed Ω e and the tilt of the polar axis. The rotation speed of the Earth, Ω e Since Ω varies very slowly, its effect on the satellite's orbit is generally not significant. Therefore, it is not necessary to include these terms in the transmitted LK ephemeris. For example, for GPS satellites, GNSS receivers provide IDOT=0 and Ω, which are adequate estimates for these terms in some applications. e Use =8.15e-9.0. (iii) The orbital eccentricity e, the inclination at the reference epoch i, the longitude of the ascending node in the orbital plane at the reference epoch Ω, the argument of perigee ω, and the mean anomaly at the reference epoch M are relatively stable parameters, so it is expected that these ephemeris parameters will require infrequent updates.

[0015] However, errors in the estimation of the semi-major axis A, which determines the satellite's orbital period, can cause the LK ephemeris to expire. Generally, the semi-major axis A of a satellite's orbit is estimated using the following equation:

[0016]

number

[0017] where n is the mean motion of the satellite, Δn is the estimated error in the mean motion, and μ is the gravitational constant of the Earth. Even for relatively long periods (e.g., 60 days), the mean motion n can be modeled by a linear function of time. If the correlation between the mean motion n and the linear function of time exceeds 0.5, and if at least 30 days of historical data exist for the mean motion n, then the estimate of n n ~ is derived from the following equation:

[0018]

number

[0019] where k and b are values ​​that can be derived, for example, from linear regression of historical data. If the correlation between the average movement n and a linear function of time does not exceed 0.5 and there is at least 30 days of historical data for the average movement n, then an estimate of n ~ is derived from the following equation:

[0020]

number

[0021] Estimated value n ~ is the reference epoch t ref is used to calculate the correction ΔM to the mean anomaly M of the satellite at

[0022]

number

[0023] An estimate of the satellite clock error Δt is obtained using the following equation:

[0024]

number

[0025] An estimate of the Doppler estimation error, Δλ, is obtained using the following equation:

[0026]

number

[0027] where a is the satellite acceleration along the line of sight at time t, and a max is the maximum acceleration of the satellite along the line of sight at time t. The Doppler estimation error of the GNSS receiver is the Doppler threshold (Δλ) max (e.g., 100Hz) to ensure that the estimated value n ~ is given by the following equation:

[0028]

number

[0029] In the formula, t maxΔM is the maximum estimated error (ΔM) for the mean anomaly M0 max This is the time when

[0030] Next, we use a long-term estimate of the length of the semimajor axis of the satellite's orbit, A ~ is obtained using the following equation:

[0031]

number

[0032] Reference epoch t ref The long-term mean anomaly M0 tref is the mean anomaly M0 at the specified time t of the last system update, according to the following equation: t is derived from

[0033]

number

[0034] Similarly, the long-term longitude of the ascending node of the orbital plane Ω0 tref is the longitude of the ascending node of the orbital plane at the specified time t of the last system update according to the following equation: t is related to.

[0035]

number

[0036] In the formula, Ω e is the Earth's rotation speed, and WN tref and W.N. t are the GPS week of the reference epoch and the GPS week of the ephemeris time, respectively.

[0037] According to one embodiment of the present invention, based on system updates obtained from at least one GNSS and provided in ephemeris updates from the ephemeris server 101, only the following ephemeris parameters are prepared by the processor of the ephemeris server 101: (i) system identification ("System ID"), (ii) satellite identification ("PRN ID"), (iii) an estimate of the length of the semi-major axis of the satellite's orbit A ~ , (iv) Estimated orbital eccentricity e ~ , (v) Estimated tilt angle i0 at the reference epoch ~ , (vi) the estimated longitude of the ascending node of the orbital plane at the reference epoch Ω0 tref , (vii) Estimated argument of perigee ω ~ , and (viii) the mean anomaly M0 at the reference epoch. tref Items (iii)-(iv) collectively constitute one phase of the LK ephemeris. As will be shown below, a GNSS receiver can use only these LK ephemeris over long periods of time (e.g., weeks) to estimate altitude, pseudorange, and Doppler within reasonable predetermined thresholds (e.g., a Doppler threshold of 100 Hz and a delay threshold of 250 microseconds), thereby avoiding frequent updates of the GNSS receiver.

[0038] In theory, if the reference epoch is known in both the ephemeris server 101 and the GNSS receiver, the ephemeris server 101 does not need to provide the ephemeris time of each LK ephemeris to the GNSS receiver. However, in practice, quantization errors accumulate, so it is preferable that the reference epoch is provided explicitly. In one embodiment, the ephemeris server 101 provides at least the GPS week of the reference epoch to the GNSS receiver.

[0039] In one embodiment, the ephemeris server 101 calculates the estimated pseudorange r ~may be monitored. For example, in GPS, the C / A code has 1023 chips transmitted over 1 millisecond. Thus, with a pseudorange prediction threshold of 0.25 milliseconds, the code delay is expected to be within 1 / 4 of the 1023 possible delays. In general, a pseudorange prediction threshold of 0.25 milliseconds is valid for months, as is the 100 Hz Doppler threshold for MEO satellites. In such a situation, the LK ephemeris generated by the method of the present invention provides an adequate pseudorange estimate. However, for lower pseudorange prediction thresholds (e.g., 0.02 milliseconds), the validity period is much shorter (e.g., days). With such a shortened validity period, the estimate A of the length of the history database of the semimajor axis may be too long to justify the pseudorange prediction threshold. ~ However, in this case, the square of the ephemeris parameter √A from the latest system update is used to estimate the length A ~ may be used in the LK ephemeris as AF0. Pseudorange estimates above 10 km should also include the contributions of the satellite clock bias (AF0) and clock drift (AF1).

[0040] Because the orbits of GNSS satellites are not perfectly predictable, the quality of altitude, pseudorange, and Doppler estimates based on the LK ephemeris will inevitably degrade over time. Therefore, according to one embodiment of the present invention, the ephemeris server 101 monitors these predictions. When the Doppler or pseudorange estimation error exceeds a corresponding preset threshold for a satellite, the ephemeris server 101 updates the LK ephemeris for that satellite.

[0041] To support its work, the ephemeris server 101 maintains a real-time database of LK ephemeris organized as "snapshots". Each snapshot corresponds to the set of LK ephemeris last generated for a satellite supported by the ephemeris server 101 (the supported satellites may be selected from multiple GNSSs). In one embodiment, the GNSS receiver requests the last snapshot associated with a specified time (the specified time is expressed, for example, as a UTC time). The GNSS receiver may also request a bitstream encoding an update from a specified snapshot (perhaps the snapshot currently implemented in the GNSS receiver) to the last snapshot.

[0042] In one embodiment, each snapshot is tagged with a timestamp. Similarly, each LK ephemeris is tagged with a timestamp in the form of a sequence number. The sequence number may be an integer t that starts at initialization (e.g., t=0 at 00:15 on January 1, 2017) and increments by one every reevaluation time (e.g., every UTC time). These sequence numbers thus label successive epochs of one UTC time. In this specification, a snapshot at time t is denoted as s(t) and the LK ephemeris of satellite j (j=1,...,n) created at time t is denoted as keph(j,t). Initially, i.e., at initialization, the ephemeris server 101 creates a snapshot s(0) from the last system update of all monitored satellites. Thus, snapshot s(0) contains the LK ephemeris keph(0,0), keph(1,0),..., keph(n,0).

[0043] At the next re-evaluation time (i.e., t=1), the ephemeris server 101 determines which of the LK ephemeris keph(0,0), keph(1,0), ..., keph(n,0) in the snapshot s(0) needs updating based on the evaluation of the update criteria for each satellite. The ephemeris server 101 creates a new LK ephemeris only if the update criteria are met. For example, if the LK ephemeris keph(0,0) and keph(25,0) need updating at time t=1, the ephemeris server 101 creates the LK ephemeris keph(0,1) and keph(25,1). The ephemeris server 101 creates a new snapshot at the re-evaluation time only if at least one LK ephemeris needs updating. Thus, snapshot s(1) contains the LK ephemeris keph(0,1), keph(1,0), . . . , keph(24,0), keph(25,1), keph(26,0), . . . , keph(n,0). If no long-lasting Kepler ephemeris exists in snapshot s(0), then ephemeris server 101 does not create snapshot s(1). This sequence of actions is repeated at every re-evaluation time. Note that in this embodiment, both snapshots and LK ephemeris are indexed by their respective creation times.

[0044] As described above, the update criteria evaluates the difference in magnitude between the estimated pseudorange Doppler or altitude obtained using the latest system update and the corresponding estimated pseudorange Doppler or altitude obtained using the LK ephemeris. If the difference exceeds a preset threshold, the update criteria is met. In one embodiment, at each re-evaluation time, the ephemeris server 101 checks this update criteria for each satellite under observation at each of approximately 100 locations located around the world. If the update criteria for a satellite is met at one or more of the 100 locations, a new LK ephemeris is generated for the satellite.

[0045] However, because the bandwidth of devices 102-1 and 102-n is limited, each device receives updates to its on-board LK ephemeris only if it requests an update from the ephemeris server 101. To reduce the number of terms used in this detailed description, the collection of LK ephemeris in a device is also referred to as a "snapshot." In some embodiments, because work is not coordinated between the ephemeris server and the devices in the system 100 (e.g., the server restores a previous ephemeris to a current snapshot for any of several reasons, as described below), the sequence number of the LK ephemeris on the ephemeris server may be smaller than the sequence number of the corresponding LK ephemeris in the device. In this case, the snapshots on the ephemeris server 101 and the snapshots on the devices need not have the same collection of LK ephemeris, even if they have the same sequence number.

[0046] With the update request, the device sends the timestamp (i.e., sequence number) associated with its last snapshot to the ephemeris server 101. The ephemeris server 101 then compares the received sequence number with the sequence numbers of each LK ephemeris in the current snapshot. The ephemeris in the ephemeris server's 101 current snapshot that have a sequence number greater than the received sequence number are designated for the requested update. Based on this comparison, the ephemeris server 101 creates and sends to the requesting device a bitstream that updates those designated ephemeris. For example, assume that the device's snapshot s(25) contains the LK ephemeris keph(0,24), keph(1,24),...,keph(24,24), keph(25,24), keph(26,24),...,keph(n,24) and the ephemeris server 101 has a current snapshot s(27) containing the LK ephemeris keph(0,24), keph(1,24),...,keph(24,24), keph(25,27), keph(26,23),...,keph(n,24), and the device sends an update request at time t=27. The device's update request includes the sequence number 25. Upon receiving the update request, the ephemeris server 101 determines that only the LK ephemeris keph(25,27) in the current snapshot s(27) has a sequence number greater than the sequence number in the update request. Therefore, the device needs a bitstream to update only the LK ephemeris keph(25,24) to keph(25,27). The device uses the bitstream to create a snapshot s(27) that contains the LK ephemeris keph(0,24), keph(1,24), . . . , keph(24,24), keph(25,27), keph(26,24), . . . , keph(n,24).

[0047] In ephemeris server 101, the sequence numbers may have any suitable bit length (e.g., 29 bits, as in the case of GPS time). However, in some embodiments, due to limited communication bandwidth and other reasons, the sequence numbers of some of devices 102-1 through 102-n may be implemented with a shorter bit length than the sequence numbers of ephemeris server 101. Naturally, the sequence numbers of such devices will "roll over" more frequently than the sequence numbers of ephemeris server 101. In other words, the sequence numbers of the devices may be modulo-2 m (m is the bit length). When comparing the sequence number (e.g., A) of the LK ephemeris in the snapshot with the sequence number (e.g., B) in the update request, the ephemeris server 101 multiplies B by 0 modulo-2. m Specifically, B is mapped to C, and B<2 m-1 If so, take value B; otherwise take value (2 m-1 -B). The sequence number of the LK ephemeris in the snapshot of the ephemeris server 101 is greater than the sequence number in the update request if (AC)>0.

[0048] At certain times, the ephemeris server 101 needs to be reset to recover from the interruption in processing. The recovery process involves initializing a new server to regenerate all LK ephemeris and replace the server that stopped processing. Such an approach is not practical because it would result in the GNSS receivers of the devices 102-1 to 102-n updating all snapshots such that the sequence numbers of substantially all LK ephemeris in the new server's snapshot are higher than those in the device's snapshot. The resulting workload would overwhelm the communication bandwidth of the system 100 (too much workload for the communication bandwidth).

[0049] The present invention provides a fast and cost-effective recovery process. In some embodiments, the real-time database of the ephemeris server 101 can be recovered from an off-site archive. Once the archived database is restored, the recovery process regenerates the restored LK ephemeris that became invalid. If the interruption in processing is short, the bandwidth required to process subsequent update requests from the devices 102-1 to 102-n is entirely acceptable. For example, if a snapshot of the current epoch can be restored from the archive, and the restoration is completed before the next epoch (i.e., the next UTC hourly re-evaluation time), the interruption in processing is minimized.

[0050] According to one embodiment of the present invention, the ephemeris server 101 also records the time of each system update if that system update is used to generate the LK ephemeris. With this approach, even if one or more snapshots are lost (either because they are unrecoverable or because the interruption in processing spans one or more re-evaluation times), all snapshots prior to the interruption in processing can be recreated following the restored snapshots. Snapshots lost during the interruption in processing can be recreated using all system updates that occurred during the interruption, which may be available from a source external to the system 100.

[0051] According to one embodiment of the present invention, the ephemeris server 101 also recovers by generating a special snapshot ("reference snapshot") from a previous system update (e.g., the current system update 24 UTC hours before the processing interruption). The LK ephemeris from the reference snapshot is not used to update the LK ephemeris of devices 102-1 to 102-n. For example, at time t=t^, a reference snapshot s(*) is created from the previous system update containing LK ephemeris keph(0,*), keph(1,*), ..., keph(n,*). Then, at t=t^+p, i.e., at the re-evaluation time of p, the respective update criteria are met and the LK ephemeris keph(25,*) and keph(26,*) are updated, and the snapshot s(t^+p) contains the LK ephemeris keph(0,*), keph(1,*), ···, keph(24,*), keph(25,t^+p), keph(26,t^+p), ···, keph(n,*). During the epoch t=t^+p, the LK ephemeris of the satellites 25, 26 are updated at the requesting device due to the update request received at the ephemeris. The remaining LK ephemeris are replaced in the normal course according to the respective update criteria at the subsequent re-evaluation time, and the corresponding LK ephemeris of the devices 101-1 to 101-n can be updated. In this way, the limited bandwidth caused by the recovery of the process is not overwhelmed. In some embodiments, rather than selecting the current system update at one reference time for all LK ephemeris of the reference snapshot, the LK ephemeris for each satellite may be generated by using a different reference time (perhaps selected randomly).

[0052] Admittedly, the recovery method of the present invention may result in performance degradation in some of the devices 102-1 to 102-n (e.g., a device may need to use an outdated LK ephemeris until the corresponding LK ephemeris from the reference snapshot is replaced in the normal course of events), but the recovery method of the present invention ensures that the system recovers gracefully over time.

[0053] According to one embodiment of the present invention, a bit stream for LK ephemeris updates has a header portion and a body portion. The header portion contains a 15-bit "Data Issue Ephemeris (IODE)" and an Identifier (SID) that lists the satellites for which the LK ephemeris has been updated. The IODE contains the sequence number of the update. The SID contains four 1-bit GNSS identification flags indicating (in order) GPS, BDS, GAL, and QZSS. If only one of the four GNSS identification flags is set, the next 8-bit word is an index into a list of satellites in the identified constellation. Otherwise, a satellite flag map for each GNSS that contains LK ephemeris follows in the order of the GNSS identification flags. If the GPS flag is set, the satellite map contains 31 flags, with each set flag representing one satellite that contains LK ephemeris. The satellites are represented in the order of their pseudorandom code index ("PRN ID"). Similarly, for BDS, GAL, and QZSS, the respective satellite flag maps have 37 bits, 36 bits, and 8 bits, respectively.

[0054] The body of the bit stream is a consecutive list of LK ephemeris (i.e., orbit and clock parameter values) according to the order of the flags set in the satellite flag map in the header. Figure 2 is a table showing the fields of the LK ephemeris according to one embodiment of the present invention. e ) flag is not set, the corresponding "week" field or "Ω e Note that the "Orbit Type" field does not appear in the bitstream. In some embodiments, the orbit type of any of the identified satellites (i.e., MEO, GEO, or GSO) is known, so the "Orbit Type" field is omitted.

[0055] In some embodiments, the ephemeris server 101 determines whether to set a health flag in the LK ephemeris to control the frequency of updates.

[0056] In some embodiments, the current snapshot is pre-installed in each GNSS receiver before it becomes operational. The current snapshot may be installed in each GNSS receiver when it begins operation in the system.

[0057] The format of each LK ephemeris (e.g., fields and their respective bit lengths) is determined empirically. According to one embodiment, 365 UTC (Coordinated Universal Time) days of actual system updates are collected and used in the simulation. The first 70 days of data are used to adjust the bit length of each field of the LK ephemeris. For example, the longer the bit length, the more accurate the Kepler parameter values. The more sensitive the update criteria are to that Kepler parameter, the longer the bit length will be required. Due to the large number of parameters in the LK ephemeris, a significant amount of trial and error and educated guesses are required to adjust the LK ephemeris format to obtain the desired bit length and high performance (i.e., requiring relatively infrequent updates).

[0058] After the desired LK ephemeris format is obtained, the remaining 295 UTC days of data are used for 31 satellites that update their LK ephemeris according to one embodiment of the present invention, as described above. Every 1200 UTC seconds, the ephemeris server evaluates the Doppler update criteria for all satellites at 100 randomly selected locations around the world. In this simulation, the Doppler criterion for each satellite is a 90 Hz threshold. If any of the evaluated update criteria exceed the threshold, an LK ephemeris is generated for the next snapshot.

[0059] In one 365 UTC day simulation using the LK ephemeris format in Figure 2, several LK ephemeris did not expire. The most frequently updated satellite had three updates. A total of 41 updates were required in the final 295 UTC day period of the simulation.

[0060] The second simulation uses a system update of 500 UTC days and various pseudorange update criteria. The results were consistent with the hypothesis that higher update frequencies result from narrower pseudorange thresholds (e.g., 0.25 ms vs. 0.02 ms). In this simulation, a Doppler threshold of 50 Hz was used, but this did not appear to have a substantial effect on pseudorange performance (i.e., increasing the 50 Hz threshold did not result in a significant decrease in update frequency under each pseudorange threshold).

[0061] In one embodiment ("Strategy 1"), the ephemeris server 101 does not send a bitstream for updating unless the number of LK ephemeris contained in the bitstream exceeds a predetermined number (eg, 5).

[0062] In another embodiment ("Strategy 2"), the wide and narrow pseudorange thresholds are monitored simultaneously, where the narrow pseudorange threshold is the product of the wide pseudorange threshold, with a scale factor less than 1.0. In this approach, if the update criteria based on the wide pseudorange threshold is met for any satellite, the LK ephemeris is updated for the satellites that meet the update criteria based on the narrow pseudorange threshold. Figure 3 shows the number of updates and the average length per bit stream from various simulation results for Strategy 1, Strategy 2, or neither strategy ("Current Strategy"), respectively. For Strategy 2, various scale factors were simulated. The simulations were performed using ephemeris data from 56 satellites from GPS, GAL, BDS, and QZSS.

[0063] The above detailed description is provided to illustrate certain embodiments of the present invention and is not intended to limit the present invention. Numerous variations and modifications are possible within the scope of the present invention, which is set forth in the appended claims.

Claims

1. An ephemeris server, A processor; a first communication interface connected to a wide area communication network; A second communication interface; A real-time database; The processor, (a) (i) obtaining broadcast ephemeris information by accessing a source of broadcast information on the wide area communication network using the first communication interface, the broadcast ephemeris information relating to satellites of at least one GNSS; (ii) extracting orbit information for an orbit of each of the satellites from the broadcast ephemeris information; and (iii) creating revised orbit information for each of the satellites from the extracted orbit information and storing the revised orbit information in the real-time database; (b) updating the revised orbit information in the real-time database when an update criterion based on an estimated error between parameter values ​​calculated using the broadcast ephemeris information and parameter values ​​calculated using the revised orbit information is met at each of a plurality of designated times; (c) providing the updated revised orbit information to each of a plurality of devices via the second communications interface, each of the devices having a GNSS receiver capable of processing broadcast signals of the satellites using the revised orbit information; The calculated parameter values ​​are one or more of altitude, pseudorange, and Doppler.

2. The ephemeris server of claim 1 , wherein the corrected orbit information is provided to the device upon request.

3. The ephemeris server of claim 1 , wherein the second communication interface accesses a low power wide area communication network.

4. The ephemeris server of claim 3 , wherein the low-power wide area communication network is LoRa-based.

5. The ephemeris server of claim 1 , wherein the revised orbit information for each of the satellites is not updated if the update criteria are not met.

6. The ephemeris server of claim 1 , wherein the revised orbital information includes Kepler ephemeris information for each of the satellites.

7. The ephemeris server of claim 6 , wherein the Kepler ephemeris information includes an estimate of the semimajor axis of one of the satellites.

8. The ephemeris server of claim 7 , wherein the semi-major axis is estimated using the mean motion of the satellites.

9. The ephemeris server of claim 8 , wherein the mean motion is modeled by a linear function of time.

10. The ephemeris server of claim 6 , wherein the Kepler ephemeris information includes a parameter value related to the mean anomaly of the orbit of one of the satellites.

11. The ephemeris server of claim 6 , wherein the Kepler ephemeris information further includes an estimate of an ascending node longitude associated with an orbital plane of one of the satellites.

12. 2. The ephemeris server of claim 1, wherein the corrected orbit information is communicated to one of the devices in a bit stream relating to only the corrected orbit information that the device does not already have.

13. The ephemeris server of claim 12 , wherein the bitstream includes the corrected orbit information for two or more of the satellites.

14. 2. The ephemeris server of claim 1, wherein the update criteria include a first performance criterion and a second performance criterion, (i) at each specified time, the update criteria is considered to be met only if at least one of the satellites satisfies the first performance criterion, and (ii) when the update criteria is considered to be met, the corrected orbit information of the orbit information of the satellite that satisfies the second performance criterion is updated.

15. The ephemeris server of claim 1 , wherein the designated times occur at regular time intervals.

16. 2. The ephemeris server of claim 1, wherein copies of the real-time database at various times are stored at one or more locations remote from the ephemeris server, thereby allowing the ephemeris server to be restored to a previous state.

17. 17. The ephemeris server of claim 16, further comprising: recording in said real-time database a creation time associated with each phase of creation of said corrected orbital information to enable said real-time database to be restored to a desired state subsequent to said previous state.

18. 18. The ephemeris server of claim 17, wherein the real-time database is restored by creating current corrected orbital information at a selected previous time as a reference set for the corrected orbital information, and the corrected orbital information in the reference set is provided to the device only after such corrected orbital information is updated after the selected previous time.

19. 1. A method for providing satellite ephemeris information from at least one GNSS at an ephemeris server, comprising: (a) (i) obtaining broadcast ephemeris information by accessing a source of broadcast information on a wide area communication network; (ii) extracting orbital information for an orbit of each of said satellites from said broadcast ephemeris information; and (iii) creating revised orbital information for each of said satellites from said extracted orbital information and storing the revised orbital information in a real-time database; (b) updating the revised orbit information in the real-time database when an update criterion based on an estimated error between parameter values ​​calculated using the broadcast ephemeris information and parameter values ​​calculated using the revised orbit information is met at each of a plurality of designated times; (c) providing updated, revised orbital information to each of a plurality of devices, each of the devices having a GNSS receiver capable of processing broadcast signals of the satellites using the revised orbital information; The method, wherein the calculated parameter values ​​are one or more of altitude, pseudorange, and Doppler.

20. The method of claim 19 , wherein the revised trajectory information is provided to the device on request.

21. 20. The method of claim 19, wherein the device and the ephemeris server communicate over a low power wide area communication network.

22. 22. The method of claim 21, wherein the low power wide area communication network is LoRa based.

23. 20. The method of claim 19, wherein the revised orbital information for each of the satellites is not updated if the update criteria is not met.

24. 20. The method of claim 19, wherein the revised orbital information includes Kepler ephemeris information for each of the satellites.

25. 25. The method of claim 24, wherein the Kepler ephemeris information includes an estimate of the semimajor axis of one of the satellites.

26. 26. The method of claim 25, wherein the semi-major axis is estimated using a mean motion of the satellite.

27. 27. The method of claim 26, wherein the mean motion is modeled by a linear function of time.

28. 25. The method of claim 24, wherein the Kepler ephemeris information includes a parameter value related to the mean anomaly of the orbit of one of the satellites.

29. 25. The method of claim 24, wherein the Kepler ephemeris information further includes an estimate of an ascending node longitude associated with an orbital plane of one of the satellites.

30. 20. The method of claim 19, wherein the revised orbit information is communicated to one of the devices in a bitstream that pertains only to revised orbit information that the device does not already possess.

31. 31. The method of claim 30, wherein the bitstream includes the revised orbit information for two or more of the satellites.

32. 20. The method of claim 19, wherein the update criteria include a first performance criterion and a second performance criterion, (i) at each designated time, the update criterion is considered to be met only if at least one of the satellites meets the first performance criterion, and (ii) when the update criterion is considered to be met, the revised orbit information of the orbit information of the satellites that meet the second performance criterion is updated.

33. 20. The method of claim 19, wherein the designated times occur at regular time intervals.

34. 20. The method of claim 19, wherein copies of the real-time database at various times are stored at one or more locations remote from the ephemeris server, thereby allowing the ephemeris server to be restored to a previous state.

35. 25. The method of claim 24, wherein the ephemeris server further records in the real-time database a creation time associated with each phase of creation of the corrected orbital information to enable restoring the real-time database to a desired state subsequent to the previous state.

36. 36. The method of claim 35, wherein the ephemeris server restores the real-time database by creating the current corrected orbital information at a selected previous time as a reference set for the corrected orbital information, and the corrected orbital information in the reference set is provided to the device only after such corrected orbital information is updated after the selected previous time.

Citation Information

Patent Citations

  • Methods and devices for generating / distributing satellite tracking information

    JP2004529032A

  • Method and system for ephemeris extension for GNSS application

    JP2008003092A

  • Prediction refresh method for ephemeris extensions

    JP2008191158A

  • Long-term compact satellite model

    JP2013040790A

  • Method and apparatus in standalone positioning without broadcast ephemeris

    US20080111738A1