Space-ground joint planning method and system for ultra-low earth orbit satellite

Abstract

The application provides a kind of star-ground joint planning method for ultra-low earth orbit satellite, comprising: receiving the load parameter file provided by user, and generating task planning file;According to GNSS telemetry data, the orbital elements of satellite are obtained, the entry and exit of satellite are forecasted, and the corresponding orbit control file and ephemeris file are generated;The task planning file, the orbit control file and the ephemeris file are sent to the corresponding instructions to the satellite;At the same time, receiving, forwarding and / or analyzing the telemetry data and data transmission file returned by the satellite, realizing the interaction between satellite and ground;Key data monitoring is carried out on the received telemetry data, and alarm level information is generated.A kind of star-ground joint planning system for ultra-low earth orbit satellite is also provided.The star-ground joint planning method and system for ultra-low earth orbit satellite provided by the application effectively improve the autonomy of satellite and ground application interaction, and reduce the difficulty of ground operation.

Description

Technical Field

[0001] This invention relates to the field of ultra-low orbit satellite technology, specifically to a satellite-ground joint planning method and system for ultra-low orbit satellites, and also provides a corresponding terminal and medium. Background Technology

[0002] In recent years, many countries and regions have begun to focus on the ultra-low Earth orbit (ULO) field and have launched ULE scientific exploration satellites. ULE satellites offer unparalleled advantages over conventional satellites in terms of improved optical imaging resolution, reduced transmission power, and lower launch costs. However, they also face greater atmospheric drag and a more demanding thermal environment. Satellite ground application systems are designed to ensure satellite application needs are met and facilitate maintenance of the satellite platform by operations and control personnel according to mission requirements. However, in the ULE environment, satellite orbit maintenance, entry and exit from Earth, and mission scheduling become significantly more difficult, posing numerous challenges to ground operations and maintenance teams. Summary of the Invention

[0003] To address the aforementioned shortcomings in the prior art, this invention provides a space-ground joint planning method and system for ultra-low orbit satellites, along with a corresponding terminal and medium.

[0004] According to one aspect of the present invention, a space-ground joint planning method for ultra-low orbit satellites is provided, comprising:

[0005] Receive a payload parameter file provided by the user. The file name of the payload parameter file includes: task start time, task type, and number of tasks.

[0006] Based on GNSS telemetry data, the orbital root numbers of the satellite were obtained, and the following operations were performed:

[0007] - Forecast the entry and exit status of satellites and generate corresponding ephemeris files, which include: ephemeris point counts, entry time, exit time, and ephemeris instruction source code;

[0008] -When the orbit control strategy is to extrapolate the orbit based on the precise orbit determination data from the ground, an orbit control file is generated according to the set orbit maintenance upper limit. The orbit control file includes: jet timing, jet duration, and source code of orbit change parameter package instructions.

[0009] - Predict the entry and exit times of satellites into and out of shadow, and generate a shadow time file, which includes the entry and exit times of the shadow.

[0010] Based on the payload parameter file, a corresponding task planning file is generated. The task planning file includes at least: task start time, task type, number of tasks, instruction name, and task sequence instruction source code.

[0011] The mission planning file, the orbit control file, and the ephemeris file contain the source code of the ephemeris instruction, the source code of the orbit change parameter package instruction, and the source code of the mission sequence instruction, which are sent to the satellite; at the same time, the satellite receives, forwards, and / or parses the telemetry data and data transmission files transmitted back from the satellite to achieve satellite-to-ground interaction.

[0012] The received telemetry data is used for key data monitoring to generate alarm level information.

[0013] Preferably, the filename of the load parameter file is named according to naming conventions.

[0014] Preferably, the naming convention includes:

[0015] XXXX load parameters - YYYY-MM-DD-HH-MM-SS-N.dat

[0016] Where XXXX represents the task type; YYYY-MM-DD-HH-MM-SS represents the task start time; and N represents the number of tasks.

[0017] Preferably, the task types include: stellar observation tasks and solar observation tasks; when the task type is a stellar observation task, the value of N is always 1; when the task type is a solar observation task, the value of N is the number of tasks that the solar observation task needs to perform under this set of parameters.

[0018] Preferably, generating a task planning file based on the load parameter file includes:

[0019] Obtain the task type from the filename of the payload parameter file, which includes: stellar observation mission and solar observation mission; wherein: for stellar observation mission, obtain the mission start time from the filename of the payload parameter file and the relevant payload parameters encapsulated in the payload parameter file, load the relevant payload parameters into the payload parameter uploading instruction, obtain the instruction name and the source code of the payload parameter uploading instruction, and generate a mission planning file;

[0020] For solar observation missions, the mission start time, mission count, and related payload parameters encapsulated in the payload parameter file are obtained from the filename of the payload parameter file. These related payload parameters are then loaded into the payload parameter annotation command to obtain the command name and payload parameter annotation command source code. Simultaneously, based on the shadow time file, the mission end time is recursively calculated according to the mission count and mission start time, generating a corresponding mission planning file. Wherein, the mission end time is the sum of the shadow entry time corresponding to the Nth exit from shadow and a fixed duration, where N is the mission count.

[0021] Preferably, the corresponding orbit control files and ephemeris files are generated, including:

[0022] The orbital six-point number of the satellite is obtained by using GNSS positioning orbital data. STK is then used to predict the satellite's entry and exit status, thereby generating the corresponding orbital control file and ephemeris file.

[0023] Preferably, the track control file includes:

[0024] - Onboard autonomous orbit control scheme, wherein the onboard autonomous orbit control scheme maintains the orbit autonomously through satellite service software and can change the upper and lower limits of autonomous orbit maintenance on the ground;

[0025] - Ground-based track control scheme, wherein the ground-based track control scheme is based on precise track determination data and / or the intervention and adjustment of parameters by track control designers to perform track recursion.

[0026] Preferably, the step of monitoring key data in the received telemetry data and generating alarm level information includes:

[0027] Based on the satellite long-tube diagnostic parameter status table, key data are monitored and judged to generate alarm level information.

[0028] According to another aspect of the present invention, a space-ground joint planning system for ultra-low Earth orbit satellites is provided, comprising: a mission planning system, an orbit and ephemeris prediction system, an operation and control system, and an anomaly handling system; wherein:

[0029] The task planning system is used to receive the load parameter file provided by the user, generate a task planning file, and then output it to the operation and control system.

[0030] The orbit and ephemeris prediction system is used to obtain the six orbital elements of the satellite based on the GNSS telemetry data received by the operation and control system, predict the satellite's entry and exit from the shadow, and generate corresponding orbit control files and ephemeris files to output to the operation and control system; calculate the entry and exit times of the satellite for each orbit, and generate shadow time files to output to the mission planning system.

[0031] The operation and control system is used to receive the mission planning file, the orbit control file, and the ephemeris file, and to obtain the ephemeris instruction source code, orbit change parameter package instruction source code, and mission sequence instruction source code contained in the file and send them to the satellite; at the same time, it receives, forwards, and / or parses the telemetry data and data transmission files transmitted back from the satellite to realize satellite-ground interaction.

[0032] The anomaly handling system is used to receive the telemetry data, monitor key data, and generate alarm level information.

[0033] According to a third aspect of the present invention, a computer terminal is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, can be used to perform the method described in any one of the preceding descriptions, or to run the system described above.

[0034] According to a fourth aspect of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, can be used to perform the method described in any one of the preceding descriptions, or to run the system described above.

[0035] By adopting the above technical solution, the present invention has at least one of the following beneficial effects compared with the prior art:

[0036] The satellite-ground joint planning method and system for ultra-low orbit satellites provided by this invention improves the autonomy of interaction between satellites and ground applications and reduces the difficulty of ground operations.

[0037] The satellite-ground joint planning method and system for ultra-low orbit satellites provided by this invention can autonomously generate mission planning documents based on the payload parameter files provided by the user, and generate mission sequence instruction source code for the satellite to complete autonomous missions, reducing system input while protecting the user's business secrets.

[0038] The satellite-ground joint planning method and system for ultra-low orbit satellites provided by this invention can autonomously generate orbit control files based on the latest orbit input, realize orbit control of satellites, reduce professional requirements, and achieve the purpose of frequent orbit maintenance for ultra-low orbit satellites.

[0039] The satellite-ground joint planning method and system for ultra-low orbit satellites provided by this invention can monitor key telemetry data and issue real-time alarms, enabling ground control personnel to promptly handle on-board anomalies and reducing their workload.

[0040] The satellite-ground joint planning method and system for ultra-low orbit satellites provided by this invention can autonomously and rapidly update satellite entry and exit plans based on the latest orbit input and generate ephemeris tables, thereby reducing orbit prediction errors for ultra-low orbit satellites and meeting the requirements for frequent ephemeris table updates for ultra-low orbit satellites.

[0041] The satellite-ground joint planning method and system for ultra-low orbit satellites provided by this invention can adapt to the requirements of solar observation missions, autonomously read the mission start time, and autonomously calculate the mission end time. Attached Figure Description

[0042] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0043] Figure 1 A flowchart of the satellite-ground joint planning method in one embodiment of the present invention.

[0044] Figure 2 A schematic diagram of the organizational structure of a space-ground joint planning system in one embodiment of the present invention.

[0045] Figure 3 This is a flowchart of the satellite-ground joint planning method and a schematic diagram of the system's organizational structure in a preferred embodiment of the present invention. Detailed Implementation

[0046] The embodiments of the present invention are described in detail below: These embodiments are implemented based on the technical solution of the present invention, and provide detailed implementation methods and specific operation processes. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention.

[0047] One embodiment of the present invention provides a space-ground joint planning method for ultra-low orbit satellites. This method realizes the interaction between ultra-low orbit satellites and the ground, improves the autonomy of interaction between satellites and ground applications, and reduces the difficulty of ground operations.

[0048] like Figure 1 As shown, the space-ground joint planning method for ultra-low orbit satellites provided in this embodiment may include:

[0049] S1 receives the payload parameter file provided by the user. The file name of the payload parameter file includes: task start time, task type and number of tasks.

[0050] S2, based on GNSS telemetry data, obtain the satellite's orbital six roots, and perform the following operations to obtain the ephemeris file, orbital control file, and shadowing time file:

[0051] - Forecast satellite entry and exit information and generate corresponding ephemeris files, which include: ephemeris point count, entry time, exit time, and ephemeris command source code;

[0052] -When the orbit control strategy is to extrapolate the orbit based on the precise orbit determination data from the ground, an orbit control file is generated according to the set orbit maintenance upper limit. The orbit control file includes: jet timing, jet duration, and source code of the orbit change parameter package instructions.

[0053] - Predict the entry and exit times of satellites into and out of shadow, and generate shadow time files, which include the entry and exit times of the shadow.

[0054] S3 generates a corresponding task planning file based on the load parameter file. The task planning file includes at least: task start time, task type, number of tasks, instruction name, and task sequence instruction source code.

[0055] S4 sends the source code of the ephemeris instruction, the source code of the orbit change parameter package instruction, and the source code of the mission sequence instruction contained in the mission planning file, orbit control file, and ephemeris file to the satellite; at the same time, it receives, forwards, and / or parses the telemetry data and data transmission files transmitted back from the satellite to realize satellite-ground interaction.

[0056] S5 performs key data monitoring on the received telemetry data and generates alarm level information.

[0057] In a preferred embodiment of S1, the filename of the load parameter file is named according to naming conventions.

[0058] In a preferred embodiment of S1, the naming convention includes:

[0059] XXXX load parameters - YYYY-MM-DD-HH-MM-SS-N.dat

[0060] Where XXXX represents the task type; YYYY-MM-DD-HH-MM-SS represents the task start time; and N represents the number of tasks.

[0061] In a specific application example of S1, the task types include: stellar observation task and solar observation task; when the task type is stellar observation task, the value of N is always 1; when the task type is solar observation task, the value of N is the number of tasks that the solar observation task needs to perform under this set of parameters.

[0062] In a preferred embodiment of S2, the orbital six-point number of the satellite is obtained through GNSS positioning orbit data, STK is called to predict the satellite's entry and exit status, and then corresponding orbital control files and ephemeris files are generated.

[0063] In a preferred embodiment of S2, the track control file includes:

[0064] - The first option is an onboard autonomous orbit control scheme. This scheme uses satellite maintenance software to maintain the orbit autonomously onboard, and the upper and lower limits of autonomous orbit maintenance can be changed from the ground.

[0065] - The second option is a ground-based track control scheme, where the track is recursively calculated from precise track determination data. This is the preferred option.

[0066] Furthermore, in the ground-based track control scheme, track control designers can intervene in and adjust the parameters.

[0067] In a preferred embodiment of S3, a task planning file is generated based on the load parameter file, including:

[0068] Obtain the mission type from the filename of the payload parameter file. Mission types include: stellar observation mission and solar observation mission; where:

[0069] For stellar observation missions, obtain the mission start time from the filename of the payload parameter file and the relevant payload parameters encapsulated in the payload parameter file. Load the relevant payload parameters into the payload parameter uploading instruction, obtain the instruction name and the source code of the payload parameter uploading instruction, and generate a mission planning file.

[0070] For solar observation missions, the mission start time, mission count, and related payload parameters encapsulated in the payload parameter file are obtained from the filename. These payload parameters are then loaded into the payload parameter annotation command to obtain the command name and source code. Simultaneously, based on the shadow time file, the mission end time is recursively derived from the mission count and mission start time, generating the corresponding mission planning file. Here, the mission end time is the sum of the shadow entry time corresponding to the Nth exit from shadow and a fixed duration, where N is the mission count.

[0071] In a preferred embodiment of S4, key data are monitored and judged according to the satellite long-tube diagnostic parameter status table to generate alarm level information.

[0072] An embodiment of the present invention also provides a space-ground joint planning system for ultra-low orbit satellites, such as... Figure 2 As shown, the system includes: a mission planning system, an orbit and ephemeris prediction system, a motion control system, and an anomaly handling system; among which:

[0073] The task planning system is used to receive the load parameter file provided by the user, generate a task planning file, and then output it to the operation and control system.

[0074] The orbit and ephemeris prediction system is used to obtain the six orbital elements of the satellite based on the GNSS telemetry data received by the operation and control system, predict the satellite's entry and exit from the shadow, and generate corresponding orbit control files and ephemeris files to be output to the operation and control system; it also calculates the entry and exit times of the satellite for each orbit and generates shadow time files to be output to the mission planning system.

[0075] The operation and control system is used to receive mission planning documents, orbit control documents, and ephemeris documents, and to obtain the source code of ephemeris instructions, orbit change parameter package instructions, and mission sequence instructions contained in the documents before sending them to the satellite; at the same time, it receives, forwards, and / or parses the telemetry data and data transmission files transmitted back from the satellite to realize satellite-ground interaction.

[0076] The anomaly handling system is used to receive telemetry data, monitor key data, and generate alarm level information.

[0077] In a preferred embodiment, the filename of the payload parameter file includes: task type, task start time, and number of tasks; the payload parameter file is named according to naming conventions.

[0078] In a preferred embodiment, the naming convention includes:

[0079] XXXX load parameters - YYYY-MM-DD-HH-MM-SS-N.dat

[0080] Where XXXX represents the task type; YYYY-MM-DD-HH-MM-SS represents the task start time; and N represents the number of tasks.

[0081] In a specific application example, the task types include: stellar observation task and solar observation task; when the task type is stellar observation task, the value of N is always 1; when the task type is solar observation task, the value of N is the number of times the solar observation task needs to be performed under this set of parameters.

[0082] In a preferred embodiment, generating a task planning file includes:

[0083] Obtain the task type from the filename of the payload parameter file. The task types include: star observation mission and solar observation mission. For star observation mission, obtain the mission start time from the filename of the payload parameter file and the relevant payload parameters encapsulated in the payload parameter file. Load the relevant payload parameters into the payload parameter uploading instruction, obtain the instruction name and the source code of the payload parameter uploading instruction, and generate the mission planning file.

[0084] For solar observation missions, the mission start time, mission count, and related payload parameters encapsulated in the payload parameter file are obtained from the filename. These payload parameters are then loaded into the parameter annotation instructions to obtain the instruction name and source code for the payload parameter annotation instructions. Simultaneously, based on the shadow time file, the mission end time is recursively derived from the mission count and mission start time, generating the corresponding mission planning file. Here, the mission end time is the sum of the shadow entry time corresponding to the Nth exit from shadow and a fixed duration, where N is the mission count.

[0085] In a preferred embodiment, the orbit and ephemeris prediction system obtains the orbital six-axis number of the satellite through GNSS positioning orbit data, calls STK to predict the satellite's entry and exit status, and generates corresponding orbit control files and ephemeris files.

[0086] In a preferred embodiment, the track control file includes:

[0087] - The first type is the on-board autonomous orbit control scheme. This scheme uses satellite maintenance software to maintain the orbit autonomously on the satellite, and the upper and lower limits of autonomous orbit maintenance can be changed on the ground.

[0088] - The second option is a ground-based track control scheme. This scheme involves ground-based recursion of track data based on precise track determination data to generate corresponding track control files. This is the preferred option.

[0089] In a preferred embodiment, in the ground-based track control scheme, the track control designer is able to intervene in and adjust the parameters.

[0090] In a preferred embodiment, the anomaly handling system monitors and judges key data according to the satellite long-tube diagnostic parameter status table, and generates alarm level information.

[0091] The technical solutions provided by the above embodiments of the present invention will be further described in detail below.

[0092] like Figure 3 As shown, the space-ground joint planning system consists of four parts: mission planning system, operation and control system, orbit and ephemeris prediction system, and anomaly handling system. Once the satellite enters the long-term management phase, users only need to generate payload parameter files according to the corresponding naming rules and input them into the system to complete on-orbit mission planning. The satellite will then autonomously complete the mission based on the planned objectives.

[0093] Satellite orbit control is divided into two strategies. The first is fully autonomous onboard orbit control. Since this scheme is designed based on ultra-low orbit satellites, space debris and on-orbit avoidance can be ignored, so the satellite can autonomously maintain its orbit. The second scheme involves the ground performing orbit recursion based on precise orbit determination data, and then the system generates the corresponding orbit control scheme. During this process, the orbit control designer can intervene and adjust the parameters. After the orbit control file is generated, it is sent to the satellite by the operation and control system for orbit control implementation.

[0094] I. Overall Parameters

[0095] The user determines the overall parameters related to the task, which serve as input for the subsequent task planning system. The parameters that need to be determined are as follows:

[0096] Table 1 Task parameters that users need to confirm

[0097]

[0098] Users need to name the payload task parameters according to the corresponding format. The specific format is as follows: XXXX payload parameters-YYYY-MM-DD-HH-MM-SS-N.dat, where XXXX is the task type; YYYY-MM-DD-HH-MM-SS is the task start time; and N is the number of tasks. If the user does not update the payload parameters for subsequent tasks, they can also manually enter the relevant information through the task planning system.

[0099] Note: When the mission is a stellar observation mission, the value of N is always 1; when the mission is a solar observation mission, the value of N is the number of solar observation missions required under this set of parameters.

[0100] II. Task Planning System

[0101] The mission planning system is a business module of the space-ground joint planning system. It receives payload parameter files provided by users and automatically extracts mission type, mission start time, mission frequency, and payload parameters from the payload parameter files as input to generate a corresponding mission planning file. This file will then be sent to the satellite as input to the subsequent operation and control system for the satellite to carry out its on-orbit mission.

[0102] 2.1 Input

[0103]

[0104] 2.2 Output

[0105]

[0106] III. Operation and Control System

[0107] The operation and control system is a satellite-to-ground interaction module, which mainly completes command sending, telemetry reception and forwarding, and data transmission file reception and forwarding. It is also responsible for parsing telemetry and data transmission files and displaying them on the corresponding interface for users to query.

[0108] 3.1 Input

[0109]

[0110] 3.2 Output

[0111]

[0112]

[0113] Remark:

[0114] Only the source code of the ephemeris instruction, orbit change parameter package instruction, and mission sequence instruction from the mission planning file, orbit control file, ephemeris file, and mission sequence instruction are retrieved and sent to the satellite.

[0115] IV. Orbit and Ephemeris Prediction System

[0116] The orbit and ephemeris prediction system is a supporting module of the space-ground joint planning system. Its main function is to use the on-board GNSS telemetry data received by the operation and control system to obtain the six orbital elements of the satellite through GNSS positioning orbit data, call STK to predict the satellite's entry and exit status, and generate corresponding orbit control documents and ephemeris documents (data transmission ephemeris tables).

[0117] 4.1 Input

[0118]

[0119] 4.2 Output

[0120]

[0121] V. Anomaly Handling System

[0122] The anomaly handling system primarily receives satellite telemetry data acquired by the operations and control system. It monitors key data from modules such as satellite operations, energy, thermal control, and mission guidance. If the corresponding telemetry data transmitted from the satellite is an anomaly for 10 consecutive cycles, an alarm is triggered. The anomaly information is automatically sent to the satellite designers via group messages, and the system is categorized and handled according to the alarm level. For a Level 1 alarm, the operations and control personnel immediately notify the relevant subsystem designers for handling. For a Level 2 alarm, the subsystem designers can postpone their actions. For a Level 3 alarm, the operations and control personnel handle the situation themselves.

[0123] 5.1 Input

[0124] 1 Telemetry data Operation control system 2 Satellite Long-Tube Diagnostic Parameter Status Table Designer Parameters can be changed

[0125] 5.2 Output

[0126] 1 Abnormal information User / Designer

[0127] The technical solution provided by the above embodiments of the present invention will be further explained below with reference to a specific application example.

[0128] In this specific application example, based on the space-ground joint planning system and method provided in the above embodiments of the present invention, the stellar observation mission and solar observation mission of ultra-low orbit satellite are described.

[0129] Both stellar observation and solar observation missions are triggered by ground commands. After triggering, the mission's end time is determined by the number of missions completed. Stellar observation missions end autonomously onboard, while solar observation missions end via ground commands. The execution time of the solar observation mission's end command is determined by the number of missions completed and the times of entering and exiting shadow. This command is generated along with the mission planning file. Both stellar and solar observation missions can also be terminated early via forced ground commands. Specifically:

[0130] The solar observation mission is conducted autonomously by the satellite and will continue until a mission completion marker is received. Therefore, for this mission, the ground control only needs to determine the mission start and end times, as well as the relevant payload parameters. The mission end time is related to the solar altitude angle, so it is necessary to avoid the solar altitude angle corresponding to the autonomous mission observation phase.

[0131] For stellar observation missions, the start time of each observation is determined by the ground station. The maximum duration of the mission is fixed and depends only on the different operational conditions of the stellar observation mission. Therefore, the end time of the stellar observation mission can be determined autonomously by the satellite. The ground station only needs to determine the mission start time and related payload parameters. The number of payload parameters for a stellar observation mission is consistent with the number of observations.

[0132] As can be seen from the above description of specific application examples, the satellite-ground joint planning method and system for ultra-low orbit satellites provided by the above embodiments of the present invention effectively improves the autonomy of interaction between satellites and ground applications, and reduces the difficulty of ground operations.

[0133] One embodiment of the present invention provides a computer terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it can be used to execute any of the methods in the above embodiments of the present invention, or to run any of the systems in the above embodiments of the present invention.

[0134] Optionally, the memory is used to store programs; the memory may include volatile memory, such as random-access memory (RAM), such as static random-access memory (SRAM), double data rate synchronous dynamic random-access memory (DDR SDRAM), etc.; the memory may also include non-volatile memory, such as flash memory. The memory is used to store computer programs (such as application programs, functional modules, etc. that implement the above methods), computer instructions, etc., and the aforementioned computer programs, computer instructions, etc., can be partitioned and stored in one or more memories. Furthermore, the aforementioned computer programs, computer instructions, data, etc., can be accessed by the processor.

[0135] The aforementioned computer programs, computer instructions, etc., can be stored in partitions within one or more memory locations. Furthermore, the aforementioned computer programs, computer instructions, data, etc., can be accessed by a processor.

[0136] A processor is used to execute computer programs stored in memory to implement the various steps of the methods or various modules of the systems involved in the above embodiments. For details, please refer to the relevant descriptions in the preceding method and system embodiments.

[0137] The processor and memory can be separate structures or integrated structures. When the processor and memory are separate structures, they can be coupled together via a bus.

[0138] According to a fourth aspect of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, can be used to perform the method of any of the above embodiments of the present invention, or to run the system of any of the above embodiments of the present invention.

[0139] The satellite-ground joint planning method and system for ultra-low orbit (ULO) satellites provided in the above embodiments of the present invention improves the autonomy of interaction between satellites and ground applications, and reduces the difficulty of ground operations. It can autonomously generate mission planning files based on user-provided payload parameter files, and generate mission sequence instruction source code for the satellite to complete autonomous tasks, reducing system input while protecting user trade secrets. It can autonomously generate orbit control files based on the latest orbit input, realizing orbit control of the satellite, reducing the professional requirements, and achieving the goal of frequent orbit maintenance for ULE satellites. It can monitor key telemetry data and provide real-time alarms, enabling ground control personnel to promptly handle on-board anomalies, reducing the workload of ground control personnel. It can autonomously and quickly update satellite entry and exit plans based on the latest orbit input and generate ephemeris tables, reducing ULE satellite orbit prediction errors and meeting the requirements for frequent ephemeris table updates for ULE satellites. It can adapt to the requirements of solar observation missions, autonomously reading the mission start time and autonomously calculating the mission end time.

[0140] Those skilled in the art will understand that, in addition to implementing the system and its various devices provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices of this invention function as logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices provided by this invention can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0141] Any matters not covered in the above embodiments of the present invention are well-known in the art.

[0142] The specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various modifications or variations within the scope of the claims, which do not affect the essence of the present invention.

Claims

1. A space-ground joint planning method for ultra-low orbit satellites, characterized in that, include: Receive a payload parameter file provided by the user. The file name of the payload parameter file includes: task start time, task type, and number of tasks. Based on GNSS telemetry data, the orbital root numbers of the satellite were obtained, and the following operations were performed: - Forecast the entry and exit status of satellites and generate corresponding ephemeris files, which include: ephemeris point counts, entry time, exit time, and ephemeris instruction source code; - When the orbit control strategy is to extrapolate the orbit based on the precise orbit determination data from the ground, an orbit control file is generated according to the set orbit maintenance upper limit. The orbit control file includes: jet timing, jet duration, and source code of orbit change parameter package instructions. - Predict the entry and exit times of satellites into and out of shadow, and generate a shadow time file, which includes the entry and exit times of the shadow. Based on the payload parameter file, a corresponding task planning file is generated. The task planning file includes at least: task start time, task type, number of tasks, instruction name, and task sequence instruction source code. The mission planning file, the orbit control file, and the ephemeris file contain the source code of the ephemeris instruction, the source code of the orbit change parameter package instruction, and the source code of the mission sequence instruction, which are sent to the satellite; at the same time, the satellite receives, forwards, and / or parses the telemetry data and data transmission files transmitted back from the satellite to achieve satellite-to-ground interaction. The received telemetry data is monitored for key data, and alarm level information is generated. in: The step of generating a corresponding task planning file based on the load parameter file includes: Obtain the task type from the filename of the payload parameter file, which includes: stellar observation mission and solar observation mission; wherein: for stellar observation mission, obtain the mission start time from the filename of the payload parameter file and the relevant payload parameters encapsulated in the payload parameter file, load the relevant payload parameters into the payload parameter uploading instruction, obtain the instruction name and the source code of the payload parameter uploading instruction, and generate a mission planning file; For solar observation missions, the mission start time, mission count, and related payload parameters encapsulated in the payload parameter file are obtained from the filename of the payload parameter file. These related payload parameters are then loaded into the payload parameter annotation command to obtain the command name and payload parameter annotation command source code. Simultaneously, based on the shadow time file, the mission end time is recursively calculated according to the mission count and mission start time, generating a corresponding mission planning file. Wherein, the mission end time is the sum of the shadow entry time corresponding to the Nth exit from shadow and a fixed duration, where N is the mission count.

2. The space-ground joint planning method for ultra-low orbit satellites according to claim 1, characterized in that, The filename of the load parameter file is named according to the naming convention.

3. The space-ground joint planning method for ultra-low orbit satellites according to claim 2, characterized in that, The naming conventions include: XXXX load parameters - YYYY-MM-DD-HH-MM-SS-N.dat Where XXXX represents the task type; YYYY-MM-DD-HH-MM-SS represents the task start time; and N represents the number of tasks.

4. The space-ground joint planning method for ultra-low orbit satellites according to claim 1, characterized in that, The mission types include: stellar observation missions and solar observation missions; when the mission type is a stellar observation mission, the value of N is always 1; when the mission type is a solar observation mission, the value of N is the number of missions that the solar observation mission needs to perform.

5. The space-ground joint planning method for ultra-low orbit satellites according to claim 1, characterized in that, Generate the corresponding orbit control files and ephemeris files, including: The orbital six-point number of the satellite is obtained by using GNSS positioning orbital data. STK is then used to predict the satellite's entry and exit status, thereby generating the corresponding orbital control file and ephemeris file.

6. The space-ground joint planning method for ultra-low orbit satellites according to claim 1, characterized in that, The track control documents include: - Onboard autonomous orbit control scheme, wherein the onboard autonomous orbit control scheme maintains the orbit autonomously through satellite service software and can change the upper and lower limits of autonomous orbit maintenance through ground control. - Ground-based track control scheme, wherein the ground-based track control scheme is based on precise track determination data and / or the intervention and adjustment of parameters by track control designers to perform track recursion.

7. The space-ground joint planning method for ultra-low orbit satellites according to claim 6, characterized in that, The step of monitoring key data from the received telemetry data and generating alarm level information includes: Based on the satellite long-tube diagnostic parameter status table, key data are monitored and judged to generate alarm level information.

8. A space-ground joint planning system for ultra-low orbit satellites, characterized in that, include: Mission planning system, orbit and ephemeris prediction system, operation control system, and anomaly handling system; among which: The task planning system is used to receive the load parameter file provided by the user, generate a task planning file, and then output it to the operation and control system. The orbit and ephemeris prediction system is used to obtain the six orbital elements of the satellite based on the GNSS telemetry data received by the operation and control system, predict the satellite's entry and exit from the shadow, and generate corresponding orbit control files and ephemeris files to output to the operation and control system; calculate the entry and exit times of the satellite for each orbit, and generate a shadow time file to output to the mission planning system. The operation and control system is used to receive the mission planning file, the orbit control file, and the ephemeris file, and to obtain the ephemeris instruction source code, orbit change parameter package instruction source code, and mission sequence instruction source code contained in the file and send them to the satellite; at the same time, it receives, forwards, and / or parses the telemetry data and data transmission files transmitted back from the satellite to realize satellite-ground interaction. The anomaly handling system is used to receive the telemetry data, monitor key data, and generate alarm level information; in: The task planning system generates a task planning file based on the load parameter file, including: Obtain the task type from the filename of the payload parameter file, which includes: stellar observation mission and solar observation mission; wherein: for stellar observation mission, obtain the mission start time from the filename of the payload parameter file and the relevant payload parameters encapsulated in the payload parameter file, load the relevant payload parameters into the payload parameter uploading instruction, obtain the instruction name and the source code of the payload parameter uploading instruction, and generate a mission planning file; For solar observation missions, the mission start time, mission count, and related payload parameters encapsulated in the payload parameter file are obtained from the filename of the payload parameter file. These related payload parameters are then loaded into the payload parameter annotation command to obtain the command name and payload parameter annotation command source code. Simultaneously, based on the shadow time file, the mission end time is recursively calculated according to the mission count and mission start time, generating a corresponding mission planning file. Wherein, the mission end time is the sum of the shadow entry time corresponding to the Nth exit from shadow and a fixed duration, where N is the mission count.

9. A computer terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it can be used to perform the method of any one of claims 1-7, or to run the system of claim 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program can be used to perform the method of any one of claims 1-7, or to run the system of claim 8.

Images