Global navigation satellite system (GNSS) and low-orbit satellite constellation data processing method and device
Through the comprehensive processing of satellite-based GNSS receiver and regional ground station data, the application scenario restriction of GNSS and LEO satellite orbits and clock difference solution is solved, high-precision orbits and clock difference data solution is realized, and the application is expanded The scenario also reduces the dependence on the number of ground station distributions.
Patent Information
- Application Number
- CN202310602095.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-25
- Publication Date
- 2024-11-26
AI Technical Summary
In the prior art, ground stations cannot be effectively set up globally, resulting in limited application scenarios for high-precision orbits and clock difference solutions for Global Satellite Navigation System (GNSS) and Low Orbit Satellites (LEO Satellites).
GNSS satellite observation data, LEO satellite inter-satellite link observation data and regional ground station surveying data are obtained through a satellite-based GNSS receiver. Combined with ground station location information, high-precision solution of GNSS satellites and LEO satellite orbits and clock difference data is realized. .
The application scenarios of high-precision orbit and clock difference solutions of GNSS satellites and LEO satellites have been expanded, reducing the dependence on the number of ground stations distribution, and improving the understanding of calculation accuracy and widespread application.
Smart Images

Figure CN119024373A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of satellite communication technology, and in particular to a method and device for processing global satellite navigation system GNSS and low-orbit satellite constellation data. Background Art
[0002] The position accuracy of Low Earth Orbit (LEO) satellites will directly determine the service performance of large low-orbit satellite constellations. In related technologies, the orbit determination of Global Navigation Satellite System (GNSS) satellites is usually based on the observation data obtained by regional ground stations from GNSS observations. When the station position of the regional ground station is known, the orbit and clock error data of the GNSS satellite are solved by double difference or non-difference methods. For the orbit determination of LEO satellites, the received GNSS satellite signals are generally parsed by an onboard GNSS receiver. When the orbit and clock error data of the GNSS satellite are known, the orbit and clock error data of the LEO satellite are solved. Therefore, in order to obtain the orbit and clock error data of the LEO satellite, the orbit and clock error data of the high-precision GNSS satellite are required as a prerequisite. The high-precision orbit and clock error data of the GNSS satellite requires the extensive installation of ground stations to improve the solution accuracy.
[0003] In the related technology, if ground stations cannot be widely set up around the world, high-precision orbit and clock error solutions for GNSS satellites and LEO satellites cannot be effectively achieved, resulting in limited application scenarios for high-precision orbit and clock error solutions for GNSS satellites and LEO satellites. Summary of the invention
[0004] The present disclosure aims to solve one of the technical problems in the related art at least to some extent.
[0005] To this end, the present disclosure proposes a global satellite navigation system GNSS and low-orbit satellite constellation data processing method, device, communication equipment, non-transitory computer-readable storage medium storing computer instructions, and computer program product, which can effectively expand the application scenarios of high-precision orbit and clock error solutions of GNSS satellites and LEO satellites.
[0006] A method for processing global satellite navigation system GNSS and low-orbit satellite constellation data proposed in an embodiment of the first aspect of the present disclosure, the global satellite navigation system GNSS includes: GNSS satellites, the low-orbit satellite constellation includes: a first low-orbit earth LEO satellite, the first LEO satellite is equipped with an onboard GNSS receiver; the method includes: obtaining onboard GNSS observation data obtained by the onboard GNSS receiver observing the GNSS satellite; obtaining LEO satellite inter-satellite link observation data related to the first LEO satellite; obtaining station GNSS observation data obtained by a regional ground station observing the GNSS satellite; obtaining station LEO satellite observation data obtained by a regional ground station observing the first LEO satellite; and determining the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station.
[0007] A global satellite navigation system GNSS and low-orbit satellite constellation data processing device proposed in an embodiment of the second aspect of the present disclosure, the global satellite navigation system GNSS includes: a GNSS satellite, the low-orbit satellite constellation includes: a first low-orbit earth LEO satellite, the first LEO satellite is equipped with an onboard GNSS receiver; the device includes: a satellite data acquisition module, used to obtain onboard GNSS observation data obtained by the onboard GNSS receiver observing the GNSS satellite, the station GNSS observation data obtained by the regional ground station observing the GNSS satellite, and the station LEO satellite observation data obtained by the regional ground station observing the first LEO satellite; an inter-satellite data acquisition module, used to obtain LEO satellite inter-satellite link observation data related to the first LEO satellite; a data processing module, used to determine the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station.
[0008] The communication device proposed in the third aspect embodiment of the present disclosure includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the global satellite navigation system GNSS and low-orbit satellite constellation data processing method proposed in the first aspect embodiment of the present disclosure is implemented.
[0009] The fourth aspect embodiment of the present disclosure proposes a non-temporary computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the global satellite navigation system GNSS and low-orbit satellite constellation data processing method proposed in the first aspect embodiment of the present disclosure.
[0010] The fifth aspect embodiment of the present disclosure proposes a computer program product. When the instructions in the computer program product are executed by a processor, the global satellite navigation system GNSS and low-orbit satellite constellation data processing method proposed in the first aspect embodiment of the present disclosure is executed.
[0011] The present invention proposes a global satellite navigation system GNSS and low-orbit satellite constellation data processing method, apparatus, communication equipment, non-transitory computer-readable storage medium storing computer instructions, and computer program product. By acquiring onboard GNSS observation data obtained by an onboard GNSS receiver observing GNSS satellites, LEO satellite inter-satellite link observation data related to a first LEO satellite, station GNSS observation data obtained by a regional ground station observing GNSS satellites, and station LEO satellite observation data obtained by a regional ground station observing the first LEO satellite, the orbit and clock error data of the GNSS satellite and / or the first LEO satellite are determined based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station, thereby effectively expanding the application scenarios of high-precision orbit and clock error solution of GNSS satellites and LEO satellites.
[0012] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The above and / or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:
[0014] Figure 1 A schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;
[0015] Figure 2 It is a flowchart of a method for processing data of a global satellite navigation system GNSS and a low-orbit satellite constellation provided by an embodiment of the present disclosure;
[0016] Figure 3 It is a flowchart of another method for processing global satellite navigation system GNSS and low-orbit satellite constellation data provided by an embodiment of the present disclosure;
[0017] Figure 4 is a flowchart of a method for processing global satellite navigation system GNSS and low-orbit satellite constellation data in an embodiment of the present disclosure;
[0018] Figure 5 is a flowchart of a method for processing global satellite navigation system GNSS and low-orbit satellite constellation data provided by another embodiment of the present disclosure;
[0019] Figure 6 It is a flowchart of another method for processing global satellite navigation system GNSS and low-orbit satellite constellation data provided by an embodiment of the present disclosure;
[0020] Figure 7 is a schematic diagram of the orbit determination process in an embodiment of the present disclosure;
[0021] Figure 8 This is a schematic diagram of the clock error data solution process in the embodiment of the present disclosure;
[0022] Fig. 9 This is a schematic diagram of the clock error data solution process in the embodiment of the present disclosure;
[0023] Fig.10 It is a structural schematic diagram of a global satellite navigation system GNSS and low-orbit satellite constellation data processing device proposed in an embodiment of the present disclosure;
[0024] Fig.11 A block diagram of an exemplary communication device suitable for implementing embodiments of the present disclosure is shown. DETAILED DESCRIPTION
[0025] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present disclosure, and are not to be construed as limitations of the present disclosure. On the contrary, the embodiments of the present disclosure include all changes, modifications, and equivalents that fall within the spirit and connotation of the appended claims.
[0026] In order to better understand a method for processing global satellite navigation system GNSS and low-orbit satellite constellation data according to an embodiment of the present disclosure, the communication system to which the embodiment of the present disclosure is applicable is first described below.
[0027] See also Figure 1 , Figure 1 The following is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include but is not limited to a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown includes a network device 101 and a terminal device 102 as an example.
[0028] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long term evolution (LTE) system, fifth generation (5G) mobile communication system, 5G new radio (NR) system, or other future new mobile communication systems.
[0029] The network device 101 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the network device.
[0030] The network device provided by the embodiments of the present disclosure may be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit. The CU-DU structure may be used to split the protocol layer of a network device, such as a base station, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU.
[0031] The terminal device 102 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device may also be referred to as a terminal device (terminal), a user equipment (UE), a mobile station (MS), a mobile terminal device (MT), etc. The terminal device may be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), etc.
[0032] The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.
[0033] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. A person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.
[0034] The execution subject of the embodiments of the present disclosure may be any type of satellite, such as a GNSS satellite, a LEO satellite, or any other possible satellite; or, the execution subject of the embodiments of the present disclosure may be any type of network device, such as a base station or a core network device; or, the execution subject in the embodiments of the present disclosure may also be a terminal device or a third-party device; of course, the execution subject in the embodiments of the present disclosure may also be any large-scale system platform, satellite monitoring equipment, etc. with data processing and solving functions, without limitation.
[0035] The global satellite navigation system GNSS and low-orbit satellite constellation data processing method and device provided by the present invention are introduced in detail below in conjunction with the accompanying drawings.
[0036] In the embodiment of the present disclosure, the low-orbit satellite may also be referred to as a LEO satellite, and the first low-orbit satellite may also be referred to as a first LEO satellite, without limitation.
[0037] Figure 2 It is a flow chart of a method for processing global satellite navigation system GNSS and low-orbit satellite constellation data provided by an embodiment of the present disclosure.
[0038] The global satellite navigation system GNSS in the embodiment of the present disclosure may include multiple GNSS satellites. The low-orbit satellite constellation may be, for example, a large low-orbit satellite constellation. The low-orbit satellite constellation may include: multiple low-orbit earth LEO satellites. The first LEO satellite may refer to any LEO satellite among the multiple low-orbit earth LEO satellites. The first LEO satellite may be equipped with a satellite-borne GNSS receiver, and there is no restriction on this.
[0039] In the related art, if ground stations cannot be widely set up around the world, high-precision orbit and clock error solutions for GNSS satellites and LEO satellites cannot be effectively realized, resulting in limited application scenarios for high-precision orbit and clock error solutions for GNSS satellites and LEO satellites. The embodiment disclosed herein is precisely to solve the above-mentioned technical problems in the related art. The LEO satellite can be regarded as a space mobile monitoring station to achieve global tracking of GNSS satellite signals, thereby not relying on the number of ground stations distributed. The orbit and clock error data of the GNSS satellite and / or the first LEO satellite can be solved by referring to the onboard GNSS receiver observation data of the LEO satellite, the station observation data of a small number of regional ground stations, and the location information of the regional ground station.
[0040] like Figure 2 As shown, the method for processing data of the global satellite navigation system GNSS and the low-orbit satellite constellation may be to process data of the global satellite navigation system GNSS and the low-orbit satellite constellation using a regional ground station. The method may include but is not limited to the following steps:
[0041] S201: Acquire onboard GNSS observation data obtained by an onboard GNSS receiver observing GNSS satellites.
[0042] In some embodiments, a satellite-borne GNSS receiver may be deployed in the first LEO satellite, and the satellite-borne GNSS receiver may be capable of tracking and monitoring other satellite signals, without limitation.
[0043] The GNSS satellite may be observed based on the onboard GNSS receiver deployed in the first LEO satellite, and the data obtained by the observation may be referred to as onboard GNSS observation data.
[0044] In some embodiments, the satellite-borne GNSS observation data may also be referred to as observation data of a LEO satellite on a GNSS satellite, without limitation.
[0045] In some embodiments, the onboard GNSS observation data may include data obtained from observing GNSS satellite signals, and may include data in any possible form that can be observed, such as GNSS satellite position data, GNSS satellite signal strength, signal sending and / or receiving time, telegrams broadcast by GNSS satellites, pseudoranges, carrier phase observations, etc., without limitation.
[0046] In some embodiments, considering that the onboard GNSS observation data may be affected by the atmospheric ionosphere, a dual-frequency GNSS observation mode may be used during orbit determination (for example, dual-frequency combined observations may be performed on frequency points with large frequency differences such as B1 and B2, or L1 and L2) to eliminate the influence of first-order ionospheric terms and ignore the influence of higher-order terms with smaller magnitudes. When orbit determination is performed on the first LEO satellite, the onboard GNSS receiver thereon may be configured to observe the GNSS satellite based on the dual-frequency GNSS observation mode to obtain onboard GNSS observation data, and there is no restriction on this.
[0047] In some embodiments, the number of GNSS satellites may be one or more. For example, the onboard GNSS observation data obtained by a onboard GNSS receiver observing one GNSS satellite may be obtained; or, the onboard GNSS observation data obtained by a onboard GNSS receiver observing multiple GNSS satellites may be obtained. There is no limitation on this.
[0048] In some embodiments of the present disclosure, a device that executes a global satellite navigation system GNSS and a low-orbit satellite constellation data processing method can obtain onboard GNSS observation data forwarded by a regional ground station, wherein when a first LEO satellite is visible relative to the regional ground station, the regional ground station receives the onboard GNSS observation data sent by the first LEO satellite based on observations by an onboard GNSS receiver, or when the first LEO satellite is not visible relative to the regional ground station, the regional ground station receives the onboard GNSS observation data of the first LEO satellite forwarded by other LEO satellites, and the other LEO satellites are visible relative to the regional ground station, and the other LEO satellites receive the onboard GNSS observation data sent by the first LEO satellite based on observations by the onboard GNSS receiver, which can effectively improve the number, accuracy and success rate of acquisition of onboard GNSS observation data.
[0049] S202: Acquire LEO satellite inter-satellite link observation data related to the first LEO satellite.
[0050] The LEO satellite inter-satellite link observation data related to the first LEO satellite refers to the data obtained by the first LEO satellite from observing the inter-satellite link of the adjacent LEO satellite, and there is no restriction on this.
[0051] In some embodiments of the present disclosure, a device that executes the global satellite navigation system GNSS and low-orbit satellite constellation data processing method can also obtain LEO satellite inter-satellite link observation data forwarded by a regional ground station, wherein when the first LEO satellite is visible relative to the regional ground station, the regional ground station receives the LEO satellite inter-satellite link observation data sent by the first LEO satellite, or when the first LEO satellite is not visible relative to the regional ground station, the regional ground station receives the LEO satellite inter-satellite link observation data of the first LEO satellite forwarded by other LEO satellites, and other LEO satellites are visible relative to the regional ground station, and other LEO satellites receive the LEO satellite inter-satellite link observation data sent by the first LEO satellite, which can effectively improve the acquisition accuracy and success rate of the LEO satellite inter-satellite link observation data.
[0052] That is to say, in some embodiments, all data can be transmitted directly to the data processing center through the regional ground station. The data processing center is an optional example of a device that executes the global satellite navigation system GNSS and low-orbit satellite constellation data processing method. All data may include data involved in solving orbit and clock error data, and there is no limitation on this.
[0053] In some embodiments, if the regional ground station forwards the data involved in solving the orbit and clock error data to the data processing center, then in the case that some regional ground station data cannot be directly transmitted to the data processing center, the regional ground station can transmit all the data to the first LEO satellite through the "communication link between the LEO satellite and the regional ground station", the first LEO satellite transmits it to the second LEO satellite through the inter-satellite link, and the second LEO satellite then transmits all the data to the regional ground station that can communicate with the data processing center through the "communication link between the LEO satellite and the regional ground station", and then transmits it to the data processing center. There is no restriction on this.
[0054] In some embodiments, when the first LEO satellite is visible relative to the regional ground station, the data involved in solving the orbit and clock error data (which may include onboard GNSS observation data and LEO satellite inter-satellite link observation data) can be sent by the first LEO satellite to the regional ground station. For example, the data involved in solving the orbit and clock error data can be sent to the regional ground station via the communication link between the first LEO satellite and the regional ground station, and then the regional ground station forwards the data involved in solving the orbit and clock error data to a data processing center. There is no limitation on this.
[0055] In other embodiments, when the first LEO satellite is not visible relative to the regional ground station, the first LEO satellite can send data involved in solving the orbit and clock error data (which may include onboard GNSS observation data and LEO satellite inter-satellite link observation data) to other LEO satellites. If the other LEO satellites are visible relative to the regional ground station, the other LEO satellites can receive the data involved in solving the orbit and clock error data sent by the first LEO satellite, and send the data involved in solving the orbit and clock error data to the regional ground station. The regional ground station will forward the data involved in solving the orbit and clock error data to the data processing center, and there is no restriction on this.
[0056] S203: Acquire station GNSS observation data obtained by the regional ground station from observing the GNSS satellite.
[0057] In some embodiments, GNSS satellites can be observed based on regional ground stations, and the observation data can be called station GNSS observation data. The location information of the regional ground station can be used to describe the location of the regional ground station, without limitation.
[0058] In some embodiments, the station GNSS observation data, satellite-borne GNSS observation data, and LEO satellite inter-satellite link observation data obtained by the regional ground station from observing GNSS satellites can be used together to determine the orbit and clock error data of the GNSS satellite and / or the first LEO satellite, without limitation.
[0059] When there are a small number of regional ground stations, in the embodiments of the present disclosure, GNSS satellites can be observed based on a small number of regional ground stations. The data obtained based on the observation of GNSS satellites by the regional ground stations can be called station GNSS observation data. The station GNSS observation data can be used to participate in the calculation of high-precision GNSS satellite orbit and / or clock error data, and there is no limitation on this.
[0060] In some embodiments, the station GNSS observation data may include data obtained by the regional ground station from observing GNSS satellite signals, and may include any possible form of data that can be observed, such as GNSS satellite position data, GNSS satellite signal strength, signal sending and / or receiving time, telegrams broadcast by GNSS satellites, pseudoranges, carrier phase observations, etc., without limitation.
[0061] In some embodiments, the number of GNSS satellites can be one or more, for example, the station GNSS observation data obtained by the regional ground station on one GNSS satellite can be obtained; or, the station GNSS observation data obtained by the regional ground station on each GNSS satellite can be obtained, or, the station GNSS observation data obtained by the regional ground station on some GNSS satellites in the GNSS constellation can be obtained, and there is no limitation on this.
[0062] S204: Acquire the station LEO satellite observation data obtained by the regional ground station observing the first LEO satellite.
[0063] In some embodiments, the first LEO satellite can be observed based on a regional ground station, and the observation data can be referred to as station LEO satellite observation data. The station LEO satellite observation data can also be referred to as observation data of the first LEO satellite by the regional ground station, without limitation.
[0064] In some embodiments, the station LEO satellite observation data may include data obtained by the regional ground station from observing the first LEO satellite signal, and may include data in any possible form that can be observed, such as the position data of the first LEO satellite, the signal strength of the first LEO satellite, the signal sending and / or receiving time, the signal content of the first LEO satellite, the pseudorange, the carrier phase observation value, etc., without limitation.
[0065] In some embodiments of the present disclosure, if there are multiple GNSS satellites, each GNSS satellite corresponds to onboard GNSS observation data and station GNSS observation data, and the GNSS satellite inter-satellite link observation data related to the GNSS satellite and the station LEO satellite observation data obtained by the regional ground station from observing the first LEO satellite can also be obtained. The first orbital data of the GNSS satellite and the second orbital data of the first LEO satellite are determined based on the GNSS satellite inter-satellite link observation data, onboard GNSS observation data, station GNSS observation data, station LEO satellite observation data, and the position information of the regional ground station, thereby effectively improving the solution accuracy of the first orbital data of the GNSS satellite and the second orbital data of the first LEO satellite when there are multiple GNSS satellites.
[0066] S205: Determine the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station.
[0067] Among them, the orbit and clock error data are used to describe the orbit parameters and clock errors of the GNSS satellite and / or the first LEO satellite. The clock error can be, for example, the clock error of the GNSS satellite or the first LEO satellite relative to the time reference, and there is no limitation on this.
[0068] In some embodiments, the onboard GNSS observation data, the station GNSS observation data, the station LEO satellite observation data, the LEO satellite intersatellite link observation data, and the position information of the regional ground station can be jointly solved to obtain the orbit and clock error data of the GNSS satellite and / or the first LEO satellite, without limitation.
[0069] In some embodiments, if the onboard GNSS observation data is obtained for each GNSS satellite observation, the station GNSS observation data is obtained for each GNSS satellite observation, and the station LEO satellite observation data is obtained for each LEO satellite observation, then the orbit and clock error data of the GNSS satellite can be solved based on the position information of the regional ground station, the onboard GNSS observation data of a LEO satellite, the station GNSS observation data, the onboard GNSS observation data of another LEO satellite, and the station GNSS observation data of another GNSS satellite, without any limitation.
[0070] In some embodiments, the orbit and clock error data of the GNSS satellite and the first LEO satellite can be obtained by jointly calculating the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station, without limitation.
[0071] In some embodiments, the orbit and clock error data of the GNSS satellite and / or the first LEO satellite can also be determined based on multi-source data (including onboard GNSS observation data, station GNSS observation data, station LEO satellite observation data, GNSS satellite inter-satellite link observation data, LEO satellite inter-satellite link observation data, and position information of regional ground stations). For example, the onboard GNSS observation data, station GNSS observation data, station LEO satellite observation data, GNSS satellite inter-satellite link observation data, LEO satellite inter-satellite link observation data, and position information of regional ground stations can be used to construct observation equations, and the orbit and clock error data of the GNSS satellite and / or the first LEO satellite can be obtained based on the joint solution of the observation equations. There is no limitation to this.
[0072] In this embodiment, by obtaining the onboard GNSS observation data obtained by the onboard GNSS receiver observing the GNSS satellite, the LEO satellite inter-satellite link observation data related to the first LEO satellite, the station GNSS observation data obtained by the regional ground station observing the GNSS satellite, and the station LEO satellite observation data obtained by the regional ground station observing the first LEO satellite, the orbit and clock error data of the GNSS satellite and / or the first LEO satellite are determined according to the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station, thereby effectively expanding the application scenarios of high-precision orbit and clock error solution of GNSS satellites and LEO satellites.
[0073] Figure 3 It is a flow chart of another method for processing global satellite navigation system GNSS and low-orbit satellite constellation data provided by an embodiment of the present disclosure.
[0074] like Figure 3 As shown, the method for processing the global satellite navigation system GNSS and low-orbit satellite constellation data may include but is not limited to the following steps:
[0075] S301: Acquire onboard GNSS observation data obtained by an onboard GNSS receiver observing GNSS satellites.
[0076] S302: Acquire LEO satellite inter-satellite link observation data related to the first LEO satellite.
[0077] S303: Acquire station GNSS observation data obtained by the regional ground station observing GNSS satellites, and station LEO satellite observation data obtained by the regional ground station observing LEO satellites.
[0078] For the description of S301 - S303 , please refer to the above embodiment, which will not be repeated here.
[0079] S304: Acquire GNSS satellite inter-satellite link observation data related to the GNSS satellite.
[0080] Among them, the GNSS satellite inter-satellite link observation data related to the GNSS satellite refers to the data obtained by the GNSS satellite from observing the inter-satellite links of the adjacent GNSS satellites, and there is no restriction on this.
[0081] S305: Determine the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the location information of the regional ground station, the GNSS satellite inter-satellite link observation data, and the station LEO satellite observation data.
[0082] In some embodiments, the acquired GNSS satellite inter-satellite link observation data, station LEO satellite observation data, spaceborne GNSS observation data, LEO satellite inter-satellite link observation data, station GNSS observation data, and location information of regional ground stations can be used to jointly solve the orbit and clock error data of the GNSS satellite and / or the first LEO satellite, without limitation.
[0083] In some embodiments of the present disclosure, the first orbital data of the GNSS satellite and the second orbital data of the first LEO satellite can be determined based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the position information of the regional ground station, the GNSS satellite inter-satellite link observation data, and the station LEO satellite observation data; the first clock difference data of the GNSS satellite and the second clock difference data of the first LEO satellite can be determined based on the onboard GNSS observation data, the station GNSS observation data, the position information of the regional ground station, the first orbital data, and the second orbital data, thereby jointly solving the first orbital data and the first clock difference data of the GNSS satellite and the second orbital data of the first LEO satellite, thereby effectively improving the solution accuracy of the orbit and clock difference data of the GNSS satellite and the first LEO satellite.
[0084] The first orbital data is used to describe the orbital parameters of the GNSS satellite, and the second orbital data is used to describe the orbital parameters of the first LEO satellite, and there is no limitation on this.
[0085] Among them, the first clock error data is used to describe the clock error of the GNSS satellite. The first clock error data can be the clock error of the GNSS satellite relative to the time reference. The second clock error data is used to describe the clock error of the target low-orbit satellite. The second clock error data can be the clock error of the target low-orbit satellite relative to the time reference. There is no limitation on this.
[0086] In some embodiments, when determining the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on multi-source data (including onboard GNSS observation data, station GNSS observation data, station LEO satellite observation data, GNSS satellite inter-satellite link observation data, LEO satellite inter-satellite link observation data, and position information of regional ground stations), the multi-source data can be, for example, input into a solution model, which can be pre-trained and have the ability to solve orbit and clock error data, and the multi-source data can be processed based on the solution model to obtain the orbit and clock error data of the GNSS satellite and / or the first LEO satellite, without limitation.
[0087] In other embodiments, when determining the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on multi-source data (including onboard GNSS observation data, station GNSS observation data, station LEO satellite observation data, GNSS satellite inter-satellite link observation data, LEO satellite inter-satellite link observation data, and position information of regional ground stations), the multi-source data can be jointly solved by a "one-step method" to obtain the orbit data of the GNSS satellite and / or the first LEO satellite, and the clock error data of the GNSS satellite and / or the first LEO satellite can be solved epoch by epoch using Kalman filtering, without limitation.
[0088] In some embodiments, the description of the "one-step method" for joint solving of multi-source data can be as follows:
[0089] Specifically, the "one-step method" first establishes the first-order differential motion equations of the low-orbit satellite and the GNSS satellite according to Newton's second law. The LEO satellite can be an optional example of the first LEO satellite in the embodiment of the present disclosure, and there is no limitation on this. The first-order differential motion equation is as follows:
[0090]
[0091] In the formula, r, are the position, velocity, and acceleration vector of the satellite’s (such as a LEO satellite or a GNSS satellite) center of mass, respectively. f represents the force on the satellite (such as a LEO satellite or a GNSS satellite). Assume that the motion state vectors of the LEO satellite and the GNSS satellite are Let the right function vector
[0092] The above formula can be expressed as:
[0093]
[0094] Integrating the above formula, we can get the initial state vector relative to time t0 Integrate to get the state vector X at time t t , that is, the general form of the solution of the above formula is obtained This is a nonlinear equation. After linearizing it, we get:
[0095] X(t)=φ(t,t0)X(t0);
[0096] Among them, φ(t,t0) is called the state transfer matrix.
[0097] In some embodiments, the state transfer matrix can be obtained by integrating the first-order differential motion equations of LEO satellites and GNSS satellites and the variational equations derived therefrom, which represents the connection between the satellite state and the initial conditions at any time, and is used to map the orbital state correction numbers at different times to the initial time, so as to participate in the final parameter estimation. After performing multiple observations, the observation equation is established for the multi-source data according to the above formula, and the satellite state parameters including the high-precision LEO satellite orbit (the high-precision LEO satellite orbit can be an optional example of the second orbit data) and the GNSS satellite orbit (the GNSS satellite orbit can be an optional example of the first orbit data) can be solved by least squares parameter estimation, without limitation.
[0098] In other embodiments, after the orbital data of the GNSS satellite and the first LEO satellite are obtained, the orbit of the GNSS satellite can be solved and predicted with high precision, and the prediction accuracy of the GNSS satellite orbit can be evaluated, and an orbit correction number relative to the GNSS satellite broadcast message can be given, without any limitation.
[0099] like Figure 4 As shown, Figure 4 It is a flow chart of the method for processing GNSS and low-orbit satellite constellation data of the global satellite navigation system in the embodiment of the present disclosure, wherein the regional monitoring station is an optional example of a regional ground station, and the regional monitoring station coordinates are an optional example of the location information of the regional ground station. The ground station observes the GNSS satellite to obtain onboard GNSS observation data, and observes the GNSS intersatellite chain to obtain GNSS satellite intersatellite link observation data. The ground station observes the low-orbit satellite to obtain the station LEO satellite observation data, and observes the low-orbit satellite intersatellite chain to obtain the LEO satellite intersatellite link observation data. The multi-source data can be jointly solved and processed to obtain the orbits of the GNSS satellite and the low-orbit satellite. Then, the orbits of the GNSS satellite and the low-orbit satellite, the regional monitoring station coordinates, the station LEO satellite observation data, and the LEO satellite intersatellite link observation data are combined to obtain the GNSS satellite clock error, the low-orbit satellite clock error, and the regional ground station clock error, without limitation.
[0100] In this embodiment, by obtaining the onboard GNSS observation data obtained by the onboard GNSS receiver observing the GNSS satellite, the LEO satellite inter-satellite link observation data related to the first LEO satellite, the station LEO satellite observation data obtained by the regional ground station observing the LEO satellite, and the station GNSS observation data obtained by the regional ground station observing the GNSS satellite, the orbit and clock error data of the GNSS satellite and / or the first LEO satellite are determined according to the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station, thereby effectively expanding the application scenarios of high-precision orbit and clock error solution of GNSS satellites and LEO satellites. If there are multiple GNSS satellites, each GNSS satellite corresponds to onboard GNSS observation data and station GNSS observation data. The GNSS satellite inter-satellite link observation data related to the GNSS satellite and the station LEO satellite observation data obtained by the regional ground station from observing the first LEO satellite can also be obtained. The first orbit data of the GNSS satellite and the second orbit data of the first LEO satellite are determined based on the GNSS satellite inter-satellite link observation data, onboard GNSS observation data, station GNSS observation data, station LEO satellite observation data, and the position information of the regional ground station. This can effectively improve the solution accuracy of the first orbit data of the GNSS satellite and the second orbit data of the first LEO satellite when there are multiple GNSS satellites.
[0101] In some embodiments of the present disclosure, the first LEO satellite belongs to a plurality of candidate LEO satellites, and each of the plurality of candidate LEO satellites is taken as the first LEO satellite, wherein the number of the first LEO satellites is multiple; or, each of some of the candidate LEO satellites is taken as the first LEO satellite, wherein the number of the first LEO satellite is at least one, thereby enabling the orbit determination solution to effectively adapt to the actual interference situation, thereby improving the practicability of the orbit determination solution.
[0102] That is to say, multiple candidate LEO satellites may be selected as target LEO satellites, wherein the number of target LEO satellites is multiple, or a candidate LEO satellite may be selected from multiple candidate LEO satellites as a target LEO satellite, wherein the number of target LEO satellites is at least one, and there is no limitation on this.
[0103] In some embodiments of the present disclosure, the candidate LEO satellite is equipped with an onboard GNSS receiver and an onboard navigation signal transmitting device; wherein, when each candidate LEO satellite among multiple candidate LEO satellites is used as the first LEO satellite, the onboard GNSS receiver carried by each candidate LEO satellite is in an on-state, and the onboard navigation signal transmitting device is in an on-state, and there is no restriction on this.
[0104] In some embodiments of the present disclosure, the candidate LEO satellites are equipped with onboard GNSS receivers and onboard navigation signal transmitting devices. The onboard GNSS receivers carried by multiple candidate LEO satellites can be maintained in an on-state, and the onboard navigation signal transmitting devices carried by multiple candidate LEO satellites can be maintained in an on-state, so as to use each candidate LEO satellite among the multiple candidate LEO satellites as the first LEO satellite.
[0105] In some embodiments of the present disclosure, the candidate LEO satellite is equipped with an onboard GNSS receiver and an onboard navigation signal transmitting device; wherein, in the case where each candidate LEO satellite in some candidate LEO satellites is used as the first LEO satellite, the onboard GNSS receiver carried by each candidate LEO satellite is in an on-state, and the onboard navigation signal transmitting device is in an off-state; the onboard GNSS receiver carried by the non-reference LEO satellite is in a off-state, and the onboard navigation signal transmitting device is in an on-state, wherein the non-reference LEO satellite is the remaining candidate LEO satellites among multiple candidate LEO satellites except some candidate LEO satellites.
[0106] In some embodiments of the present disclosure, each candidate LEO satellite is equipped with an onboard GNSS receiver and an onboard navigation signal transmitting device. The onboard GNSS receiver carried by the selected candidate LEO satellite can be maintained in an on-state, and the onboard navigation signal transmitting devices carried by the selected candidate LEO satellite can be maintained in an off-state. The onboard GNSS receivers carried by non-reference LEO satellites can be maintained in an off-state, and the onboard navigation signal transmitting devices carried by non-reference LEO satellites can be maintained in an on-state, so that each candidate LEO satellite among some candidate LEO satellites can be used as the first LEO satellite.
[0107] For example, for LEO satellites, since they need to provide navigation enhancement services to ground users, they are equipped with both an uplink antenna for receiving GNSS signals and a downlink antenna for broadcasting navigation signals to the ground. In order to effectively avoid interference with observation when the downlink antenna transmits the same frequency signal as the dual-frequency observation and ensure that effective dual-frequency observation data can be obtained, the embodiments of the present disclosure can also support a transceiver isolation mechanism. Two solutions can be considered: (1) If there is no transceiver interference for all candidate LEO satellites, strategy 1 in Table 1 can be used to complete orbit determination, that is, all candidate LEO satellites participate in joint orbit determination; (2) If transceiver isolation cannot be effectively performed, strategy 2 in Table 1 can be used to complete orbit determination, and some of the candidate LEO satellites among the multiple candidate LEO satellites can be selected as reference satellites (which can be an optional example of the first LEO satellite) for receiving GNSS satellite signals, and the remaining candidate LEO satellites (which can be an optional example of a non-reference LEO satellite) are used for broadcasting navigation enhancement downlink signals, that is, the selected part of the candidate LEO satellites participate in joint orbit determination.
[0108] Table 1
[0109]
[0110] For example, if GNSS and all candidate LEO satellites are used for joint orbit determination, a small number of ground stations distributed regionally are established on the ground to observe GNSS satellites and all candidate LEO satellites (all candidate LEO satellites are regarded as the first LEO satellites), generate station GNSS observation data, station LEO satellite observation data, and simultaneously receive GNSS satellite intersatellite link observation data, LEO satellite intersatellite link observation data, and the onboard GNSS observation data obtained by the onboard GNSS receiver on the first LEO satellite observing the GNSS satellite. Then, the "one-step method" is used to perform multi-source data joint solution. The input and output of the main data are as follows Figure 5 As shown, Figure 5 It is a flow chart of a method for processing global satellite navigation system GNSS and low-orbit satellite constellation data provided by another embodiment of the present disclosure. After the orbits of the GNSS satellite and the first LEO satellite are obtained by solving and predicting the orbit of the GNSS satellite, the prediction accuracy of the GNSS satellite orbit is evaluated, and an orbit correction number relative to the GNSS satellite broadcast message is given.
[0111] exist Figure 5In the embodiment, GNSS satellite inter-satellite link measurement data is an optional example of GNSS satellite inter-satellite link observation data in the embodiment of the present disclosure; GNSS observation data of the regional monitoring station is an optional example of station GNSS observation data of the regional ground station in the embodiment of the present disclosure; low-orbit satellite inter-satellite link measurement data is an optional example of LEO satellite inter-satellite link observation data in the embodiment of the present disclosure; low-orbit satellite observation data of the regional monitoring station is an optional example of station LEO satellite observation data in the embodiment of the present disclosure; low-orbit satellite on-board receiver is an optional example of on-board GNSS receiver in the embodiment of the present disclosure; GNSS observation data of the low-orbit satellite on-board receiver is an optional example of on-board GNSS observation data in the embodiment of the present disclosure; high-precision GNSS satellite orbit is an optional example of first orbit data of GNSS satellite in the embodiment of the present disclosure; high-precision low-orbit satellite orbit is an optional example of second orbit data of the target low-orbit satellite in the embodiment of the present disclosure, and there is no limitation on this.
[0112] Figure 6 It is a flow chart of another method for processing global satellite navigation system GNSS and low-orbit satellite constellation data provided by an embodiment of the present disclosure.
[0113] The global satellite navigation system GNSS in the embodiment of the present disclosure includes: GNSS satellites. The low-orbit satellite constellation can be, for example, a large low-orbit satellite constellation. The low-orbit satellite constellation can include: a first low-orbit earth LEO satellite. The first LEO satellite is equipped with an onboard GNSS receiver. The onboard GNSS receiver can observe the GNSS satellite to obtain onboard GNSS observation data. Each candidate LEO satellite among some candidate LEO satellites is used as the first LEO satellite.
[0114] This embodiment can be applied to the orbit determination mode of "joint orbit determination of the low-orbit satellite constellation, the earth and the satellite based on the reference satellite", that is, when a large low-orbit satellite constellation includes multiple candidate LEO satellites, some candidate LEO satellites are selected to participate in the joint orbit determination of the low-orbit satellite constellation, the earth and the satellite.
[0115] like Figure 6 As shown, the method for processing the global satellite navigation system GNSS and low-orbit satellite constellation data may include but is not limited to the following steps:
[0116] S601: Acquire station LEO satellite observation data obtained by a regional ground station observing a non-reference LEO satellite, wherein the non-reference LEO satellite is a candidate LEO satellite remaining from a plurality of candidate LEO satellites except for some candidate LEO satellites.
[0117] In some embodiments, some of the selected candidate LEO satellites may be referred to as reference LEO satellites, and unselected candidate LEO satellites may be referred to as non-reference LEO satellites, without limitation.
[0118] In some embodiments, the station LEO satellite observation data may be obtained by observing the non-reference LEO satellite by a regional ground station, and there is no limitation to this.
[0119] S602: Acquire inter-satellite link observation data of a reference LEO satellite related to a non-reference LEO satellite.
[0120] Among them, the reference LEO satellite inter-satellite link observation data related to the non-reference LEO satellite refers to the data obtained by the non-reference LEO satellite from observing the inter-satellite link of the adjacent reference LEO satellite, and there is no restriction on this.
[0121] S603: Determine the second orbit data of the non-reference LEO satellite according to the station LEO satellite observation data, the reference LEO satellite inter-satellite link observation data related to the non-reference LEO satellite, and the second orbit data of the first LEO satellite.
[0122] Among them, the second orbit data of the first LEO satellite can be obtained by joint calculation based on the implementation methods in the above embodiments.
[0123] That is to say, the second orbit data of the non-reference LEO satellite can be obtained by calculating the station LEO satellite observation data, the reference LEO satellite intersatellite link observation data, and the second orbit data of the first LEO satellite obtained by the regional ground station observing the non-reference LEO satellite, and there is no restriction on this.
[0124] In some embodiments, when each candidate LEO satellite in some candidate LEO satellites is used as the first LEO satellite, the first LEO satellite may also be referred to as a reference LEO satellite. In this case, the orbit determination strategy adopted is the satellite-ground-satellite joint orbit determination of the low-orbit satellite constellation based on the reference LEO satellite, as illustrated below:
[0125] In some application scenarios, if the uplink and downlink GNSS antenna signals of a candidate LEO satellite are interfered, resulting in the unavailability of GNSS dual-frequency ionospheric observation combined precise orbit determination, and only regionally distributed ground stations are available, a satellite-ground-satellite joint orbit determination strategy based on a reference LEO satellite can be adopted. That is:
[0126] Two candidate LEO satellites are selected as reference LEO satellites on an orbital plane, and the dual-frequency ionosphere-free combined observation data (i.e., an optional example of onboard GNSS observation data) obtained by the onboard GNSS receiver is used to perform orbit determination and obtain high-precision second orbit data of the first LEO satellite.
[0127] The calculated second orbit data of the first LEO satellite is used as a strong constraint to participate in the orbit determination processing of the non-reference LEO satellite, and then the second orbit data of the entire low-orbit satellite constellation is obtained. Figure 7 As shown, Figure 7 : is a schematic diagram of the orbit determination process in the embodiment of the present disclosure, including:
[0128] (a) Using the onboard GNSS observation data obtained from the reference LEO satellite in the low-orbit satellite constellation, the second orbit data of the reference LEO satellite is solved in a "one-step method" to achieve high-precision synchronization of the constellation space reference of the reference LEO satellite to the space reference of the GNSS system.
[0129] (b) Joint orbit determination using ground station observations and LEO intersatellite link measurements. During orbit determination, the second orbit data of the reference LEO satellite calculated in the previous step is strongly constrained, and the second orbit data of the non-reference LEO satellite is calculated using a small number of ground station observations of the non-reference LEO satellite (the observation data of the station LEO satellite obtained by the regional ground station observing the non-reference LEO satellite) and the reference LEO satellite intersatellite link observation data.
[0130] exist Figure 7 In the embodiment of the present disclosure, the GNSS observation data of the regional monitoring station is an optional example of the station GNSS observation data of the ground station in the embodiment of the present disclosure; the LEO satellite inter-satellite link measurement data is an optional example of the LEO satellite inter-satellite link observation data related to the first LEO satellite in the embodiment of the present disclosure; the LEO satellite observation data of the regional ground station is an optional example of the station LEO satellite observation data in the embodiment of the present disclosure; the reference LEO satellite onboard receiver is an optional example of the onboard GNSS receiver in the first LEO satellite in the embodiment of the present disclosure; the GNSS observation data of the reference LEO satellite onboard receiver is an optional example of the onboard GNSS observation data of the onboard GNSS receiver in the embodiment of the present disclosure. an optional example of measurement data; a high-precision GNSS satellite orbit, which is an optional example of the first orbit data of the GNSS satellite in the embodiment of the present disclosure; a high-precision reference LEO satellite orbit, which is an optional example of the second orbit data of the first LEO satellite in the embodiment of the present disclosure; a reference LEO satellite, which is an optional example of the first LEO satellite in the embodiment of the present disclosure; a candidate LEO satellite other than the reference LEO satellite, which is an optional example of the non-reference LEO satellite in the embodiment of the present disclosure; the high-precision orbit of the LEO satellite other than the reference LEO satellite, which is an optional example of the second orbit data of the non-reference LEO satellite in the embodiment of the present disclosure; there is no limitation on this.
[0131] S604: Determine the clock error data of the non-reference LEO satellite, the first clock error data of the GNSS satellite, and the clock error data of the regional ground station based on the first orbit data of the GNSS satellite, the second orbit data of the first LEO satellite, the position information of the regional ground station, and the inter-satellite link observation data of the reference LEO satellite related to the non-reference LEO satellite.
[0132] In some embodiments of the present disclosure, the clock error data of the benchmark and non-benchmark LEO satellites, the first clock error data of the GNSS satellite, and the clock error data of the regional ground station can be determined based on the first orbit data of the GNSS satellite, the second orbit data of the first LEO satellite, the position information of the regional ground station, and the benchmark LEO satellite inter-satellite link observation data related to the non-benchmark LEO satellite, so as to effectively estimate the clock error data of the non-benchmark LEO satellite that does not participate in the joint solution, and effectively expand the application scenarios of the global satellite navigation system GNSS and LEO satellite constellation data processing method
[0133] In some embodiments, the predicted orbit of the first LEO satellite (an optional example of the second orbit data), the predicted orbit of the GNSS satellite (an optional example of the first orbit data) and the coordinates of the ground station (an optional example of the location information of the regional ground station) can be fixed. At the same time, after adding various models (for example, two-body motion in the dynamic model, non-spherical gravity of the earth, gravity of the sun and the moon, solar radiation pressure, solid tide, ocean tide perturbation, polar tide, atmospheric drag, earth reflected light pressure, etc.) correction items, the Kalman filter algorithm is used to filter and solve the first clock error data of the GNSS satellite, the clock error of the LEO satellite and the clock error data of the ground station (such as Figure 8 As shown, Figure 8 It is a schematic diagram of the clock error data solution process in the embodiment of the present disclosure), and the clock error data is fitted according to the broadcast requirements to obtain a clock error fitting function. The clock error fitting function can support the prediction of the clock error data of the GNSS satellite and / or the first LEO satellite within a certain time range, without any restriction.
[0134] Among them, Kalman filtering can process the observation data in epoch order, without storing a large amount of historical information, relying on the state transfer matrix to link the states of the previous and next epochs, and fully balance the relationship between the observed value and the state prediction value. The Kalman filter algorithm can be divided into state prediction, state estimation, filter gain calculation, prediction variance matrix calculation, estimated variance matrix calculation and other processes to estimate the clock error data of the GNSS satellite and / or the first LEO satellite at the epoch to be predicted.
[0135] In some embodiments, a certain low-orbit satellite can be selected as a reference LEO satellite, and the onboard atomic time of the reference LEO satellite can be used as the reference time. On the basis of the non-differenced ionospheric combined observation values, gross error elimination, cycle slip detection and repair can be performed, and then the clock error data of the GNSS satellite and / or non-reference LEO satellite can be solved to improve the accuracy of the solved clock error data.
[0136] exist Figure 8 In the figure, the monitoring station coordinates are an optional example of the location information of the regional ground station in the embodiment of the present disclosure; the GNSS observation data of the regional monitoring station are an optional example of the GNSS observation data of the monitoring station in the embodiment of the present disclosure; the predicted orbit of the LEO satellite is an optional example of the second orbit data of the first LEO satellite in the embodiment of the present disclosure; the GNSS observation data of the LEO satellite onboard receiver is an optional example of the onboard GNSS observation data in the embodiment of the present disclosure; the predicted orbit of the GNSS satellite is an optional example of the first orbit data of the CNSS satellite in the embodiment of the present disclosure; the GNSS satellite clock error is an optional example of the first clock error data of the CNSS satellite in the embodiment of the present disclosure; the regional ground station clock error is an optional example of the clock error data of the regional ground station in the embodiment of the present disclosure; the LEO satellite onboard GNSS receiver clock error is an optional example of the second clock error data of the first LEO satellite in the embodiment of the present disclosure; there is no limitation on this.
[0137] In some embodiments, for a non-reference LEO satellite that is not involved in solving the navigation satellite clock error estimation, the predicted orbit of the LEO satellite (an optional example of the second orbit data) and the orbit of the GNSS satellite (an optional example of the first orbit data) are fixed, the coordinates of the ground monitoring station (an optional example of the location information of the regional ground station) and the low-orbit inter-satellite link measurement data are introduced, and various models (for example, two-body motion in the dynamic model, non-spherical gravity of the earth, gravity of the sun and the moon, solar radiation pressure, solid tide, ocean tide perturbation, polar tide, atmospheric drag, earth reflected light pressure, etc.) are added. After correction items, the Kalman filter algorithm is used to correct the clock error data of the onboard GNSS receiver on the LEO satellite, the clock error of the GNSS satellite (an optional example of the first clock error data), and the clock error of the ground monitoring station (an optional example of the clock error data of the regional ground station)
[0138] Perform epoch-by-epoch filtering (e.g. Fig. 9 As shown, Fig. 9It is a schematic diagram of the clock error data solution process in the embodiment of the present disclosure), and the clock error data is fitted according to the broadcast requirements to obtain a clock error fitting function, which can support the prediction of the clock error data of non-reference LEO satellites within a certain time range, without limitation. The above describes the real-time solution of LEO satellite clock error data based on the high-precision orbit data and clock error data of known GNSS satellites and the orbit data of LEO satellites. The above processing process can be performed on the satellite or on the ground, without limitation.
[0139] Fig.10 1 is a schematic diagram of the structure of a global satellite navigation system GNSS and a low-orbit satellite constellation data processing device proposed in an embodiment of the present disclosure. Fig.10 As shown, the global satellite navigation system GNSS includes: GNSS satellites, and the low-orbit satellite constellation includes at least: a first low-orbit earth LEO satellite, and the first LEO satellite carries a satellite-borne GNSS receiver; the global satellite navigation system GNSS and low-orbit satellite constellation data processing device 10 includes:
[0140] The satellite data acquisition module 101 is used to acquire the onboard GNSS observation data obtained by the onboard GNSS receiver observing the GNSS satellites, the station GNSS observation data obtained by the regional ground station observing the GNSS satellites, and the station LEO satellite observation data obtained by the regional ground station observing the first LEO satellite.
[0141] The inter-satellite data acquisition module 102 is used to acquire LEO satellite inter-satellite link observation data related to the first LEO satellite.
[0142] The data processing module 103 is used to determine the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station.
[0143] It should be noted that the aforementioned explanation of the global satellite navigation system GNSS and low-orbit satellite constellation data processing method is also applicable to the global satellite navigation system GNSS and low-orbit satellite constellation data processing device of this embodiment, and will not be repeated here.
[0144] In this embodiment, by obtaining the onboard GNSS observation data obtained by the onboard GNSS receiver observing the GNSS satellite, the LEO satellite inter-satellite link observation data related to the first LEO satellite, the station GNSS observation data obtained by the regional ground station observing the GNSS satellite, and the station LEO satellite observation data obtained by the regional ground station observing the first LEO satellite, the orbit and clock error data of the GNSS satellite and / or the first LEO satellite are determined according to the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station, thereby effectively expanding the application scenarios of high-precision orbit and clock error solution of GNSS satellites and LEO satellites.
[0145] Fig.11 A block diagram of an exemplary communication device suitable for implementing embodiments of the present disclosure is shown. Fig.11 The communication device 12 shown is only an example and should not limit the functionality and scope of use of the embodiments of the present disclosure. Fig.11 As shown, the communication device 12 is in the form of a general purpose computing device. Components of the communication device 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).
[0146] The bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnection (PCI) bus.
[0147] The communication device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the communication device 12, including volatile and non-volatile media, removable and non-removable media.
[0148] The memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The communication device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Fig.11 Not shown, often called a "hard drive").
[0149] although Fig.11 Not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (e.g., a compact disc read only memory (hereinafter referred to as: CD-ROM), a digital versatile disc read only memory (hereinafter referred to as: DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.
[0150] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28, such program modules 42 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods of the embodiments described in the present disclosure.
[0151] The communication device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a human body to interact with the communication device 12, and / or any device that enables the communication device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 22. In addition, the communication device 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the communication device 12 through a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the communication device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0152] The processing unit 16 executes various functional applications and data processing by running the programs stored in the system memory 28, such as implementing the global satellite navigation system GNSS and low-orbit satellite constellation data processing method mentioned in the above-mentioned embodiment.
[0153] In order to implement the above-mentioned embodiments, the present disclosure also proposes a non-temporary computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the global satellite navigation system GNSS and low-orbit satellite constellation data processing method proposed in the aforementioned embodiments of the present disclosure.
[0154] In order to implement the above embodiments, the present disclosure also proposes a computer program product. When the instruction processor in the computer program product executes, it executes the global satellite navigation system GNSS and low-orbit satellite constellation data processing method proposed in the aforementioned embodiments of the present disclosure.
[0155] It should be noted that, in the description of the present disclosure, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present disclosure, unless otherwise specified, the meaning of "plurality" is two or more.
[0156] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present disclosure includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.
[0157] It should be understood that the various parts of the present disclosure can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.
[0158] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.
[0159] In addition, each functional unit in each embodiment of the present disclosure may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.
[0160] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.
[0161] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0162] Although the embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present disclosure. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present disclosure.
Claims
1. A method for processing global satellite navigation system GNSS and low-orbit satellite constellation data, characterized in that: The global satellite navigation system GNSS comprises: a GNSS satellite, the low-orbit satellite constellation comprises: a first low-orbit earth LEO satellite, the first LEO satellite carries a satellite-borne GNSS receiver; the method comprises: Acquiring onboard GNSS observation data obtained by the onboard GNSS receiver from observing the GNSS satellite; Acquiring LEO satellite intersatellite link observation data associated with the first LEO satellite; Obtaining station GNSS observation data obtained by a regional ground station observing the GNSS satellite; Acquiring station LEO satellite observation data obtained by the regional ground station observing the first LEO satellite; and The orbit and clock error data of the GNSS satellite and / or the first LEO satellite are determined based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station.
2. The method according to claim 1, characterized in that The obtaining of the onboard GNSS observation data obtained by the onboard GNSS receiver from observing the GNSS satellite comprises: Acquiring the satellite-borne GNSS observation data forwarded by the regional ground station; Wherein, when the first LEO satellite is visible relative to the regional ground station, the regional ground station receives the onboard GNSS observation data observed and sent by the first LEO satellite based on the onboard GNSS receiver; or, When the first LEO satellite is not visible relative to the regional ground station, the regional ground station receives the onboard GNSS observation data forwarded by other LEO satellites. The other LEO satellites are visible relative to the regional ground station, and the other LEO satellites receive the onboard GNSS observation data observed and sent by the first LEO satellite based on the onboard GNSS receiver.
3. The method according to claim 1, characterized in that The acquiring of LEO satellite intersatellite link observation data related to the first LEO satellite includes: Acquiring the LEO satellite intersatellite link observation data forwarded by the regional ground station; Wherein, when the first LEO satellite is visible to the regional ground station, the regional ground station receives the LEO satellite intersatellite link observation data sent by the first LEO satellite; or, When the first LEO satellite is not visible to the regional ground station, the regional ground station receives the LEO satellite inter-satellite link observation data forwarded by other LEO satellites. The other LEO satellites are visible to the regional ground station, and the other LEO satellites receive the LEO satellite inter-satellite link observation data sent by the first LEO satellite.
4. The method according to claim 1, characterized in that The method further comprises: Acquiring GNSS satellite intersatellite link observation data related to the GNSS satellite; The determining of the orbit and clock error data of the GNSS satellite and / or the first LEO satellite according to the onboard GNSS observation data, the LEO satellite intersatellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station includes: The orbit and clock error data of the GNSS satellite and / or the first LEO satellite are determined based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the location information of the regional ground station, the GNSS satellite inter-satellite link observation data, and the station LEO satellite observation data.
5. The method according to claim 4, characterized in that The determining the orbit and clock error data of the GNSS satellite and / or the first LEO satellite according to the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the position information of the regional ground station, the GNSS satellite inter-satellite link observation data, and the station LEO satellite observation data comprises: Determine the first orbital data of the GNSS satellite and the second orbital data of the first LEO satellite according to the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the location information of the regional ground station, the GNSS satellite inter-satellite link observation data, and the station LEO satellite observation data; The first clock error data of the GNSS satellite and the second clock error data of the first LEO satellite are determined according to the onboard GNSS observation data, the station GNSS observation data, the position information of the regional ground station, the first orbit data, and the second orbit data.
6. The method according to any one of claims 1 to 5, characterized in that: The first LEO satellite belongs to a plurality of candidate LEO satellites; wherein, Each candidate LEO satellite in the plurality of candidate LEO satellites is used as the first LEO satellite, wherein the number of the first LEO satellites is multiple; or, Each candidate LEO satellite in some of the candidate LEO satellites is used as the first LEO satellite, wherein the number of the first LEO satellite is at least one.
7. The method according to claim 6, characterized in that The candidate LEO satellite carries an onboard GNSS receiver and an onboard navigation signal transmitting device; wherein, When each candidate LEO satellite among the multiple candidate LEO satellites is used as the first LEO satellite, the onboard GNSS receiver carried by each candidate LEO satellite is in an on-state, and the onboard navigation signal transmitting device is in an on-state.
8. The method according to claim 6, characterized in that The candidate LEO satellite carries an onboard GNSS receiver and an onboard navigation signal transmitting device; wherein, In the case where each candidate LEO satellite in some of the candidate LEO satellites is used as the first LEO satellite, the onboard GNSS receiver carried by each candidate LEO satellite is in an on-state, and the onboard navigation signal transmitting device is in an off-state; The onboard GNSS receiver of the non-reference LEO satellite is in a closed state, and the onboard navigation signal transmitting device is in an open state, wherein the non-reference LEO satellite is the remaining candidate LEO satellite among the multiple candidate LEO satellites except for some of the candidate LEO satellites.
9. The method according to claim 6, characterized in that In the case where each candidate LEO satellite in some of the candidate LEO satellites is selected as the first LEO satellite, the method further includes: Acquire station LEO satellite observation data obtained by the regional ground station observing a non-reference LEO satellite, wherein the non-reference LEO satellite is a candidate LEO satellite remaining in the plurality of candidate LEO satellites except for some of the candidate LEO satellites; Acquiring reference LEO satellite intersatellite link observation data associated with the non-reference LEO satellite; The second orbit data of the non-reference LEO satellite is determined based on the station LEO satellite observation data, the reference LEO satellite intersatellite link observation data related to the non-reference LEO satellite, and the second orbit data of the first LEO satellite.
10. The method according to claim 6, characterized in that In the case where each candidate LEO satellite in some of the candidate LEO satellites is selected as the first LEO satellite, the method further includes: The clock error data of the non-reference LEO satellite, the first clock error data of the GNSS satellite, and the clock error data of the regional ground station are determined based on the first orbit data of the GNSS satellite, the second orbit data of the first LEO satellite, the position information of the regional ground station, and the reference LEO satellite inter-satellite link observation data related to the non-reference LEO satellite, wherein the non-reference LEO satellite is the remaining candidate LEO satellite among the multiple candidate LEO satellites except for some of the candidate LEO satellites.
11. A global satellite navigation system GNSS and low-orbit satellite constellation data processing device, characterized in that: The global satellite navigation system GNSS comprises: a GNSS satellite, the low-orbit satellite constellation comprises: a first low-orbit earth LEO satellite, the first LEO satellite carries a satellite-borne GNSS receiver; the device comprises: a satellite data acquisition module, configured to acquire onboard GNSS observation data obtained by the onboard GNSS receiver observing the GNSS satellite, station GNSS observation data obtained by a regional ground station observing the GNSS satellite, and station LEO satellite observation data obtained by the regional ground station observing the first LEO satellite; An inter-satellite data acquisition module, used to acquire LEO satellite inter-satellite link observation data related to the first LEO satellite; A data processing module is used to determine the orbit and clock error data of the GNSS satellite and / or the first LEO satellite based on the onboard GNSS observation data, the LEO satellite inter-satellite link observation data, the station GNSS observation data, the station LEO satellite observation data, and the position information of the regional ground station.
12. A communication device, characterized in that: include: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 10.
13. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: in, The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 10.
14. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10.
Citation Information
Cited By
On-orbit time synchronization system of low-orbit satellite
CN120630634A
