Satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system and method

Abstract

The present application relates to a kind of satellite load observation attitude control and data transmission, orbit control autonomous intelligent planning system and method, the system includes mission guide module, attitude control module, orbit control module and data transmission module;The attitude control module includes several thrusters for satellite attitude control, the orbit control module is used for satellite autonomous orbit control calculation, and carries out satellite orbit control, the data transmission module is used for satellite autonomous data transmission calculation, and satellite data is transmitted to ground;The mission guide module is in system control core, executes load observation task implementation strategy, according to priority reasonably arrange satellite's working time sequence, so that the satellite is intelligently switched between attitude control and data transmission to ground, orbit control, controls satellite autonomous intelligent operation in orbit.Autonomous intelligent planning, autonomous data transmission calculation, autonomous orbit control calculation are beneficial.

Description

[Technical Field]

[0001] This invention relates to the field of satellite control technology, specifically to a satellite payload observation attitude control and data transmission, and orbit control autonomous intelligent planning system and method. [Background Technology]

[0002] The basic function of telemetry is to transmit the engineering parameters of a spacecraft to the ground. The function of data transmission is to transmit the scientific data collected by the payload to the ground.

[0003] Existing satellite payload observation attitude control, data transmission and orbit control autonomous intelligent planning technologies have the following shortcomings:

[0004] Defect 1: Disconnection between payload observation attitude control and orbit control; When a satellite performs payload observation tasks, there are attitude requirements for the task, which often conflict with the attitude requirements of orbit control or the attitude accuracy during orbit control is insufficient, resulting in the inability to achieve seamless on-board autonomous connection between payload observation attitude control and orbit control.

[0005] Defect 2: Separation of payload observation data transmission from orbit control; Similar to defect 1, due to the high data downlink rate, the power consumption required is relatively large. Therefore, while saving onboard energy as much as possible, it is desirable to have a small angle between the direction of maximum gain and the direction of the star-ground connection. This places certain requirements on the onboard attitude, which will also lead to a conflict between the data transmission attitude requirements and the orbit control attitude requirements. Traditionally, both data transmission and orbit control are controlled by the ground, which means that the onboard cannot make full use of the non-data transmission time interval for data transmission.

[0006] Deficiency 3: Lack of system planning for payload observation attitude control, data transmission and orbit control; generally, satellite payload observation missions do not consider possible orbit control implementation. If a conflict occurs, there is no protection logic on the satellite, which may lead to the failure of the observation mission or even excessive satellite energy consumption leading to a reduction in battery life.

[0007] This invention addresses the technical problems of separation between attitude control and orbit control, separation between data transmission and orbit control, and lack of system planning in the autonomous and intelligent operation of satellites in orbit. It provides technical improvements to the autonomous and intelligent planning system and method for satellite payload observation attitude control, data transmission, and orbit control. [Summary of the Invention]

[0008] The purpose of this invention is to propose an autonomous intelligent planning system for satellite payload observation attitude control and data transmission, and orbit control, which enables autonomous intelligent planning, autonomous calculation of data transmission, and autonomous calculation of orbit control.

[0009] To achieve the above objectives, the technical solution adopted by this invention is a satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system, including an observation payload platform. The satellite operation includes during payload observation missions and between payload observation missions. The observation payload platform includes an observation payload for performing payload observation missions during payload observation missions; it also includes a mission guidance module, an attitude control module, an orbit control module, and a data transmission module. The attitude control module includes several thrusters for satellite attitude control, the orbit control module is used for the satellite to autonomously calculate orbit control and perform satellite orbit control, and the data transmission module is used for the satellite to autonomously calculate data transmission and transmit satellite data. Earth-to-ground transmission; the payload observation mission includes payload power-on initialization, observation period, and payload power-off. During the payload observation mission, the payload observation platform operates, the satellite payload observation attitude is maintained, and satellite orbit control is not possible. During the payload observation mission intervals, the payload observation platform turntable regains control of the mission guidance module, enabling satellite orbit control. The mission guidance module is at the core of the system control, executes the payload observation mission implementation strategy, and rationally arranges the satellite's working sequence according to priority, enabling the satellite to intelligently switch between attitude control, data transmission to Earth, and orbit control, thus controlling the satellite to operate autonomously and intelligently in orbit.

[0010] Preferably,

[0011] The data transmission module autonomously calculates data transmission and possesses the conditions required for autonomous data transmission on the satellite: data transmission ephemeris table or data transmission entry and exit ground commands, and ground station coordinates; the data transmission module autonomously calculates the power-on and power-off times, data reading and downlink logic, and related parameters based on the parameters from the ground uplink.

[0012] The orbit control module autonomously calculates orbit control and possesses the conditions required for autonomous orbit control on a satellite: orbit control trigger threshold parameters or orbit control ground commands. Based on the orbit control threshold parameters stored on the ground or on-board, and based on the collected orbit measurement data, the orbit control module calculates the difference between the parameters and the control threshold parameters through filtering and analysis methods. Taking into account certain engineering deviations, the module performs orbit control based on the trigger threshold parameters to ensure that the satellite can fly steadily under limited ground telemetry and control support.

[0013] Preferably,

[0014] For satellite payload observation missions at high orbital altitudes, the atmosphere is thinner, with lower density and less drag, resulting in slower satellite orbit decay. Ensuring the rapid transmission of mission data is the top priority. The priority of payload observation mission implementation strategies, from highest to lowest, is: payload observation attitude control > data transmission to Earth > orbit control.

[0015] For payload observation missions at low orbital altitudes, the atmosphere is relatively dense, resulting in high drag and rapid satellite orbit decay. Ensuring that the orbit does not decrease too quickly and cause the satellite to fall is the top priority. The priority of the payload observation mission implementation strategy, from high to low, is: payload observation attitude control > orbit control > data transmission to Earth.

[0016] Preferably, the high section refers to a track height of 280km, and the low section refers to a track height of less than 200km.

[0017] Preferably, the satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system achieves autonomous intelligent operation of the satellite in orbit through the interaction of the following flags and parameters:

[0018] The mission guidance module outputs the orbit control preparation flag Flag_GKZB to the attitude control module, and the attitude control module outputs attitude control parameters to the mission guidance module.

[0019] The task guidance module transmits the preparation flag Flag_SCZB to the attitude control module, and the attitude control module outputs the attitude establishment flag Flag_SCZT to the task guidance module.

[0020] The task guidance module outputs a data transmission start flag (Flag_SCKKS) to the data transmission module, and the data transmission module outputs a data transmission request flag (Flag_SCQQ) to the task guidance module.

[0021] The task guidance module outputs a flag (Flag_RW) indicating whether the current observation task has ended to the orbit control module. Flag_RW = 0x55 indicates that orbit control is possible, while Flag_RW = 0xAA indicates that orbit control is not possible. The orbit control module outputs a orbit control request flag (Flag_GKQQ) and the desired orbit control parameters to the task guidance module.

[0022] The attitude control module outputs the track control attitude establishment flag Flag_GKZT to the track control module, and the track control module outputs the track control flag Flag_GK to the attitude control module.

[0023] Another objective of this invention is to propose an autonomous intelligent planning method for satellite payload observation attitude control and data transmission and orbit control, which includes autonomous intelligent planning, autonomous calculation of data transmission, and autonomous calculation of orbit control.

[0024] To achieve the aforementioned objective, the present invention provides a high-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system. This satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system includes the following steps:

[0025] G1. Is the current observation task finished? Flag_RW = 0x55? If not, wait;

[0026] G2: Is there a data transmission request? If not, execute G5.

[0027] G3. Start data transmission attitude preparation according to the data transmission ephemeris table or data transmission entry / exit ground instructions;

[0028] G4 executes data transmission to ground; G1 is executed when data transmission ends.

[0029] G5: Is there a track control request? If not, execute G1.

[0030] G6. Start orbit control preparation according to the satellite's autonomous orbit control logic or orbit control ground instructions, and clear the payload observation mission sequence at the same time;

[0031] G7. Execute the high-segment track control method. After track control ends, execute G1.

[0032] Preferably, the high-segment track control method in step G7 includes the following steps:

[0033] G71. The orbit control module sends Flag_GKQQ=1 and the desired orbit control attitude angle to the mission guidance module, requesting orbit control.

[0034] G72. Is the current observation mission complete? Flag_RW = 0x55. If yes, send the orbit control request to the mission guidance module. The mission guidance module sends Flag_GKZB = 1 to the attitude control module to prepare for orbit control, and then the mission ends.

[0035] G73, the mission guidance module sends the "side-lying non-observation" rectifier mode and the "orbit system fixed pointing" guidance law to the attitude control module, and the mission guidance module sends Flag_GKZB=1 orbit control preparation to the attitude control module;

[0036] G74, Does the attitude control module send Flag_GKZT=1 to the track control module to establish track control attitude? If not, wait;

[0037] G75, has the track control module reached the controllable time calculated? If not, wait;

[0038] G76, The track control module sends Flag_GK=1 to the attitude control module;

[0039] G77, the attitude control module controls the corresponding thruster to start working;

[0040] G78, The track control module sends Flag_GK=0 to the attitude control module (not track control);

[0041] G79. The track control module sends a request for no track control (Flag_GKQQ=0) to the task guidance module.

[0042] G7a, the mission guidance module sends the "vertical non-observation" rectifier sub-mode and the "vertical non-biased flow" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=0 non-track control preparation to the attitude control module, and the process ends.

[0043] A low-stage autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system, comprising the following steps:

[0044] D1. Is the current observation task finished? Flag_RW = 0x55? If not, wait;

[0045] D2. Is there a track control request? If not, proceed to D5.

[0046] D3. Begin orbit control preparation based on the satellite's autonomous orbit control logic or ground commands for orbit control;

[0047] D4. Execute the low-segment track control method. After track control ends, execute D1.

[0048] D5. Is there a data transmission request? If not, execute D1.

[0049] D6. Begin data transmission attitude preparation according to the data transmission ephemeris table or data transmission entry / exit ground instructions.

[0050] D7. Execute the low-segment data to ground transmission method. After the data transmission ends, execute D1.

[0051] Preferably, the low-segment track control method in step D4 includes the following steps:

[0052] D41. The orbit control module sends Flag_GKQQ=1 and the desired orbit control attitude angle to the mission guidance module, requesting orbit control.

[0053] D42. Is the current observation mission complete? Flag_RW = 0x55. If yes, send the orbit control request to the mission guidance module. The mission guidance module sends Flag_GKZB = 1 to the attitude control module to prepare for orbit control, and then the mission ends.

[0054] D43. The mission guidance module sends the "side-lying non-observation" rectifier mode and the "orbit system fixed pointing" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=1 orbit control preparation to the attitude control module.

[0055] D44. Does the attitude control module send Flag_GKZT=1 to the track control module to establish track control attitude? If not, wait.

[0056] D45. Has the track control module reached the controllable time calculated? If not, wait.

[0057] D46. The track control module sends Flag_GK=1 to the attitude control module;

[0058] D47. The attitude control module controls the corresponding thruster to start working.

[0059] D48. The track control module sends Flag_GK=0 to the attitude control module (not track control).

[0060] D49. The track control module sends a request for no track control (Flag_GKQQ=0) to the task guidance module.

[0061] D4a. The mission guidance module sends the "lateral non-observation" rectifier sub-mode and the "lateral non-biased flow" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=0 non-track control preparation to the attitude control module, and the process ends.

[0062] Preferably, the low-band data to ground transmission method in step D7 includes the following steps:

[0063] D71. The data transmission module sends Flag_SCQQ=1 and the desired data transmission attitude angle to the task guidance module, requesting data transmission.

[0064] D72. Is the current observation task finished? Flag_RW = 0x55. If so, send a data transmission request to the task guidance module. The task guidance module sends Flag_SCZB = 1 to the attitude control module to prepare for data transmission, and then ends.

[0065] D73. The mission guidance module sends the "orbital system fixed pointing" guidance law to the attitude control module, and the mission guidance module sends Flag_SCZB=1 data transmission preparation to the attitude control module.

[0066] D74. Does the attitude control module send Flag_SCZT=1 to the task guidance module to establish the attitude? If not, wait.

[0067] D75. The task guidance module sends a data transmission start flag to the data transmission module.

[0068] D76. The data transmission module reads the ephemeris or transmits data upon arrival according to ground instructions, then ends.

[0069] The present invention provides an autonomous intelligent planning system and method for satellite payload observation attitude control, data transmission, and orbit control, which has the following beneficial effects:

[0070] Advantage 1: Autonomous intelligent planning. It can autonomously plan payload observation attitude control, data transmission and orbit control through on-board software, and reasonably arrange the working sequence of each satellite according to priority to ensure efficient and intelligent on-board operation.

[0071] Advantage 2: Autonomous data transmission calculation. The conditions required for autonomous data transmission on the satellite are: data transmission ephemeris (or data transmission entry and exit ground instructions), ground station coordinates, and the satellite can autonomously calculate the power-on and power-off times of the data transmission unit, data reading and downlink logic, and related parameters through the uplink parameters from the ground.

[0072] Advantage 3: Autonomous orbit control. The conditions required for onboard autonomous orbit control are: trigger threshold parameters for orbit control; the satellite calculates the difference between the orbit control threshold parameters stored on the ground or onboard, and the collected orbit measurement data, through filtering and analysis methods. Under the premise of considering certain engineering deviations, orbit control based on trigger threshold parameters ensures that the satellite can fly steadily under the premise of limited ground telemetry and control support. [Attached Image Description]

[0073] Figure 1 This is a diagram showing the relationship between software modules of a satellite payload observation attitude control and data transmission, and orbit control autonomous intelligent planning system.

[0074] Figure 2 This is a diagram showing the relationship between Flag_RW, the marker indicating whether the current observation task of the low-segment orbit control has ended, and the payload observation task in an autonomous intelligent planning system for satellite payload observation attitude control, data transmission, and orbit control.

[0075] Figure 3 This is a flowchart of the advanced autonomous planning process of a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system.

[0076] Figure 4 This is a flowchart of the high-segment orbit control process of a satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system.

[0077] Figure 5 This is a flowchart of the low-segment autonomous planning process of a satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system.

[0078] Figure 6 This is a flowchart of the low-segment orbit control process of a satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system.

[0079] Figure 7 This is a flowchart of the low-segment data transmission process of a satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system.

Detailed Implementation Methods

[0080] The present invention will now be further described with reference to the embodiments and the accompanying drawings.

[0081] Example 1

[0082] This embodiment implements an autonomous intelligent planning system for satellite payload observation attitude control, data transmission, and orbit control.

[0083] This embodiment of the system is based on an efficient payload observation mission implementation strategy, which includes intelligent switching between mission attitude control and data transmission and orbit control, solving the technical problem of satellite autonomous intelligent operation in orbit.

[0084] Figure 1 This is a diagram showing the module relationships within the load observation software. (See attached diagram.) Figure 1 As shown, this embodiment of the system is an implementation scheme for autonomous intelligent management of a satellite in orbit, specifically including an observation payload platform, a mission guidance module, an attitude control module, an orbit control module, and a data transmission module. The satellite operation includes during payload observation missions and between payload observation missions. The observation payload platform includes observation payloads for performing payload observation missions during payload observation missions. The attitude control module includes several thrusters for satellite attitude control. The orbit control module is used for the satellite to autonomously calculate orbit control and perform satellite orbit control. The data transmission module is used for the satellite to autonomously calculate data transmission and transmit satellite data to the ground.

[0085] The data transmission module autonomously calculates data transmission parameters and possesses the necessary conditions for autonomous onboard data transmission: a data transmission ephemeris (or data transmission entry / exit ground commands) and ground station coordinates. The satellite data transmission module can autonomously calculate the power-on / off times of the data transmission unit, data reading and downlink logic, and related parameters based on uplink parameters from the ground.

[0086] The orbit control module autonomously calculates orbit control parameters, possessing the necessary conditions for onboard autonomous orbit control: trigger threshold parameters for orbit control. Based on the orbit control threshold parameters stored on the ground or onboard, and simultaneously using acquired orbit measurement data, the satellite calculates the difference between the calculated parameters and the control threshold parameters through filtering and analysis methods. Taking into account certain engineering deviations, orbit control based on the trigger threshold parameters ensures that the satellite can achieve steady-state flight under limited ground-based telemetry and control support.

[0087] The mission guidance module is located at the core of the system control and executes the payload observation mission implementation strategy, enabling the satellite to intelligently switch between attitude control, data transmission to the ground, and orbit control, and rationally arrange the working sequence of each satellite according to priority, so as to control the satellite to operate autonomously and intelligently in orbit.

[0088] This embodiment of the system involves onboard autonomous logic for attitude mission planning, data transmission, and orbit control. The mission guidance module executes the payload observation mission implementation strategy and determines the priority based on the orbital altitude. Figure 2 This is a diagram showing the relationship between Flag_RW (indicating whether the current observation task has ended) and the payload observation task in a satellite payload observation attitude control and data transmission, and orbit control autonomous intelligent planning system. (See attached diagram.) Figure 2As shown, the payload observation mission implementation strategy involves the flag Flag_RW indicating whether the current observation mission has ended. During the payload observation mission, including payload power-on initialization, observation period, and payload power-off, the payload observation platform is operational, the satellite attitude is maintained, and orbit control is not possible; during this period, the flag Flag_RW = 0xAA. During the gaps between payload observation missions, the payload observation platform's turntable master control returns to the mission guidance module, orbit control is possible, and the flag Flag_RW = 0x55.

[0089] For missions at altitudes below 280km, the atmosphere is thinner, with lower density and less drag, resulting in slower satellite orbit decay. Ensuring rapid data transmission is the top priority. Therefore, the priority of these three functions, from highest to lowest, is: payload observation and attitude control > data transmission > orbit control. For missions with orbital altitudes below 200km, the atmosphere is denser, with greater drag, resulting in faster satellite orbit decay. Ensuring the orbit doesn't drop too quickly and cause satellite reentry is the top priority. Therefore, the priority of these three functions, from highest to lowest, is: payload observation and attitude control > orbit control > data transmission.

[0090] Specifically, in this embodiment, the system achieves autonomous and intelligent on-orbit operation of the satellite through the interaction of the following flags and information:

[0091] The mission guidance module outputs the orbit control preparation flag Flag_GKZB to the attitude control module, and the attitude control module outputs the attitude angle and attitude angular velocity to the mission guidance module.

[0092] The task guidance module outputs a data transmission start flag (Flag_SCKKS) to the data transmission module, and the data transmission module outputs a data transmission request flag (Flag_SCQQ) to the task guidance module.

[0093] The mission guidance module outputs a flag (Flag_RW) indicating whether the current observation mission has ended to the orbit control module. Flag_RW = 0x55 indicates orbit controllable, and Flag_RW = 0xAA indicates orbit control not possible. The orbit control module outputs a orbit control request flag (Flag_GKQQ), as well as the desired roll angle, pitch angle, and yaw angle to the mission guidance module.

[0094] The attitude control module outputs the track control attitude establishment flag Flag_GKZT to the track control module, and the track control module outputs the track control flag Flag_GK to the attitude control module.

[0095] The advantages of this system lie in its functionality, primarily in the following aspects: Advantage 1: Autonomous intelligent planning, enabling it to autonomously plan tasks, data transmission, and orbit control through onboard software, and rationally arrange the working sequence of each satellite according to priority, ensuring efficient and intelligent onboard operation. Advantage 2: Autonomous calculation of data transmission; Advantage 3: Autonomous calculation of orbit control.

[0096] Example 2

[0097] This embodiment implements a high-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system. The method in this embodiment is based on the system implemented in Embodiment 1.

[0098] Figure 3 This is a flowchart of the advanced autonomous planning process for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system. (See attached flowchart.) Figure 3 As shown, for a mission at 280km, the atmosphere is relatively thin, with low density and low drag, resulting in slow satellite orbit decay. Ensuring rapid data transmission is the top priority. Therefore, the priorities of the three—mission, data transmission, and orbit control—are as follows: Mission > Data Transmission > Orbit Control. The specific implementation process is as follows:

[0099] G1. Is the current observation task finished? Flag_RW = 0x55? If not, wait;

[0100] G2: Is there a data transmission request? If not, execute G5.

[0101] G3. Start data transmission attitude preparation according to the data transmission ephemeris table or ground command;

[0102] G4 executes data transmission to ground; G1 is executed when data transmission ends.

[0103] G5: Is there a track control request? If not, execute G1.

[0104] G6. Start orbit control preparation according to the satellite's autonomous orbit control logic or ground instructions, and clear the payload observation mission sequence at the same time;

[0105] G7. Execute the high-segment track control method. After track control ends, execute G1.

[0106] Figure 4 This is a flowchart of the high-segment orbit control process for a satellite payload observation attitude control and data transmission, and orbit control autonomous intelligent planning system. (See attached flowchart.) Figure 4 As shown, the high-segment (280km) track control logic of this embodiment, step G7 of the high-segment track control method flow is as follows:

[0107] G71. The orbit control module sends Flag_GKQQ=1 and the desired orbit control attitude angle to the mission guidance module, requesting orbit control.

[0108] G72. Is the current observation mission complete? Flag_RW = 0x55. If yes, send the orbit control request to the mission guidance module. The mission guidance module sends Flag_GKZB = 1 to the attitude control module to prepare for orbit control, and then the mission ends.

[0109] G73, the mission guidance module sends the "side-lying non-observation" rectifier mode and the "orbit system fixed pointing" guidance law to the attitude control module, and the mission guidance module sends Flag_GKZB=1 orbit control preparation to the attitude control module;

[0110] G74. Does the attitude control module send Flag_GKZT=1 to the attitude control module to establish the attitude? If yes, wait; Flag_GKZT=1: established, Flag_GKZT=0: not established;

[0111] G75, has the track control module reached the controllable time calculated? If not, wait;

[0112] G76. The track control module sends Flag_GK=1 track control to the attitude control module; Flag_GK=1: track control, meaning track control is required; Flag_GK=0: no track control, meaning track control is not required.

[0113] G77, the attitude control module controls the corresponding thruster to start working;

[0114] G78, The track control module sends Flag_GK=0 to the attitude control module (not track control);

[0115] G79. The track control module sends a request for no track control (Flag_GKQQ=0) to the task guidance module.

[0116] G7a, the mission guidance module sends the "vertical non-observation" rectifier sub-mode and the "vertical non-biased flow" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=0 non-track control preparation to the attitude control module, and the process ends.

[0117] This embodiment demonstrates a high-segment track control example: track altitude 280km.

[0118] [T0, T0+40min]: The execution time interval of the payload observation mission, with no transmission requests and no track control requests.

[0119] (T0+40min, T0+120min): During the interval between payload observation missions, there are numerous transmission requests but no track control requests.

[0120] (T0+120min, T0+130min): The execution time interval of the payload observation mission, with no transmission requests and no track control requests.

[0121] (T0+130min, T0+135min): The execution time interval of the payload observation mission, during which data transmission requests were rejected and there were no track control requests.

[0122] (T0+135min, T0+160min): The execution time interval of the payload observation mission, during which numerous transmission requests are made, and some orbit control requests are rejected (but orbit control requests continue to be sent).

[0123] T0+160min: During the gap in payload observation missions, numerous transmission requests occur, including orbit control requests. Immediately responding to orbit control requests is crucial, as the entire orbit control process can take anywhere from 3 to 96 minutes. Therefore, the mission sequence originally scheduled to restart at T0+240min is cancelled.

[0124] T0+220min: During the interval between payload observation tasks, data transmission requests are rejected but will continue to be sent because there are track control requests and track control has not ended.

[0125] T0+220min10s: During the payload observation mission interval, there is a data transmission request 1 minute before entry into orbit, but no track control request. One minute before entry into orbit, preparation for data transmission attitude begins, preparing to enter the data transmission logic flow.

[0126] (T0+225min10s, T0+230min): During the interval between payload observation missions, there is a data transmission request but no track control request. The data transmission area is also within the telemetry and control area, and it is the sequence of payload observation mission commands sent up after T0+360min.

[0127] (T0+230min, T0+360min): During the interval between load observation tasks, there is a data transmission request but no track control request.

[0128] (T0+360min, T0+400min): The execution time interval of the payload observation mission, with no transmission requests and no track control requests.

[0129] (T0+400min, T0+480min): During the interval between load observation missions, there are numerous transmission requests but no track control requests.

[0130] ...

[0131] After 20 minutes of observation, the payload observation time interval is arranged according to the height of natural orbit decay. No data transmission is performed during the observation mission, and no orbit control is performed during the entire mission time interval.

[0132] Example 3

[0133] This embodiment implements a low-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system. This method is based on the system implemented in Embodiment 1.

[0134] Figure 5 This is a flowchart of the low-stage autonomous planning process for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system. (See attached flowchart.) Figure 5As shown, for missions requiring orbit maintenance due to high atmospheric density, the denser atmosphere results in greater drag and faster orbital decay. Ensuring the orbit doesn't deteriorate too quickly and cause the satellite to fall is the top priority. Therefore, the priority of the three (mission, orbit control, and data transmission) is as follows: Mission > Orbit Control > Data Transmission. The specific implementation process is as follows:

[0135] D1. Is the current observation task finished? Flag_RW = 0x55? If not, wait;

[0136] D2. Is there a track control request? If not, proceed to D5.

[0137] D3. Begin orbit control preparation based on satellite autonomous orbit control logic or ground commands;

[0138] D4. Execute the low-segment track control method. After track control ends, execute D1.

[0139] D5. Is there a data transmission request? If not, execute D1.

[0140] D6. Start data transmission attitude preparation according to the data transmission ephemeris table or ground command;

[0141] D7. Execute the low-segment data to ground transmission method. After the data transmission ends, execute D1.

[0142] Figure 6 This is a flowchart of the low-segment orbit control process for a satellite payload observation attitude control and data transmission, and orbit control autonomous intelligent planning system. (See attached flowchart.) Figure 6 As shown, the low-segment (track height below 200km) track control logic of this embodiment is illustrated in step D4, which is the low-segment track control method flow as follows:

[0143] D41. The orbit control module sends Flag_GKQQ=1 and the desired orbit control attitude angle to the mission guidance module, requesting orbit control.

[0144] D42. Is the current observation mission complete? Flag_RW = 0x55. If yes, send the orbit control request to the mission guidance module. The mission guidance module sends Flag_GKZB = 1 to the attitude control module to prepare for orbit control, and then the mission ends.

[0145] D43. The mission guidance module sends the "side-lying non-observation" rectifier mode and the "orbit system fixed pointing" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=1 orbit control preparation to the attitude control module.

[0146] D44. Does the attitude control module send Flag_GKZT=1 to the track control module to establish track control attitude? If not, wait.

[0147] D45. Has the track control module reached the controllable time calculated? If not, wait.

[0148] D46. The track control module sends Flag_GK=1 to the attitude control module;

[0149] D47. The attitude control module controls the corresponding thruster to start working.

[0150] D48. The track control module sends Flag_GK=0 to the attitude control module (not track control).

[0151] D49. The track control module sends a request for no track control (Flag_GKQQ=0) to the task guidance module.

[0152] D4a. The mission guidance module sends the "lateral non-observation" rectifier sub-mode and the "lateral non-biased flow" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=0 non-track control preparation to the attitude control module, and the process ends.

[0153] The main differences between the orbital control logic for low-level and high-level tasks are twofold:

[0154] 1. The instruction sequence will no longer be deleted in the lower segment because the dense atmosphere at low orbit causes high aerodynamic drag, which leads to rapid satellite orbit decay. Orbit maintenance is frequent and the specific time is unpredictable and consumes a lot of fuel. Therefore, the mission execution sequence will be prepared one day in advance, which has fully taken into account the impact of orbit decay. There is no need to change the payload observation process due to orbit control.

[0155] 2. After the orbit control jetting is completed, for the lower section, a side-lying non-biased flow guidance is sent to the attitude control. The purpose is to minimize the windward area and ensure that jetting can be performed at any time without performing tasks or data transmission.

[0156] Figure 7 This is a flowchart of the low-segment data transmission process for a satellite payload observation attitude control and data transmission, and orbit control autonomous intelligent planning system. (See attached flowchart.) Figure 7 As shown, the method in this embodiment describes the low-segment (orbital altitude below 200km) data transmission logic. Low-segment data transmission requires close cooperation between the satellite and ground. However, whether it is ground control or the satellite autonomously controlling the power on / off of the data transmission unit based on the ephemeris, the data transmission module must first issue a data transmission request flag. Then, the mission guidance integrates the mission and attitude control status, and feeds back a data transmission start flag to the data transmission module before data transmission can proceed. Step D7, the low-segment data to ground transmission method flow, is as follows:

[0157] D71. The data transmission module sends Flag_SCQQ=1 and the desired data transmission attitude angle to the task guidance module, requesting data transmission.

[0158] D72. Is the current observation task finished? Flag_RW = 0x55. If so, send a data transmission request to the task guidance module. The task guidance module sends Flag_SCZB = 1 to the attitude control module to prepare for data transmission, and then ends.

[0159] D73. The mission guidance module sends the "orbital system fixed pointing" guidance law to the attitude control module, and the mission guidance module sends Flag_SCZB=1 data transmission preparation to the attitude control module.

[0160] D74. Does the attitude control module send Flag_SCZT=1 to the task guidance module to establish the attitude? If not, wait.

[0161] D75. The task guidance module sends a data transmission start flag to the data transmission module.

[0162] D76. The data transmission module reads the ephemeris or transmits data upon arrival according to ground instructions, then ends.

[0163] Example 1 of low-segment track control in this embodiment: Track altitude below 200km - higher stage

[0164] [T0, T0+20min]: The execution time interval of the payload observation mission, with no transmission requests and no track control requests.

[0165] (T0+20min, T0+100min): During the interval between load observation missions, there are numerous transmission requests but no track control requests.

[0166] (T0+100min, T0+105min): During the interval between payload observation tasks, there is a data transmission request 1 minute before entry into orbit, but no track control request. 1 minute before entry into orbit, the data transmission logic is entered, the attitude is adjusted to a data transmission attitude 1 minute later, data is transmitted 3 minutes later, and the attitude is adjusted back to the non-mission routine attitude 1 minute later.

[0167] (T0+105min, T0+200min): During the interval between load observation missions, there are numerous transmission requests but no track control requests.

[0168] (T0+200min, T0+220min): The execution time interval of the payload observation task, during which data transmission requests were rejected and no track control requests were made.

[0169] ...

[0170] The system operates in a two-hour cycle of 40-minute observations followed by 80-minute intervals. If there are data transmission or track control requests, they are executed according to the priority of the software logic.

[0171] Example 2 of low-segment track control in this embodiment: Track altitude below 200km - lower stage

[0172] [T0, T0+15min]: The execution time interval of the payload observation mission, with no transmission requests and no track control requests.

[0173] (T0+15min, T0+45min): During the intervals between payload observation missions, numerous transmission requests occur, including orbit control requests. The orbit control requests must be responded to immediately. The entire orbit control process should take less than 40 seconds; therefore, orbit control requests must be rejected starting 140 seconds before the mission begins, allowing 100 seconds for attitude adjustment.

[0174] (T0+45min, T0+60min): The execution time interval of the payload observation mission, with no transmission requests and no track control requests.

[0175] (T0+60min, T0+120min): During the interval between load observation missions, there are numerous transmission requests and track control requests. Track control operations are the same as those between (T0+15min, T0+45min).

[0176] (T0+120min, T0+135min): The execution time interval of the payload observation mission, with no transmission requests and no track control requests.

[0177] [T0+135min, T0+223min]: The payload observation mission ends, numerous transmission requests and track control requests are received. The track is raised to a specific height through two track control operations.

[0178] After T0+223 minutes: The payload observation mission ends. One minute before entry, there is a data transmission request, but no track control request. Two minutes before entry, data transmission attitude preparation begins, and the system enters data transmission logic within the territory.

[0179] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM).

[0180] The above description is only a preferred embodiment of the present invention. It should be noted that those skilled in the art can make several improvements and additions without departing from the principle of the present invention, and these improvements and additions should also be considered within the scope of protection of the present invention.

Claims

1. A satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system, comprising an observation payload platform, wherein satellite operation includes payload observation missions during and between payload observation missions, and the observation payload platform includes an observation payload for performing payload observation missions during payload observation missions; characterized in that: It also includes a mission guidance module, an attitude control module, an orbit control module, and a data transmission module. The attitude control module includes several thrusters for satellite attitude control. The orbit control module is used for the satellite to autonomously calculate orbit control and perform satellite orbit control. The data transmission module is used for the satellite to autonomously calculate data transmission and transmit satellite data to the ground. During the payload observation mission, the observation payload is powered on and initialized, observed, and powered off. During the payload observation mission, the payload observation platform is operational, the satellite payload observation attitude is maintained, and satellite orbit control is not possible. During the gaps between payload observation missions, the payload observation platform turntable regains control of the mission guidance module, and satellite orbit control can be performed. The mission guidance module is at the core of the system control, executes the payload observation mission implementation strategy, and rationally arranges the satellite's working sequence according to priority, enabling the satellite to intelligently switch between attitude control, data transmission to the ground, and orbit control, and control the satellite to operate autonomously and intelligently in orbit.

2. The satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system according to claim 1, characterized in that: The data transmission module autonomously calculates data transmission and possesses the conditions required for autonomous data transmission on the satellite: data transmission ephemeris table or data transmission entry and exit ground commands, and ground station coordinates; the data transmission module autonomously calculates the power-on and power-off times, data reading and downlink logic, and related parameters based on the parameters from the ground uplink. The orbit control module autonomously calculates orbit control and possesses the conditions required for autonomous orbit control on a satellite: orbit control trigger threshold parameters or orbit control ground commands. Based on the orbit control threshold parameters stored on the ground or on-board, and based on the collected orbit measurement data, the orbit control module calculates the difference between the parameters and the control threshold parameters through filtering and analysis methods. Taking into account certain engineering deviations, the module performs orbit control based on the trigger threshold parameters to ensure that the satellite can fly steadily under limited ground telemetry and control support.

3. The satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system according to claim 2, characterized in that: For satellite payload observation missions at high orbital altitudes, the atmosphere is thinner, with lower density and less drag, resulting in slower satellite orbit decay. Ensuring the rapid transmission of mission data is the top priority. The priority of payload observation mission implementation strategies, from highest to lowest, is: payload observation attitude control > data transmission to Earth > orbit control. For payload observation missions at low orbital altitudes, the atmosphere is relatively dense, resulting in high drag and rapid satellite orbit decay. Ensuring that the orbit does not decrease too quickly and cause the satellite to fall is the top priority. The priority of the payload observation mission implementation strategy, from high to low, is: payload observation attitude control > orbit control > data transmission to Earth.

4. The satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system according to claim 3, characterized in that: The "high section" refers to a track altitude of 280km, and the "low section" refers to a track altitude of less than 200km.

5. The satellite payload observation attitude control and data transmission, orbit control autonomous intelligent planning system according to claim 3, characterized in that... The satellite achieves autonomous and intelligent operation in orbit through the interaction of the following flags and parameters: The mission guidance module outputs the orbit control preparation flag Flag_GKZB to the attitude control module, and the attitude control module outputs attitude control parameters to the mission guidance module. The task guidance module transmits the preparation flag Flag_SCZB to the attitude control module, and the attitude control module outputs the attitude establishment flag Flag_SCZT to the task guidance module. The task guidance module outputs a data transmission start flag (Flag_SCKKS) to the data transmission module, and the data transmission module outputs a data transmission request flag (Flag_SCQQ) to the task guidance module. The task guidance module outputs a flag (Flag_RW) indicating whether the current observation task has ended to the orbit control module. Flag_RW = 0x55 indicates that orbit control is possible, while Flag_RW = 0xAA indicates that orbit control is not possible. The orbit control module outputs a orbit control request flag (Flag_GKQQ) and the desired orbit control parameters to the task guidance module. The attitude control module outputs the track control attitude establishment flag Flag_GKZT to the track control module, and the track control module outputs the track control flag Flag_GK to the attitude control module.

6. A high-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system, based on the satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system described in claim 5, characterized in that... Includes the following steps: G1. Is the current observation task finished? Flag_RW = 0x55? If not, wait; G2: Is there a data transmission request? If not, execute G5. G3. Start data transmission attitude preparation according to the data transmission ephemeris table or data transmission entry / exit ground instructions; G4 executes data transmission to ground; G1 is executed when data transmission ends. G5: Is there a track control request? If not, execute G1. G6. Start orbit control preparation according to the satellite's autonomous orbit control logic or orbit control ground instructions, and clear the payload observation mission sequence at the same time; G7. Execute the high-segment track control method. After track control ends, execute G1.

7. The high-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system according to claim 6, characterized in that... The G7 high-segment track control method includes the following steps: G71. The orbit control module sends Flag_GKQQ=1 and the desired orbit control attitude angle to the mission guidance module, requesting orbit control. G72. Is the current observation mission complete? Flag_RW = 0x55. If yes, send the orbit control request to the mission guidance module. The mission guidance module sends Flag_GKZB = 1 to the attitude control module to prepare for orbit control, and then the mission ends. G73, the mission guidance module sends the "side-lying non-observation" rectifier mode and the "orbit system fixed pointing" guidance law to the attitude control module, and the mission guidance module sends Flag_GKZB=1 orbit control preparation to the attitude control module; G74, Does the attitude control module send Flag_GKZT=1 to the track control module to establish track control attitude? If not, wait; G75, has the track control module reached the controllable time calculated? If not, wait; G76, The track control module sends Flag_GK=1 to the attitude control module; G77, the attitude control module controls the corresponding thruster to start working; G78, The track control module sends Flag_GK=0 to the attitude control module (not track control); G79. The track control module sends a request for no track control (Flag_GKQQ=0) to the task guidance module. G7a, the mission guidance module sends the "vertical non-observation" rectifier sub-mode and the "vertical non-biased flow" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=0 non-track control preparation to the attitude control module, and the process ends.

8. A low-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system, based on the satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system described in claim 5, characterized in that... Includes the following steps: D1. Is the current observation task finished? Flag_RW = 0x55? If not, wait; D2. Is there a track control request? If not, proceed to D5. D3. Begin orbit control preparation based on the satellite's autonomous orbit control logic or ground commands for orbit control; D4. Execute the low-segment track control method. After track control ends, execute D1. D5. Is there a data transmission request? If not, execute D1. D6. Begin data transmission attitude preparation according to the data transmission ephemeris table or data transmission entry / exit ground instructions. D7. Execute the low-segment data to ground transmission method. After the data transmission ends, execute D1.

9. The low-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system according to claim 8, characterized in that... Step D4, the low-segment track control method, includes the following steps: D41. The orbit control module sends Flag_GKQQ=1 and the desired orbit control attitude angle to the mission guidance module, requesting orbit control. D42. Is the current observation mission complete? Flag_RW = 0x55. If yes, send the orbit control request to the mission guidance module. The mission guidance module sends Flag_GKZB = 1 to the attitude control module to prepare for orbit control, and then the mission ends. D43. The mission guidance module sends the "side-lying non-observation" rectifier mode and the "orbit system fixed pointing" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=1 orbit control preparation to the attitude control module. D44. Does the attitude control module send Flag_GKZT=1 to the track control module to establish track control attitude? If not, wait. D45. Has the track control module reached the controllable time calculated? If not, wait. D46. The track control module sends Flag_GK=1 to the attitude control module; D47. The attitude control module controls the corresponding thruster to start working. D48. The track control module sends Flag_GK=0 to the attitude control module (not track control). D49. The track control module sends a request for no track control (Flag_GKQQ=0) to the task guidance module. D4a. The mission guidance module sends the "side-lying non-observation" rectifier sub-mode and the "side-lying non-biased flow" guidance law to the attitude control module. The mission guidance module sends Flag_GKZB=0 non-track control preparation to the attitude control module, and the process ends.

10. The low-segment autonomous planning method for a satellite payload observation attitude control, data transmission, and orbit control autonomous intelligent planning system according to claim 8, characterized in that... Step D7, the low-band data to ground transmission method, includes the following steps: D71. The data transmission module sends Flag_SCQQ=1 and the desired data transmission attitude angle to the task guidance module, requesting data transmission. D72. Is the current observation task finished? Flag_RW = 0x55. If so, send a data transmission request to the task guidance module. The task guidance module sends Flag_SCZB = 1 to the attitude control module to prepare for data transmission, and then ends. D73. The mission guidance module sends the "orbital system fixed pointing" guidance law to the attitude control module, and the mission guidance module sends Flag_SCZB=1 data transmission preparation to the attitude control module. D74. Does the attitude control module send Flag_SCZT=1 to the task guidance module to establish the attitude? If not, wait. D75. The task guidance module sends a data transmission start flag to the data transmission module. D76. The data transmission module reads the ephemeris or transmits data upon arrival according to ground instructions, then ends.

Images