WO2021103451A1 - 一种卫星数据处理方法、装置及卫星备份子系统 - Google Patents

一种卫星数据处理方法、装置及卫星备份子系统 Download PDF

Info

Publication number
WO2021103451A1
WO2021103451A1 PCT/CN2020/092405 CN2020092405W WO2021103451A1 WO 2021103451 A1 WO2021103451 A1 WO 2021103451A1 CN 2020092405 W CN2020092405 W CN 2020092405W WO 2021103451 A1 WO2021103451 A1 WO 2021103451A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
task
backup
satellite
track
Prior art date
Application number
PCT/CN2020/092405
Other languages
English (en)
French (fr)
Inventor
周舒婷
王珑
袁振博
王磊
Original Assignee
成都星时代宇航科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 成都星时代宇航科技有限公司 filed Critical 成都星时代宇航科技有限公司
Priority to US17/419,703 priority Critical patent/US11416292B2/en
Publication of WO2021103451A1 publication Critical patent/WO2021103451A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1438—Restarting or rejuvenating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G06F9/4887—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues involving deadlines, e.g. rate based, periodic
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1456—Hardware arrangements for backup
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2015—Redundant power supplies

Definitions

  • This application relates to the field of satellite technology, and specifically, provides a satellite data processing method, device, and satellite backup subsystem.
  • One way is to restart the equipment on the satellite using hot backup.
  • the principle of hot backup is to put at least two pieces of the same hardware on the satellite, install the same system in each piece of hardware, and install the same system on each piece of hardware. The system does the same thing synchronously, if one of them is broken, it will switch to the other.
  • the cost of host backup in this method is high, multiple hardware is required, and power consumption is high.
  • the power on the satellite is very limited. Once the power is exhausted, the satellite cannot be used.
  • Another way is to use a system restore method to restart the equipment on the satellite, which restores the currently running system to the initial state of the system.
  • the system restore method is adopted.
  • the system restore method can only restore the system to the initial state, and restore it to the initial state.
  • the process of the system and the process of updating the initial state of the system to the system that was running before the restoration, it will inevitably affect the normal execution of the satellite mission;
  • second, in the process of system restoration due to the large amount of data, It also takes a long time. If there is an abnormal situation such as a power failure on the way, it may cause the restoration to fail, which will lead to more time and cost to restore the restoration.
  • the purpose of this application is to provide a satellite data processing method, device, and satellite backup subsystem, so as to improve some of the problems that exist in the backup solutions adopted for the equipment on the satellite.
  • the embodiment of the application provides a satellite data processing method, which is applied to a satellite backup subsystem, and the method includes:
  • a data receiving task where the data task includes data backup or data restoration;
  • breakpoint backup or breakpoint restoration is adopted to split a complete data task into multiple single-track tasks for segment execution, so as to realize the backup or restoration of the satellite on-orbit system, thereby solving some other problems.
  • the backup method cannot achieve the problem of on-track backup or restore operations.
  • splitting the data task into multiple single-track tasks includes:
  • the data task is split into multiple single-orbit tasks.
  • the task can be quickly split into multiple single-orbit tasks based on the total time for executing the data task and the estimated time that the satellite is allowed to execute the data task during a round orbit flight, which can simplify the splitting process.
  • estimating the length of time during which the satellite is allowed to execute the data task during a round orbit flight includes:
  • the time length for which the satellite is permitted to perform data tasks during one orbiting flight is estimated.
  • splitting the data task into multiple single-track tasks includes:
  • the data task is split into multiple single-track tasks according to the permitted execution time of the data task in each orbital flight and the remaining data task amount of the data task.
  • the data task is split into multiple single-track tasks based on the time allowed to execute the data task in each orbital flight and the remaining data task amount of the data task, so that the data task is split into multiple tasks.
  • a single-track mission it is possible to fully consider the difference between the permitted execution time of the data mission in different orbital flights, so as to make more reasonable use of resources and make the splitting effect more efficient.
  • the data task is split into multiple single-track tasks according to the permitted execution time of the data task in each orbital flight and the remaining data task amount of the data task ,include:
  • the duration of the data backup or data restoration operation permitted in the current orbiting flight is less than the duration required by the remaining data task of the data task, then the data backup or data restoration is permitted to be executed in the current orbiting flight The duration of the operation, dividing the remaining data of the data task into the single-track task that needs to be performed for this orbiting flight and the remaining data task after subtracting the single-track task that needs to be performed for the current orbiting flight;
  • the single-track task to be performed for the orbiting flight is the data task The remaining data tasks.
  • the remaining data of the data task is calculated based on the duration of the data backup or data restoration operation during this orbital flight determined on the previous orbit, and the duration required for the remaining data task of the calculated data task.
  • the task is split, the electric energy in the storage battery can be fully and reasonably used, and the waste of resources can be avoided.
  • executing respective corresponding single-track tasks includes:
  • the technical means of breakpoint backup or breakpoint restoration is used to record the start flag bit of data backup or data restoration in the single-track mission during this orbital flight, and the end flag bit when the recording is completed , So that when performing data backup or data restoration in a single-orbit mission during the next orbital flight, there are traces to follow, realize the backup or restore of the satellite on-orbit system, and solve the problems of some other backup methods.
  • recording the start flag of the data backup or data restoration in the single-track task execution this time includes:
  • the end flag will start to record the data backup or data restoration this time. If the end flag indicating the completion of the last operation is not recorded in the file, the start flag bit of this data backup or data restoration will be recorded from the beginning to improve the reliability of the device, or , To record the start flag bit of this data backup or data restore from the last corresponding end flag bit to save the time of backup or restore.
  • the task of receiving data includes:
  • the data task instruction carries a device identifier, and the device identifier is configured to indicate a device on which the data task is to be executed;
  • the satellite backup subsystem when receiving a data task instruction from the ground station, it sends an inquiry request to the ground station, and after receiving the confirmation instruction, the satellite backup subsystem determines that the data task is received, and then performs data backup or restoration , Can reduce the risk of misoperation.
  • the method further includes:
  • the execution of the current single-track task is stopped to avoid hardware damage to the backup memory.
  • the embodiment of the present application also provides a satellite data processing method, which is applied to a ground station, and the method includes:
  • the data task instruction carries a device identifier, and the device identifier is configured to indicate the device on which the data task is to be executed;
  • the confirmation instruction carries multiple single-orbit sub-times, each single-orbit sub-time represents the time period during which the satellite is permitted to perform the data task in one orbital flight, and the sum of the multiple single-orbit sub-times is equal to the total duration.
  • the total time required for data backup or data restoration of the device corresponding to the device identification is carried in the query request, so that the ground station performs data backup or data restoration for each track according to the total time.
  • An embodiment of the present application also provides a satellite backup subsystem, including: a backup memory and a processor, and the backup memory is connected to the processor;
  • the backup memory is configured to store backup data
  • the processor is configured to receive a data task, wherein the data task includes data backup or data restoration; and is also configured to split the data task into a plurality of single-track tasks; and in each orbital flight Is configured to execute respective corresponding single-track tasks to back up the data in the memory corresponding to the device that needs to execute the data task to the backup memory, or restore the backup data in the backup memory to the memory .
  • An embodiment of the present application also provides a satellite data processing device, which is applied to a ground station, and the device includes:
  • the first sending module is configured to receive a data task instruction from a ground station, the data task instruction carries a device identifier, and the device identifier is configured to indicate a device on which the data task is to be executed;
  • the receiving module is configured to receive an inquiry request sent by the satellite in response to the data task instruction whether it is necessary to execute the data task on the device corresponding to the device identification, and the inquiry request carries the identification of the device The total time required for the corresponding device to execute the data task;
  • the second sending module is configured to send a confirmation instruction to the satellite, so that the satellite backup subsystem in the satellite, according to the single-orbit sub-time length carried in the confirmation instruction, executes the sub-orbital execution corresponding to the single-orbit sub-time length Single track mission;
  • the confirmation instruction carries multiple single-orbit sub-times, each single-orbit sub-time represents the time period during which the satellite is permitted to perform the data task in one orbital flight, and the sum of the multiple single-orbit sub-times is equal to the total duration.
  • An embodiment of the present application also provides a satellite backup subsystem, including: a backup memory and a processor, and the backup memory is connected to the processor;
  • the backup memory is configured to store backup data
  • a computer program is solidified in the processor, and the processor is configured to execute the above-mentioned satellite data processing method by running the computer program.
  • the embodiment of the present application also provides a computer-readable storage medium, the readable storage medium stores a computer program, and the computer program executes the above-mentioned satellite data processing method when the computer program is run by a processor.
  • the embodiments of the present application also provide a computer program product, which when running on a computer, causes the computer to execute the above-mentioned satellite data processing method.
  • Fig. 1 shows a schematic flowchart of a satellite data processing method applied to a satellite backup subsystem provided by an embodiment of the present application.
  • FIG. 2 shows a schematic diagram of the flow of each execution of a single-track task provided by an embodiment of the present application.
  • FIG. 3 shows a schematic flowchart of a data backup or restoration operation after an abnormal power failure and restart according to an embodiment of the present application.
  • Fig. 4 shows a schematic diagram of modules of a satellite data processing device applied to a ground station provided by an embodiment of the present application.
  • Figure 5 shows a schematic structural diagram of a backup subsystem provided by an embodiment of the present application.
  • the embodiments of the present application provide a satellite data processing method that uses breakpoint backup and breakpoint restoration technical means to realize satellite on-orbit system backup Or restore to solve the problems of some backup methods.
  • some system backup schemes can only restore the system to the initial state. If the state of the system changes in the middle, it cannot meet the requirements.
  • on-orbit system backup means that after a device has been running for a period of time, if the current state meets the backup requirements, the current state is set as a restore point and data backup is performed through on-orbit backup. , If a failure occurs later, just restore the system to the restore point that was backed up.
  • satellites In the process of flying around the earth, satellites generally rely on energy storage batteries and solar panels to convert solar energy to supply power.
  • the power of the energy storage battery is determined by the time the satellite is launched into the sky. Therefore, the power of the energy storage battery is limited, and the solar panels can convert solar energy into solar energy.
  • the solar panels can receive solar energy. ; But when the satellite is in the backlight, it cannot receive solar energy, or it receives very little solar energy.
  • the deployment area of the solar panels carried on the satellites and the conversion rate of the solar panels are limited. Therefore, the power on the satellites is limited.
  • the startup time for a satellite to orbit is generally between 10-40 minutes.
  • the daily tasks of the satellite must be completed first, and the remaining time can be used for backup tasks such as restoration.
  • the remaining time is often not enough to complete a complete backup or restore, which may cause the backup to fail.
  • this application adopts the solution of breakpoint backup and breakpoint restoration to realize the backup or restoration of the satellite's on-orbit system.
  • the backup and restoration tasks are divided into multiple single-orbit tasks, and during an orbital flight (each Track) to perform a single track task.
  • FIG. 1 is a satellite data processing method applied to a satellite backup subsystem in a satellite according to an embodiment of this application. The steps involved will be described below in conjunction with FIG. 1.
  • Step 101 Receive data task.
  • the ground station can send a data task instruction to the satellite, and the satellite backup subsystem performs subsequent operations after receiving the data task instruction ; For example, get the total time required to perform a complete data task.
  • the data task may include data backup or data restoration.
  • the satellite backup subsystem can perform subsequent operations when it receives the data task of the ground station. For example, in the above example, the satellite backup subsystem receives the data task of the ground station, and then obtains what is needed to perform a complete data task. Total duration.
  • the satellite backup subsystem in order to avoid misoperation, when the satellite backup subsystem receives the data task instruction, it can also send to the ground station whether it needs to correspond to the device identification carried by the data task instruction.
  • the device executes the inquiry request of the data task, and after receiving the confirmation instruction sent by the ground station in response to the inquiry request, the satellite backup subsystem determines that the received data task can be executed in order to perform subsequent operations.
  • the data task instruction may carry a device identifier, and the device identifier may be configured to indicate the device on which the data task is to be executed.
  • the satellite backup subsystem can send satellite status parameters to the ground station, which can include the operating parameters of the equipment on the satellite; when the equipment on the satellite has been operating for a period of time, if the current status meets the backup requirements, Then the ground station can send data backup instructions to the satellite.
  • the ground station can send data backup instructions to the satellite. For example, when a system has not failed during a preset period of time (for example, 2 months), it means that the current state is relatively stable, and it can be backed up.
  • the device can also be backed up regularly, for example, once every fixed time interval (for example, 2 months).
  • Step 102 Split the data task into multiple single-track tasks.
  • the satellite backup subsystem can split the received data task into multiple (two or more) single-track tasks.
  • the satellite backup subsystem splits the data task into multiple (two or more) single-orbit tasks, which can be completed in multiple times; for example, the satellite backup subsystem can be completed according to each orbit During the flight, the time allowed to execute the data task and the remaining data task amount of the data task, the data task is divided into multiple single-track tasks.
  • the satellite backup subsystem can determine the length of time allowed to perform data tasks in each orbiting flight according to the following rules; for example, the satellite backup subsystem can be based on the power of the satellite during the previous orbiting flight and the remaining amount to be backed up or restored.
  • the amount of data tasks determines the length of time allowed to perform data backup or data restoration during this orbiting flight; then, the satellite backup subsystem can be based on the amount of power of the satellite during this orbiting flight and the remaining amount of data tasks to be backed up or restored, Determine the time allowed for data backup or data restoration in the next orbiting flight; when splitting the task, the satellite backup subsystem can calculate the remaining time required for the data task and determine the time allowed in this orbiting flight Whether the duration of the data backup or data restoration operation is less than the calculated duration required for the remaining data task volume of the data task; if the duration of the data backup or data restoration operation permitted during the orbiting flight is less than the remaining data task duration According to the length of time required for the data mission, the satellite backup subsystem can split the remaining data of the data mission into the single-orbit mission that needs to be performed for this orbital flight according to the time allowed to perform data backup or data restoration during this orbital flight.
  • the duration of the data backup or data restoration operation allowed during the Nth bypass flight is 20 minutes; then during the Nth bypass flight, if the satellite backup is The time required for the subsystem to calculate the remaining data task volume after completing the data task is about 30 minutes, because the time (20 minutes) allowed to perform the data backup or data restoration operation during the Nth bypass flight is less than the remaining data after the backup or restoration.
  • the satellite backup subsystem can split the remaining data of the data mission into the single track that needs to be executed for this (Nth) orbital flight Tasks and data tasks remaining after subtracting the single-orbit mission that needs to be performed for this (Nth) orbiting flight; in the N+1th bypassing flight, assuming that the data is permitted to be executed during the N+1th bypassing flight
  • the duration of the backup or data restoration operation is 15 minutes.
  • the duration required to perform the remaining data task amount of the data task is 10 minutes, which is less than the time allowed to perform data backup during this (N+1th) bypass flight or The duration of the data restoration operation (15 minutes), the single-track task to be performed for this (N+1th) orbital flight is the remaining data task of the data task, that is, the split is completed.
  • the satellite backup subsystem splits the data task into multiple single-track tasks, which can also be completed at one time, that is, when the data backup or data restoration is about to start, the data task will be executed. Split into multiple single track tasks.
  • the satellite backup subsystem may split the data task into multiple single orbits based on the total time required to perform the data task and the estimated time for the satellite to perform the data task during a round orbit flight. task. For example, assuming that the total time required to perform a complete data mission on a certain device on a satellite is 65 minutes, and the estimated time allowed to execute the data mission during a satellite orbit flight is 15 minutes, the satellite backup subsystem can Based on the total time (65 minutes) and the estimated time (15 minutes) that the satellite is allowed to perform the data task during a round orbit flight of the satellite, the data task is divided into 5 single-orbit tasks, of which the first 4 single-orbit tasks correspond to The sub-times are all 15 minutes, and the corresponding sub-time of the last single-track task is 5 minutes.
  • the satellite backup subsystem can estimate the satellite's one-time orbit based on the average value of the duration of data backup or data restoration configured during each orbital flight of the satellite at multiple historical moments. The length of time allowed to perform data tasks during orbital flight.
  • the satellite backup subsystem can use the average of the duration of data backup or data restoration configured for the first 5 orbits to estimate the duration of the data mission permitted to execute during a satellite orbit.
  • the satellite backup subsystem may also estimate the length of time the satellite is permitted to execute the data task during an orbital flight based on the current satellite power.
  • single-track sub-duration can be completed by the ground station (satellite platform) in addition to the satellite backup subsystem.
  • the satellite backup subsystem can obtain the device identification carried in the data mission instruction to determine the device corresponding to the device identification to perform a complete data backup task or restore task location. The total time required, and divide the single track time.
  • the satellite backup subsystem can send to the ground station whether it is necessary to perform data backup or data restoration on the device corresponding to the device identifier carried in the instruction.
  • Request after receiving the confirmation instruction sent by the ground station in response to the inquiry request, perform the corresponding backup or restore operation.
  • the task division can be performed by the satellite backup subsystem, or it can be performed by the satellite's main system, and then the main system sends the divided multiple single-orbit tasks to the satellite backup subsystem.
  • the satellite backup subsystem can realize information interaction with the ground station based on the communication module of the satellite main system (such as Beidou communication module). For example, when the satellite main system receives an instruction from the ground station, it can forward the instruction to the satellite backup subsystem When the satellite backup subsystem needs to send an inquiry request to the ground station, the inquiry request can be sent to the satellite master system, and then the satellite master system sends the inquiry request to the ground station.
  • the satellite backup subsystem can obtain the device identification carried in the data task instruction and determine the The total time required for the device corresponding to the device identification to perform a complete data backup task or restore task, and respond to the data task instruction to send an inquiry request to the ground station whether it is necessary to perform data backup or data restoration; where the inquiry request carries The total duration.
  • the ground station After the ground station obtains the total time in the query request, it can divide the task based on the total time, and then send a confirmation command to the satellite.
  • the confirmation command can carry multiple (two or more) single-track sub-times.
  • a single-orbit sub-time indicates the length of time that the satellite is allowed to perform data backup or data restoration during an orbital flight. The sum of the duration of all single tracks is equal to the total duration. It can be seen that in this embodiment, the ground station can assign tasks to the satellites and control the satellites by sending instructions to the satellites.
  • the query request sent to the ground station may not carry the device corresponding to the device identification.
  • the query request needs to carry the total time length. Accordingly, at this time, the determination instruction returned by the ground station carries at least two single track sub-time lengths.
  • Step 103 Perform the respective single-track missions each time the orbital flight.
  • the satellite backup subsystem can combine multiple single-orbit missions obtained above, and execute the corresponding single-orbit mission of each orbit each time it orbits. For ease of understanding, in conjunction with the flowchart shown in FIG. 2 for each execution of a single-track task, the execution of each orbital corresponding single-track task during each orbital flight is described.
  • Step 103a Record the start flag bit of the data backup or data restoration in this single-track task execution.
  • the satellite backup subsystem When the satellite backup subsystem performs data backup or data restoration in this single-track mission, it can record the start flag of the data backup or data restoration in this single-track mission.
  • the satellite backup subsystem when the satellite backup subsystem records the start flag of this data backup or data restoration: you can first check whether there is a characterization distance and the closest time of this orbital flight recorded in the file. Point’s data backup or restore end flag bit; if the file records the end flag bit that characterizes the data backup or data restore at the closest time point of the orbiting flight (if yes), then the satellite backup subsystem The start flag bit of this data backup or data restoration can be recorded from the last corresponding end flag bit; if the data backup or data corresponding to the nearest time point of the orbiting flight is not recorded in the file The end of the restoration flag (when it is No), the satellite backup subsystem can record the start flag of this data backup or data restoration. For example, the satellite backup subsystem can start from the first corresponding start flag. Start recording the start flag of the current data backup or data restoration, or the satellite backup subsystem can start recording the start flag of the current data backup or data restoration from the last corresponding end flag.
  • the satellite backup subsystem when the satellite backup subsystem records the start flag of the data backup or data restoration in this single-orbit mission, if the document records the characteristic distance to the nearest orbital flight.
  • the end flag bit of data backup or restoration that is, when the file does not indicate the end flag bit of the data backup or restoration corresponding to the completion of the last orbital flight, it indicates that the last backup or restore failed, as a possibility
  • the satellite backup subsystem can re-backup or restore from the beginning to improve reliability. At this time, the satellite backup subsystem can start recording the data backup or data restoration
  • the satellite backup subsystem can also perform data backup or data restoration from the last corresponding end flag bit, so as to save the need for re-backing up or restoring from the beginning.
  • the start flag bit of this data backup or data restoration is recorded from the end flag bit corresponding to the last time.
  • Step 103b Starting from the start flag of the data backup or data restoration in the single-track task, execute the data backup or data restoration in the single-track task.
  • the satellite backup subsystem can record the start flag of the data backup or data restoration in this single-track mission, and then start from the start flag. At the beginning, perform data backup or data restoration according to the time allowed to perform data backup or data restoration in this single-track task.
  • Step 103c When the data backup or data restoration in the corresponding single-track task is executed, the end flag when the execution is completed is recorded.
  • the satellite backup subsystem when the satellite backup subsystem completes the data backup or data restoration in the corresponding single-track mission, that is, when the data backup or data restoration is performed for the duration of the single-track mission, the data backup or data restoration is permitted to be performed When the duration is, you can record the end flag at the time of completion to end this time. In this way, when the next data backup or data restoration is performed, the satellite backup subsystem can first check whether the file has an end flag indicating the completion of the last backup, and if so, start execution from the end flag indicating the completion of the last backup This time data backup or data restoration.
  • the satellite backup subsystem can record the start flag in the file, and then back up the data to the backup memory; in the single-track When the backup task is completed, the satellite backup subsystem can record the backup end flag in the file; when the single-track backup task is executed for the second time and thereafter, the satellite backup subsystem can first check whether there is a record in the file indicating that the last backup was completed. End flag bit; if there is, the satellite backup subsystem can start to record the start flag bit from the last end flag bit, then back up the data to the backup memory, and record it in the recording file when the single-track backup task is executed. End flag; if not, it means the previous failure. The satellite backup subsystem can record the start flag of this data backup from the first corresponding start flag, or from the last corresponding The end mark bit starts to record the start mark bit of this data backup.
  • the satellite backup subsystem when the satellite backup subsystem performs data backup or restoration, in order to save electricity, all unrelated peripherals can be turned off during this period, such as turning off the equipment configured for aerial photography, and only the power supply of key components such as the satellite backup subsystem is retained. To speed up the restoration speed.
  • the satellite backup subsystem can also monitor the power supply voltage during the execution of a single-track mission (data backup or data restoration), and when it is monitored that the power supply voltage continues to drop or drops to a set point When the threshold is reached, stop the current data backup or data restoration.
  • a single-track mission data backup or data restoration
  • an execution unit with a power-down detection function can be selected to execute the corresponding.
  • the aforementioned power failure detection refers to executing a predetermined protection strategy when the power supply voltage continues to drop or drops to a set threshold, for example, stopping the current single-track task (data backup or data restoration), and turning off its own power supply.
  • an energy storage device such as a capacitor, that uses power for the backup memory can also be set, so that after the backup subsystem is abnormally powered off, the capacitor can be used to temporarily delay the backup memory. Power-off time, thereby protecting the backup memory and improving the reliability of the equipment. Since the power supply voltage continues to drop or drops to the set threshold, the execution unit generally no longer writes or reads data to the backup memory, and the power supply to the backup memory has not completely stopped at this time, and then configure the capacitor for energy storage. Effectively delay the power-off time of the backup memory to protect the backup memory.
  • the satellite backup subsystem when the satellite backup subsystem starts to perform data backup or data restoration, it can detect whether there is an end flag indicating that the data backup or data restoration was completed last time; if so, it means uploading. If the second backup or restore is successful, the satellite backup subsystem can continue the current data backup or data restoration from the last end flag bit; if not, it means the last backup or restore failed, and the satellite backup subsystem can restart from the beginning Restart the current data backup or data restoration, or continue the current data backup or data restoration from the last end flag bit.
  • the schematic diagram of the process is shown in Figure 3.
  • the embodiment of the present application also provides a satellite data processing device 200 applied to the ground station, as shown in FIG. 4 Show.
  • the satellite data processing device 200 may include: a first sending module 210, a receiving module 220, and a second sending module 230.
  • the first sending module 210 is configured to send a data task instruction to the satellite, the data task instruction carries a device identifier, and the device identifier is configured to indicate a device for which the data task is to be executed.
  • the receiving module 220 is configured to receive an inquiry request sent by the satellite in response to the data task instruction whether it is necessary to perform a data task on the device corresponding to the device identifier, and the inquiry request carries a data backup task or a restore task for the device corresponding to the device identifier. The total time required.
  • the second sending module 230 is configured to send a confirmation instruction to the satellite, so that the satellite backup subsystem in the satellite executes the single-orbit task corresponding to the single-orbit sub-duration according to the single-orbit sub-duration carried in the confirmation instruction.
  • the instruction carries multiple single orbit sub-times. Each single-orbit sub-time indicates the time period during which the satellite is allowed to perform data backup or data restoration during an orbital flight. The sum of the multiple single-orbit sub-times is equal to the total time.
  • FIG. 5 shows a structural block diagram of a satellite backup subsystem 300 provided by an embodiment of the present application.
  • the embedded system in the figure may be an object to be backed up or restored, and the system memory may be configured to store data of the embedded system.
  • the satellite backup subsystem 300 may include: a power management unit 310, a backup memory 320, and a processor 330.
  • the power management unit 310 can supply power to the backup memory 320 and the processor 330.
  • the satellite backup subsystem 300 can realize information interaction with the ground station based on the communication module (Beidou communication module) of the satellite main system. For example, when the satellite receives an instruction from the ground station, the instruction can be sent to the satellite backup subsystem 300. When the satellite backup subsystem 300 needs to send an inquiry request to the ground station, the inquiry request may be sent to the satellite main system, and the satellite main system sends the inquiry request to the ground station.
  • the communication module Beidou communication module
  • the backup memory 320 may be configured to store backup data.
  • System programs can be solidified in the processor.
  • the system program may include at least one system function module that may be solidified in the operating system (OS) of the satellite backup subsystem 300 in the form of a system or firmware (firmware).
  • OS operating system
  • firmware firmware
  • the processor 330 can be configured to receive a data task, where the data task is a data backup task or a data restoration task; and can also be configured to split the data task into multiple single-track tasks; When flying, they are configured to execute their corresponding single-track missions to back up data in the memory corresponding to the device that needs to perform data missions to the backup memory, or restore the backup data in the backup memory to the memory.
  • the backup memory 320 may be, but is not limited to, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), and programmable read-only memory (Programmable Read-Only Memory, PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc.
  • RAM Random Access Memory
  • ROM read only memory
  • PROM Programmable Read-Only Memory
  • PROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • the processor 330 may be an integrated circuit chip with signal processing capability.
  • the above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (DSP), a dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the general-purpose processor may be a microprocessor or the processor 330 may also be any conventional processor or the like.
  • each block in the flowchart or block diagram may represent a module, program segment, or part of code, and the above-mentioned module, program segment, or part of code includes one or more modules configured to implement prescribed logical functions. Executable instructions.
  • the functions marked in the block may also occur in a different order from the order marked in the drawings.
  • each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or actions Or it can be realized by a combination of dedicated hardware and computer instructions.
  • the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.
  • this function is implemented in the form of a system function module and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a system product, and the computer system product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a notebook computer, a server, or a network device, etc.) execute all or part of the steps of the methods provided in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
  • the embodiments of the present application also provide a computer program product, which can execute the methods involved in the above method embodiments provided by the present application when the computer program product runs on a computer.
  • the electronic devices, computer storage media, and computer program products provided in the embodiments of the present application can all be configured to execute the corresponding methods provided in the foregoing embodiments. Therefore, the beneficial effects that can be achieved can be referred to The beneficial effects of the corresponding methods provided above will not be repeated here.
  • breakpoint backup or breakpoint restore Due to the use of breakpoint backup or breakpoint restore technical solutions, a complete data task can be split into multiple single-track tasks to be executed in stages to achieve satellite on-orbit system backup or restore, thereby solving some other backup methods that cannot be achieved. Problems with on-track backup or restore operations.
  • the task can be quickly split into multiple single-orbit tasks based on the total time to execute the data task and the estimated time allowed to execute the data task during one orbit of the satellite, which can simplify the splitting process.
  • the data task is split into multiple single-track tasks, so that the data task is split into multiple single-track tasks. It can fully consider the difference between the time length of the data task permitted to execute the data task in different orbital flights, and can use resources more reasonably, making the splitting effect more efficient.
  • the start flag bit for data backup or data restoration in the single-track mission is recorded, and the end flag bit when the recording is completed, so that the data backup or data backup in the single-track mission is performed during the next orbital flight.
  • the start flag bit for data backup or data restoration in the single-track mission is recorded, and the end flag bit when the recording is completed, so that the data backup or data backup in the single-track mission is performed during the next orbital flight.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Radio Relay Systems (AREA)
  • Position Fixing By Use Of Radio Waves (AREA)
  • Retry When Errors Occur (AREA)

Abstract

一种卫星数据处理方法、装置（200）及卫星备份子系统（300），属于卫星技术领域。该方法应用于卫星备份子系统（300），该方法包括：接收数据任务（101），其中，该数据任务包括数据备份任或数据还原；将所述数据任务拆分成多个单轨任务（102）；在每次绕轨飞行时，执行各自对应的单轨任务（103）。该方法采用断点备份或断点还原的方案，将一次完整的数据任务拆分为多个单轨任务并分段执行，以实现卫星在轨系统的备份或还原。

Description

一种卫星数据处理方法、装置及卫星备份子系统
相关申请的交叉引用
本申请要求于2019年11月29日提交中国专利局的申请号为2019112103374、名称为“一种卫星数据处理方法、装置及卫星备份子系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及卫星技术领域，具体而言，提供一种卫星数据处理方法、装置及卫星备份子系统。
背景技术
卫星上的设备在运行过程中可能出现例如宇宙射线照射等造成的异常掉电等情况，当卫星上的设备出现上述情况时，可能会出现数据存储出错，而数据存储出错则可能直接导致设备无法正常工作。
为了使得卫星上的设备能够重新正常工作，提供了一些解决方案以解决上述问题。其中一种方式为：采用热备份的方式重新启动卫星上的设备，其中热备份的原理是在卫星上放至少两台一样的硬件，每台硬件里面安装一样的系统，且每台硬件上的系统同步做一样的事情，若其中一台坏了，就切换到另一台。但是，这种方式中主机备份的成本高，需要多台硬件，耗电量也高，而卫星上的电量非常有限，一旦电量消耗完毕，卫星将无法使用。
另一种方式则为：采用系统还原的方式重新启动卫星上的设备，其使得现在正在运行的系统还原至该系统的初始状态。但采用系统还原的方式，其一，如果正在运行的系统在使用中通过卫星数传上行链路进行了版本的更新，采用系统还原的方式只能将系统恢复到初始状态，而还原至初始状态的系统的过程中，和初始状态的系统更新至还原前正在运行的系统的过程中，势必会影响到卫星任务的正常执行；其二，在系统还原的过程中，因其数据量较大，所花费的时间也较长，若途中存在异常情况如掉电等时，则可能造成还原失败，从而导致耗费更多的时间成本去进行还原恢复。
发明内容
本申请的目的在于提供一种卫星数据处理方法、装置及卫星备份子系统，以改善一些针对卫星上的设备所采用的备份方案所存在的问题。
为实现上述目的，本申请采用的技术方案如下：
本申请实施例提供了一种卫星数据处理方法，应用于卫星备份子系统，所述方法包括：
接收数据任务，其中，所述数据任务包括数据备份或数据还原；
将所述数据任务拆分成多个单轨任务；
在每次绕轨飞行时，执行各自对应的单轨任务。
本申请实施例中，采用断点备份或断点还原的技术方案，将一次完整的数据任务拆分为多个单轨任务分段执行，以实现卫星在轨系统备份或还原，进而解决一些其他的备份方式无法实现在轨备份或还原操作的问题。
可选地，作为一种可能的实现方式，将所述数据任务拆分成多个单轨任务，包括：
获取执行所述数据任务所需的总时长；
预估所述卫星一次绕轨飞行时准许执行所述数据任务的时长；
基于所述总时长和所述卫星一次绕轨飞行时准许执行所述数据任务的时长，将所述数据任务拆分成多个单轨任务。
本申请实施例中，根据执行该数据任务的总时长和预估的卫星一次绕轨飞行时准许执行数据任务的时长可快速地将该任务拆分成多个单轨任务，能够简化拆分流程。
可选地，作为一种可能的实现方式，预估所述卫星一次绕轨飞行时准许执行所述数据任务的时长，包括：
根据多个历史时刻所述卫星在每次绕轨飞行时配置的执行数据备份或数据还原的时长的平均值，预估所述卫星一次绕轨飞行时准许执行数据任务的时长。
可选地，作为一种可能的实现方式，将所述数据任务拆分成多个单轨任务，包括：
根据每次绕轨飞行中准许执行所述数据任务的时长和所述数据任务的剩余数据任务量，将所述数据任务拆分成多个单轨任务。
本申请实施例中，根据每次绕轨飞行中准许执行该数据任务的时长和该数据任务的剩余数据任务量，将该数据任务拆分成多个单轨任务，使得将数据任务拆分成多个单轨任务时，能够充分考虑不同次绕轨飞行中准许执行该数据任务的时长间的差异，更能合理利用资源，使得拆分效果更高效。
可选地，作为一种可能的实现方式，根据每次绕轨飞行中准许执行所述数据任务的时长和所述数据任务的剩余数据任务量，将所述数据任务拆分成多个单轨任务，包括：
根据上次绕轨飞行时，卫星的电量以及待备份或待还原的剩余数据任务量，确定本次绕轨飞行中准许执行数据备份或者数据还原操作的时长；
计算所述数据任务的剩余数据任务所需的时长；
判断所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长是否小于所述数据任务的剩余数据任务量所需的时长；
若所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长小于所述数据任务的剩余数据任务所需的时长，则根据所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长，将所述数据任务的剩余数据拆分为本次绕轨飞行需执行的单轨任务和减去所述本次绕轨飞行需执行的单轨任务之后剩余的数据任务；
若所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长不小于所述数据任务的剩余数据任务所需的时长，则本次绕轨飞行需执行的单轨任务为所述数据任务的剩余数据任务。
本申请实施例中，通过在上一轨确定的本次绕轨飞行时执行数据备份或者数据还原操作的时长，以及计算的数据任务的剩余数据任务所需的时长，从而对数据任务的剩余数据任务进行拆分，可以充分且合理的使用蓄电池中的电能，避免资源的浪费。
可选地，作为一种可能的实现方式，执行各自对应的单轨任务，包括：
记录本次执行所述单轨任务中的数据备份或者数据还原的起始标志位；
从所述单轨任务中数据备份或者数据还原的所述起始标志位开始，执行所述单轨任务中的数据备份或者数据还原；
在执行完对应的所述单轨任务中的数据备份或者数据还原时，记录执行完时的结束标志位。
本申请实施例中，采用断点备份或断点还原的技术手段，在本次绕轨飞行时记录执行单轨任务中的数据备份或者数据还原的起始标志位，以及记录完成时的结束标志位，使得在下次绕轨飞行时执行单轨任务中的数据备份或者数据还原时，有迹可循，实现卫星在轨系统备份或还原，进而解决一些其他备份方式存在的问题。
可选地，作为一种可能的实现方式，记录本次执行所述单轨任务中的数据备份或者数据还原的起始标志位，包括：
查看文档中是否记录有表征距离与本次绕轨飞行的最近时间点的数据备份或者数据还原的结束标志位；
若所述文档中记录有表征距离与本次绕轨飞行的最近时间点的数据备份或者数据还原的结束标志位，则从上一次对应的结束标志位开始记录本次执行数据备份或者数据还原的起始标志位；
若所述文档中并未记录有表征距离与本次绕轨飞行的最近时间点对应的数据备份或者数据还原的结束标志位，记录本次执行数据备份或者数据还原的起始标志位。
本申请实施例中，若文档中记录有表征距离与本次绕轨飞行的最近时间点的数据备份或者还原的结束标志位时，则从该结束标志位开始记录本次执行数据备份或者数据还原的起始标志位，若文档中没有记录有表征完成上一次操作的结束标志位时，则从头重新开始 记录本次执行数据备份或者数据还原的起始标志位，以提高设备的可靠性，或者，从上上次对应的结束标记位开始记录本次执行数据备份或者数据还原的起始标志位，以节约备份或还原的时间。
可选地，作为一种可能的实现方式，接收数据任务，包括：
接收来自地面站的数据任务指令，所述数据任务指令中携带有设备标识，所述设备标识被配置成指示待执行数据任务的设备；
向所述地面站发送是否需要对所述设备标识所对应的设备执行所述数据任务的询问请求；
在接收所述地面站响应所述询问请求发送的确认指令时，表征接收到所述数据任务。
本申请实施例中，在接收到来自地面站的数据任务指令时，通过向地面站发送询问请求，并在接收到确定指令后，卫星备份子系统确定接收到数据任务，然后执行数据备份或还原，能够降低误操作的风险。
可选地，作为一种可能的实现方式，在执行单轨任务的过程中，所述方法还包括：
当监测到供电电压持续下降或者下降到设定阈值时，停止执行当前的单轨任务。
本申请实施例中，当监测到供电电压持续下降或者下降到设定阈值时，停止执行当前的单轨任务，以避免备用存储器硬件性地损坏。
本申请实施例还提供一种卫星数据处理方法，应用于地面站，所述方法包括：
向卫星发送数据任务指令，所述数据任务指令中携带有设备标识，所述设备标识被配置成指示待执行数据任务的设备；
接收所述卫星响应所述数据任务指令发送的是否需要对所述设备标识所对应的设备执行所述数据任务的询问请求，所述询问请求中携带有对所述设备标识所对应的设备执行所述数据任务所需的总时长；
向所述卫星发送确认指令，以使所述卫星中的卫星备份子系统根据所述确认指令中携带的单轨子时长，分轨执行与所述单轨子时长所对应的单轨任务；
其中，所述确认指令中携带有多个单轨子时长，每个单轨子时长表示卫星在一次绕轨飞行中准许执行所述数据任务的时长，所述多个单轨子时长之和等于所述总时长。
本申请实施例中，通过在询问请求中携带对设备标识所对应的设备执行数据备份或者数据还原所需的总时长，以便地面站根据该总时长对每一轨执行数据备份或者数据还原的时长进行划分，并将划分好的多个单轨子时长携带在确认指令中发给卫星的卫星子系统，使得卫星子系统可以直接基于划分好的单轨子时长执行对应的操作即可，可节约卫星的能耗资源。
本申请实施例还提供一种卫星备份子系统，包括：备用存储器和处理器，所述备用存储器和所述处理器连接；
所述备用存储器，被配置成存储备份数据；
所述处理器，被配置成接收数据任务，其中，所述数据任务包括数据备份或数据还原；以及还被配置成将所述数据任务拆分成多个单轨任务；并在每次绕轨飞行时，被配置成执行各自对应的单轨任务，以将需要执行所述数据任务的设备对应的存储器中的数据备份至所述备用存储器，或者将所述备用存储器中的备份数据还原至所述存储器。
本申请实施例还提供一种卫星数据处理装置，应用于地面站，所述装置包括：
第一发送模块，被配置成接收来自地面站的数据任务指令，所述数据任务指令中携带有设备标识，所述设备标识被配置成指示待执行数据任务的设备；
接收模块，被配置成接收所述卫星响应所述数据任务指令发送的是否需要对所述设备标识所对应的设备执行所述数据任务的询问请求，所述询问请求中携带有对所述设备标识所对应的设备执行所述数据任务所需的总时长；
第二发送模块，被配置成向所述卫星发送确认指令，以使所述卫星中的卫星备份子系统根据所述确认指令中携带的单轨子时长，分轨执行与所述单轨子时长所对应的单轨任务；
其中，所述确认指令中携带有多个单轨子时长，每个单轨子时长表示卫星在一次绕轨飞行中准许执行所述数据任务的时长，所述多个单轨子时长之和等于所述总时长。
本申请实施例还提供一种卫星备份子系统，包括：备用存储器和处理器，所述备用存储器和所述处理器连接；
所述备用存储器，被配置成存储备份数据；
所述处理器中固化有计算机程序，所述处理器被配置成通过运行所述计算机程序，执行上述的卫星数据处理方法。
本申请实施例还提供一种计算机可读存储介质，该可读存储介质上存储有计算机程序，该计算机程序被处理器运行时执行上述的卫星数据处理方法。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品在计算机上运行时，使得计算机执行上述的卫星数据处理方法。
附图说明
图1示出了本申请实施例提供的一种应用于卫星备份子系统中的卫星数据处理方法的流程示意图。
图2示出了本申请实施例提供的每次执行单轨任务的流程示意图。
图3示出了本申请实施例提供的一种异常掉电重启后，再次进行数据备份或还原操作时的流程示意图。
图4示出了本申请实施例提供的一种应用于地面站中的卫星数据处理装置的模块示意图。
图5示出了本申请实施例提供的一种备份子系统的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案执行描述。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其执行进一步定义和解释。同时，在本申请的描述中诸如“第一”、“第二”等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
再者，本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
鉴于一些针对卫星的数据备份采用的一些备份方案所存在的缺陷，本申请实施例提供了一种卫星数据处理方法，采用断点备份和断点还原的技术手段，以实现卫星的在轨系统备份或还原，进而解决一些备份方式存在的问题，例如，一些系统备份方案只能将系统恢复到初始状态，若中途系统的状态发生改变，则不能满足要求。
整体上讲，在轨系统备份是指，当一台设备在运行了一段时间后，若当前的状态满足备份要求，则将当前的状态设置为一个还原点并通过在轨备份的方式进行数据备份，若之后发生故障，就将系统还原到所备份的还原点即可。
卫星在绕地球飞行的过程中，一般是靠储能电池和太阳能帆板转化太阳能来供电。但储能电池的电量由卫星发射上空时所决定，因此该储能电池的电量有限，而太阳能帆板转化太阳能的电能也有限，比如当卫星处于迎光面时，太阳能帆板能接收到太阳能；但是当卫星处于背光面时，便不能接收到太阳能，或者接收到的太阳能会很少。此外，卫星上携带的太阳能帆板的展开面积以及太阳能帆板的转化率都有限，因此，卫星上电力有限。
以立方星为例，通常卫星绕轨一周(飞完一轨)大约需要90分钟，为了节省卫星上有限的电能，卫星绕轨一周的开机时间一般在10-40分钟之间。在这10-40分钟的时间里，首先要完成卫星的日常任务，剩余的时间才能去做还原等的备份工作，然而剩余的时间往往不够完成一次完整的备份或还原，从而可能导致备份失败。
因此，本申请采用断点备份和断点还原的方案来实现卫星的在轨系统备份或还原，简单地讲，就是将备份和还原任务分成多个单轨任务，在一次绕轨飞行中(每一轨)执行一个单轨任务。
请参阅图1，为本申请实施例提供的一种应用于卫星中的卫星备份子系统中的卫星数据处理方法，下面将结合图1对其所包含的步骤执行说明。
步骤101：接收数据任务。
在一些可能的实施方式中，当需要对卫星上的某个设备执行数据任务，可以由地面站向卫星发送数据任务指令，卫星备份子系统在接收到该数据任务指令后，便执行后续的操作；例如，获取执行一次完整数据任务所需的总时长。其中，该数据任务可以包括数据备份或数据还原。
卫星备份子系统可以在接收到地面站的数据任务时，便执行后续的操作，例如在上述的示例中，卫星备份子系统接收到地面站的数据任务，便获取执行一次完整数据任务所需的总时长。
当然，在本申请其他一些可能的实施方式中，为了避免误操作，卫星备份子系统在接收到数据任务指令时，还可以向地面站发送是否需要对该数据任务指令携带的设备标识所对应的设备执行数据任务的询问请求，并在接收到地面站响应该询问请求发送的确认指令后，卫星备份子系统确定可以执行接收到的数据任务，以便执行后续的操作。其中，数据任务指令中可以携带有设备标识，该设备标识可以被配置成指示待执行数据任务的设备。
另外，卫星备份子系统可以向地面站发送卫星的状态参数，该状态参数可以包含有卫星上的设备的运行参数；当卫星上的设备在运行了一段时间后，若当前的状态满足备份要求，则地面站便可以向卫星发送数据备份指令。例如，当一个系统在运行预设时长(例如2个月)期间均未出过故障，就说明目前这个状态比较稳定，那么就可以对它进行备份。此外，也可定期对设备进行数据备份，例如，每间隔固定时长(例如2个月)就进行一次备份。
步骤102：将数据任务拆分成多个单轨任务。
卫星备份子系统可以将接收到的数据任务拆分成多个(两个及以上)单轨任务。
其中，作为一种可能的实施方式，卫星备份子系统将数据任务拆分成多个(两个及以上)单轨任务可以是分多次完成的；比如，卫星备份子系统可以根据每次绕轨飞行中准许执行该数据任务的时长和数据任务的剩余数据任务量，将该数据任务拆分成多个单轨任务。
其中，卫星备份子系统可以根据以下规律来确定每次绕轨飞行中准许执行数据任务的时长；例如，卫星备份子系统可以根据上一次绕轨飞行时，卫星的电量以及待备份或还原的剩余数据任务量，确定本次绕轨飞行中准许执行数据备份或者数据还原的时长；然后，卫星备份子系统可以根据本次绕轨飞行时，卫星的电量以及待备份或还原的剩余数据任务量，确定下一次绕轨飞行中准许执行数据备份或者数据还原的时长；在进行任务拆分时，卫星备份子系统可以计算数据任务的剩余数据任务所需的时长，并判断本次绕轨飞行中准许执行数据备份或者数据还原操作的时长是否小于计算得到的该数据任务的剩余数据任务量所需的时长；若本次绕轨飞行中准许执行数据备份或者数据还原操作的时长小于该数据任务的剩余数据任务所需的时长，则卫星备份子系统可以根据本次绕轨飞行中准许执行数据备份或者数据还原操作的时长，将数据任务的剩余数据拆分为本次绕轨飞行需执行的单轨任务和减去本次绕轨飞行需执行的单轨任务之后剩余的数据任务；若本次绕轨飞行中准许执行数据备份或者数据还原操作的时长不小于(大于或等于)数据任务的剩余数据任务所需的时长，则本次绕轨飞行需执行的单轨任务为数据任务的剩余数据任务。
例如，在第N-1次绕轨飞行时，确定的在第N次绕过飞行时准许执行数据备份或者数据还原操作的时长为20分钟；则在第N次绕过飞行时，若卫星备份子系统计算执行完数据任务的剩余数据任务量所需的时长约为30分钟，由于第N次绕过飞行时准许执行数据备份或者数据还原操作的时长(20分钟)小于备份或还原完剩余数据任务量所需的时长(30分钟)，则在第N次绕过飞行时，卫星备份子系统可以将该数据任务的剩余数据拆分为本次(第N次)绕轨飞行需执行的单轨任务和减去本次(第N次)绕轨飞行需执行的单轨任务之后剩余的数据任务；在第N+1次绕过飞行时，假设在第N+1次绕过飞行时准许执行数据备份或者数据还原操作的时长为15分钟，此时由于执行该数据任务的剩余数据任务量所需的时长为10分钟，小于本次(第N+1次)绕过飞行时准许执行数据备份或者数据还原操作的时长(15分钟)，则本次(第N+1次)绕轨飞行需执行的单轨任务为该数据任务的剩余数据任务，也即拆分完成。
另外，作为又一种可能的实施方式，卫星备份子系统将数据任务拆分成多个单轨任务也可以是一次性完成的，也即在即将开始执行数据备份或数据还原时，便将数据任务拆分成多个单轨任务。
比如，在一些可能的实施方式中，卫星备份子系统可以基于执行数据任务所需的总时长和预估的卫星一次绕轨飞行时准许执行该数据任务的时长将数据任务拆分成多个单轨任务。例如，假设对卫星上的某个设备进行一次完整数据任务所需的总时长为65分钟，预估的卫星一次绕轨飞行时准许执行该数据任务的时长为15分钟，则卫星备份子系统可以基于该总时长(65分钟)和预估的卫星一次绕轨飞行时准许执行数据任务的时长(15分钟)，将该数据任务拆分成5个单轨任务，其中，前4个单轨任务对应的子时长均为15分钟，最后一个单轨任务的对应的子时长为5分钟。
另外，作为一种可能的实施方式，卫星备份子系统可以根据多个历史时刻该卫星在每次绕轨飞行时配置的执行数据备份或数据还原的时长的平均值，来预估该卫星一次绕轨飞行时准许执行数据任务的时长。
例如，卫星备份子系统可以利用为前5轨配置的执行数据备份或数据还原的时长的平均值，来预估卫星一次绕轨飞行时准许执行数据任务的时长。当然，在本申请实施例其他的一些实施方式中，卫星备份子系统也可以是根据当前卫星的电量来预估卫星在一次绕轨飞行时准许执行该数据任务的时长。
另外，需要说明的是，单轨任务(单轨子时长)的划分除了可以由卫星备份子系统完成外，还可以由地面站(卫星平台)完成。例如，当卫星接收到地面站发送的数据任务指令时，卫星备份子系统可以获取该数据任务指令中携带的设备标识，以确定对该设备标识对应的设备执行一次完整数据备份任务或者还原任务所需的总时长，并进行单轨时长划分。
并且，为了避免误操作，当卫星接收到地面站发送的数据任务指令时，卫星备份子系统可以向地面站发送是否需要对该指令中携带的设备标识对应的设备执行数据备份或者数据还原的询问请求，在接收到地面站响应该询问请求发送的确认指令后，再执行对应的备份或还原操作。
其中，任务划分可以由卫星备份子系统执行完成，也可以是由卫星的主系统来执行完成，然后由主系统将划分后的多个单轨任务发送给卫星备份子系统。卫星备份子系统可以基于卫星主系统的通信模块(比如北斗通信模块)实现与地面站的信息交互，例如，卫星主系统在接收到地面站的指令时，可以将该指令转发给卫星备份子系统，卫星备份子系需要向地面站发送询问请求时，可以将该询问请求发送给卫星主系统，然后由卫星主系统将该询问请求发送给地面站。
在一些可能的实施方式中，若任务划分是由地面站执行完成，当卫星接收到地面站发送的数据任务指令时，卫星备份子系统可以获取该数据任务指令中携带的设备标识，确定对该设备标识对应的设备执行一次完整数据备份任务或者还原任务所需的总时长，并响应该数据任务指令向地面站发送是否需要执行数据备份或者数据还原的询问请求；其中，该 询问请求中携带有该总时长。
地面站在获取到该询问请求中的总时长后，可以基于该总时长进行任务划分，然后向卫星发送确认指令，该确认指令中可以携带有多个(两个及以上)单轨子时长，每个单轨子时长表示卫星在一次绕轨飞行中准许执行数据备份或者数据还原的时长。所有单轨子时长之和等于总时长。可见，在该实施方式中，地面站可以为卫星分配任务，并通过向卫星发射指令从而对卫星进行控制。
需要说明的是，当任务划分是由卫星执行完成时，卫星备份子系统在接收到地面站发送的数据任务指令后，向地面站发送的询问请求中可以不携带对该设备标识对应的设备执行一次完整数据备份任务或者还原任务所需的总时长。当任务划分是由地面站来完成时，该询问请求需要携带对该总时长，相应地，此时地面站返回的确定指令中携带有至少两个单轨子时长。
步骤103：在每次绕轨飞行时，执行各自对应的单轨任务。
卫星备份子系统可以结合上述获得的多个单轨任务，在每次绕轨飞行时，执行每一轨各自对应的单轨任务。为了便于理解，结合图2所示的针对每次执行单轨任务的流程图来对在每次绕轨飞行时，执行每一轨各自对应的单轨任务进行说明。
步骤103a：记录本次执行单轨任务中的数据备份或者数据还原的起始标志位。
卫星备份子系统在本次执行单轨任务中的数据备份或者数据还原时，可以记录本次执行单轨任务中的数据备份或者数据还原的起始标志位。
其中，作为一种可能的实施方式，卫星备份子系统在记录本次执行数据备份或者数据还原的起始标志位时：可以先查看文档中是否记录有表征距离与本次绕轨飞行的最近时间点的数据备份或者还原的结束标志位；若文档中记录有表征距离与本次绕轨飞行的最近时间点的数据备份或者数据还原的结束标志位(在为是时)，则卫星备份子系统可以从上一次对应的结束标志位开始记录本次执行数据备份或者数据还原的起始标志位；若文档中并未记录有表征距离与本次绕轨飞行的最近时间点对应的数据备份或者数据还原的结束标志位(在为否时)，则卫星备份子系统可以记录本次执行数据备份或者数据还原的起始标志位，例如，卫星备份子系统可以从第一次对应的起始标记位开始记录本次执行数据备份或者数据还原的起始标志位，或者，卫星备份子系统可以从上上次对应的结束标记位开始记录本次执行数据备份或者数据还原的起始标志位。
在一些可能的实施方式中，卫星备份子系统在记录本次执行单轨任务中的数据备份或者数据还原的起始标志位的过程中，若文档中记录有表征距离与本次绕轨飞行的最近时间点(上一次)对应的数据备份或者还原的结束标志位，也即文档中记录有表征完成上一次绕轨飞行时对应的数据备份或者还原的结束标志位时，表示上次的备份或还原成功，则卫星备份子系统可以从上一次对应的结束标志位开始记录本次执行数据备份或者数据还原的起始标志位；若文档中记录没有表征距离与本次绕轨飞行的最近时间点对应的数据备份或者还原的结束标志位，也即文档中记录没有表征完成上一次绕轨飞行时对应的数据备份或者还原的结束标志位时，表示上次的备份或还原失败，作为一种可能的实施方式，可以卫星备份子系统可以从头重新备份或还原，以提高可靠性，此时，则卫星备份子系统可以从第一次对应的起始标记位开始记录本次执行数据备份或者数据还原的起始标志位。
可以理解的是，作为本申请实施例其他一些可能的实施方式，卫星备份子系统也可以从上上次对应的结束标志位开始执行数据备份或者数据还原，以节约从头重新备份或还原所需的时间，此时从上上次对应的结束标志位开始记录本次执行数据备份或者数据还原的起始标志位。
步骤103b：从单轨任务中数据备份或者数据还原的起始标志位开始，执行单轨任务中的数据备份或者数据还原。
卫星备份子系统在本次执行单轨任务中的数据备份或者数据还原的过程中，可以在记录本次执行单轨任务中的数据备份或者数据还原的起始标志位后，便从该起始标志位开始， 根据本次单轨任务准许执行数据备份或者数据还原的时长去执行数据备份或者数据还原。
步骤103c：在执行完对应的单轨任务中的数据备份或者数据还原时，记录执行完时的结束标志位。
在一些可能的实现方式中，卫星备份子系统在完成对应的单轨任务中的数据备份或者数据还原时，也即执行数据备份或者数据还原的时长达到本次单轨任务中准许执行数据备份或者数据还原的时长时，可以记录完成时的结束标志位，结束本次。如此，待下次执行数据备份或者数据还原时，卫星备份子系统可以先查看文档中是否记录有表示上次备份完成的结束标志位，若有则从表示上次备份完成的结束标志位开始执行本次的数据备份或者数据还原。
为了便于理解，以执行数据备份为例；当卫星备份子系统第一次执行单轨备份任务时，卫星备份子系统可以在文档中记录起始标志位，然后将数据备份至备份存储器；在该单轨备份任务执行完毕时，卫星备份子系统可以在文档中记录备份结束标志位；当第二次及以后执行单轨备份任务时，卫星备份子系统可以先查看文档中是否记录有表示上次完成备份的结束标志位；如果有，则卫星备份子系统可以从上次的结束标志位开始记录起始标志位，然后将数据备份至备份存储器，并在该单轨备份任务执行完毕时，在记录文档中记录结束标志位；如果没有，则代表上一次失败，则卫星备份子系统可以从第一次对应的起始标记位开始记录本次执行数据备份的起始标志位，或者，从上上次对应的结束标记位开始记录本次执行数据备份的起始标志位。
其中，卫星备份子系统在执行数据备份或还原时，为了节约用电，可以在这期间关闭所有不相关外设，例如关闭被配置成航拍的设备，仅保留卫星备份子系统等关键部件的电源，以加快还原速度。
可选地，在一些可能的实施方式中，卫星备份子系统在执行单轨任务(数据备份或者数据还原)的过程中，还可以监测供电电压，且当监测到供电电压持续下降或者下降到设定阈值时，停止当前的数据备份或者数据还原。
通常，当设备异常掉电时，不仅仅数据会存储错误，更重要的是作为数据备份的备用存储器可能也会因此而受损(卫星上的硬件损坏将难以修补)。因此，为了避免备用存储器硬件性地损坏，例如被击穿等，可以选用带掉电检测功能的执行单元(处理器)来执行对应的。
其中，上述的掉电检测，是指在供电电压持续下降或者下降到设定阈值就执行预定的保护策略，例如，停止执行当前的单轨任务(数据备份或者数据还原)，并关闭自身电源。
此外，在本申请实施例其他一些可能的实现方式中，还可以设置为备用存储器用电的储能装置，例如电容，使得备份子系统异常掉电后，能够利用电容短暂地延后备用存储器的断电时间，从而保护备用存储器，提高设备的可靠性。由于供电电压持续下降或者下降到设定阈值时，执行单元一般不再向备用存储器中写入或读取数据，而此时向备用存储器的供电还没有完全停止，再配置电容的储能，可以有效延后备用存储器的断电时间，以保护备用存储器。
另外，当异常掉电重启后，卫星备份子系统在开始执行数据备份或者数据还原时，可以检测记录有是否有表示上次完成数据备份或者数据还原的就结束标志位；若有，则表示上次备份或者还原成功，则卫星备份子系统可以从上次的结束标志位开始继续进行本次的数据备份或者数据还原；若没有，则表示上次备份或者还原失败，则卫星备份子系统可以从头重新开始进行本次的数据备份或者数据还原，或者从上上次的结束标志位开始继续进行本次的数据备份或者数据还原，其过程示意图如图3所示。
另外，基于与本申请实施例提供的上述应用于地面站的卫星数据处理方法相同的发明构思，本申请实施例还提供了一种应用于地面站中的卫星数据处理装置200，如图4所示。该卫星数据处理装置200可以包括：第一发送模块210、接收模块220、第二发送模块230。
第一发送模块210，被配置成向卫星发送数据任务指令，数据任务指令中携带有设备标 识，设备标识被配置成指示待执行数据任务的设备。
接收模块220，被配置成接收卫星响应数据任务指令发送的是否需要对设备标识所对应的设备执行数据任务的询问请求，询问请求中携带有对设备标识所对应的设备执行数据备份任务或者还原任务所需的总时长。
第二发送模块230，被配置成向卫星发送确认指令，以使卫星中的卫星备份子系统根据确认指令中携带的单轨子时长，分轨执行与单轨子时长所对应的单轨任务，其中，确认指令中携带有多个单轨子时长，每个单轨子时长表示卫星在一次绕轨飞行中准许执行数据备份或者数据还原的时长，多个单轨子时长之和等于总时长。
本申请实施例所提供的卫星数据处理装置200，其实现原理及产生的技术效果和前述方法实施例相同，为简要描述，装置实施例部分未提及之处，可参考前述方法实施例中相应内容。
另外，如图5所示，图5示出了本申请实施例提供的一种卫星备份子系统300的结构框图。其中，图中的嵌入式系统可以为待进行数据备份或还原的对象，该系统存储器可以被配置成存储嵌入式系统的数据。该卫星备份子系统300可以包括：电源管理单元310、备用存储器320以及处理器330。
电源管理单元310可以为备用存储器320以及处理器330供电。卫星备份子系统300可以基于卫星主系统的通信模块(北斗通信模块)实现与地面站的信息交互，例如，卫星在接收到地面站的指令时，可以将该指令发送给卫星备份子系统300，卫星备份子系统300需要向地面站发送询问请求时，可以将该询问请求发送给卫星主系统，由卫星主系统将该询问请求发送给地面站。
备用存储器320可以被配置成存储备份数据。处理器中可以固化有系统程序。其中，该系统程序可以包括至少一个可以系统或固件(firmware)的形式固化在卫星备份子系统300的操作系统(operating system，OS)中的系统功能模块。当处理器330执行卫星数据处理装置100包括的系统功能模块或计算机程序时，可以执行上述的卫星数据处理方法。
例如，处理器330，可以被配置成接收数据任务，其中，数据任务为数据备份任务或数据还原任务；以及还可以被配置成将数据任务拆分成多个单轨任务；并在每次绕轨飞行时，被配置成执行各自对应的单轨任务，以将需要执行数据任务的设备对应的存储器中的数据备份至备用存储器，或者将备用存储器中的备份数据还原至存储器。
其中，备用存储器320可以是，但不限于，随机存取存储器(Random Access Memory，RAM)，只读存储器(Read Only Memory，ROM)，可编程只读存储器(Programmable Read-Only Memory，PROM)，可擦除只读存储器(Erasable Programmable Read-Only Memory，EPROM)，电可擦除只读存储器(Electric Erasable Programmable Read-Only Memory，EEPROM)等。
处理器330可以是一种集成电路芯片，具有信号的处理能力。上述的处理器可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器330也可以是任何常规的处理器等。
需要说明的是，本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，也可以通过其它的方式实现。以上所描述的装置实施例仅仅是示意性的，例如，附图中的流程图和框图显示了根据本申请的多个实施例的装置、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或代码的 一部分，上述的模块、程序段或代码的一部分包含一个或多个被配置成实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现方式中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
另外，在本申请各个实施例中的各功能模块可以集成在一起形成一个独立的部分，也可以是各个模块单独存在，也可以两个或两个以上模块集成形成一个独立的部分。
该功能如果以系统功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以系统产品的形式体现出来，该计算机系统产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，笔记本电脑,服务器，或者网络设备等)执行本申请各个实施例提供的方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。
并且，基于与上述方法实施例相同的发明构思，本申请实施例还提供一种计算机程序产品，该计算机程序产品在计算机上运行时，可以执行本申请提供上述方法实施例中所涉及的方法。
其中，需要说明的是，本申请实施例提供的电子设备、计算机存储介质、计算机程序产品均可以被配置成执行上述实施例所提供的对应的方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
最后应说明的是：以上所述仅为本申请的部分实施例而已，并不用于限制本申请，尽管参照前述实施例对本申请进行了详细的说明，对于本领域的技术人员来说，其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
工业实用性
由于采用断点备份或断点还原的技术方案，能够将一次完整的数据任务拆分为多个单轨任务分段执行，以实现卫星在轨系统备份或还原，进而解决一些其他的备份方式无法实现在轨备份或还原操作的问题。
另外，还根据执行该数据任务的总时长和预估的卫星一次绕轨飞行时准许执行数据任务的时长可快速地将该任务拆分成多个单轨任务，能够简化拆分流程。
并且，根据每次绕轨飞行中准许执行该数据任务的时长和该数据任务的剩余数据任务量，将该数据任务拆分成多个单轨任务，使得将数据任务拆分成多个单轨任务时，能够充分考虑不同次绕轨飞行中准许执行该数据任务的时长间的差异，更能合理利用资源，使得拆分效果更高效。
而且，在本次绕轨飞行时记录执行单轨任务中的数据备份或者数据还原的起始标志位，以及记录完成时的结束标志位，使得在下次绕轨飞行时执行单轨任务中的数据备份或者数据还原时，有迹可循，实现卫星在轨系统备份或还原，进而解决一些其他备份方式存在的问题。

Claims (15)

  1. 一种卫星数据处理方法，其特征在于，应用于卫星备份子系统，所述方法包括：
    接收数据任务，其中，所述数据任务包括数据备份或数据还原；
    将所述数据任务拆分成多个单轨任务；
    在每次绕轨飞行时，执行各自对应的单轨任务。
  2. 根据权利要求1所述的卫星数据处理方法，其特征在于，将所述数据任务拆分成多个单轨任务，包括：
    获取执行所述数据任务所需的总时长；
    预估所述卫星一次绕轨飞行时准许执行所述数据任务的时长；
    基于所述总时长和所述卫星一次绕轨飞行时准许执行所述数据任务的时长，将所述数据任务拆分成多个单轨任务。
  3. 根据权利要求2所述的卫星数据处理方法，其特征在于，预估所述卫星一次绕轨飞行时准许执行所述数据任务的时长，包括：
    根据多个历史时刻所述卫星在每次绕轨飞行时配置的执行数据备份或数据还原的时长的平均值，预估所述卫星一次绕轨飞行时准许执行数据任务的时长。
  4. 根据权利要求1所述的卫星数据处理方法，其特征在于，将所述数据任务拆分成多个单轨任务，包括：
    根据每次绕轨飞行中准许执行所述数据任务的时长和所述数据任务的剩余数据任务量，将所述数据任务拆分成多个单轨任务。
  5. 根据权利要求4所述的卫星数据处理方法，其特征在于，根据每次绕轨飞行中准许执行所述数据任务的时长和所述数据任务的剩余数据任务量，将所述数据任务拆分成多个单轨任务，包括：
    根据上次绕轨飞行时，卫星的电量以及待备份或待还原的剩余数据任务量，确定本次绕轨飞行中准许执行数据备份或者数据还原操作的时长；
    计算所述数据任务的剩余数据任务所需的时长；
    判断所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长是否小于所述数据任务的剩余数据任务量所需的时长；
    若所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长小于所述数据任务的剩余数据任务所需的时长，则根据所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长，将所述数据任务的剩余数据拆分为本次绕轨飞行需执行的单轨任务和减去所述本次绕轨飞行需执行的单轨任务之后剩余的数据任务；
    若所述本次绕轨飞行中准许执行数据备份或者数据还原操作的时长不小于所述数据任务的剩余数据任务所需的时长，则本次绕轨飞行需执行的单轨任务为所述数据任务的剩余数据任务。
  6. 根据权利要求2或5所述的卫星数据处理方法，其特征在于，执行各自对应的单轨任务，包括：
    记录本次执行所述单轨任务中的数据备份或者数据还原的起始标志位；
    从所述单轨任务中数据备份或者数据还原的所述起始标志位开始，执行所述单轨任务中的数据备份或者数据还原；
    在执行完对应的所述单轨任务中的数据备份或者数据还原时，记录执行完时的结束标志位。
  7. 根据权利要求6所述的卫星数据处理方法，其特征在于，记录本次执行所述单轨任务中的数据备份或者数据还原的起始标志位，包括：
    查看文档中是否记录有表征距离与本次绕轨飞行的最近时间点的数据备份或者数据还原的结束标志位；
    若所述文档中记录有表征距离与本次绕轨飞行的最近时间点的数据备份或者数据还原的结束标志位，则从上一次对应的结束标志位开始记录本次执行数据备份或者数据还原的起始标志位；
    若所述文档中并未记录有表征距离与本次绕轨飞行的最近时间点对应的数据备份或者数据还原的结束标志位，记录本次执行数据备份或者数据还原的起始标志位。
  8. 根据权利要求1所述的卫星数据处理方法，其特征在于，接收数据任务，包括：
    接收来自地面站的数据任务指令，所述数据任务指令中携带有设备标识，所述设备标识被配置成指示待执行数据任务的设备；
    向所述地面站发送是否需要对所述设备标识所对应的设备执行所述数据任务的询问请求；
    在接收所述地面站响应所述询问请求发送的确认指令时，表征接收到所述数据任务。
  9. 根据权利要求1-5或7-8中任一项所述的卫星数据处理方法，其特征在于，在执行单轨任务的过程中，所述方法还包括：
    当监测到供电电压持续下降或者下降到设定阈值时，停止执行当前的单轨任务。
  10. 一种卫星数据处理方法，其特征在于，应用于地面站，所述方法包括：
    向卫星发送数据任务指令，所述数据任务指令中携带有设备标识，所述设备标识被配置成指示待执行数据任务的设备；
    接收所述卫星响应所述数据任务指令发送的是否需要对所述设备标识所对应的设备执行所述数据任务的询问请求，所述询问请求中携带有对所述设备标识所对应的设备执行所述数据任务所需的总时长；
    向所述卫星发送确认指令，以使所述卫星中的卫星备份子系统根据所述确认指令中携带的单轨子时长，分轨执行与所述单轨子时长所对应的单轨任务；
    其中，所述确认指令中携带有多个单轨子时长，每个单轨子时长表示卫星在一次绕轨飞行中准许执行所述数据任务的时长，所述多个单轨子时长之和等于所述总时长。
  11. 一种卫星备份子系统，其特征在于，包括：备用存储器和处理器，所述备用存储器和所述处理器连接；
    所述备用存储器，被配置成存储备份数据；
    所述处理器，被配置成接收数据任务，其中，所述数据任务包括数据备份或数据还原；以及还被配置成将所述数据任务拆分成多个单轨任务；并在每次绕轨飞行时，被配置成执行各自对应的单轨任务，以将需要执行所述数据任务的设备对应的存储器中的数据备份至所述备用存储器，或者将所述备用存储器中的备份数据还原至所述存储器。
  12. 一种卫星数据处理装置，其特征在于，应用于地面站，所述装置包括：
    第一发送模块，被配置成接收来自地面站的数据任务指令，所述数据任务指令中携带有设备标识，所述设备标识被配置成指示待执行数据任务的设备；
    接收模块，被配置成接收所述卫星响应所述数据任务指令发送的是否需要对所述设备标识所对应的设备执行所述数据任务的询问请求，所述询问请求中携带有对所述设备标识所对应的设备执行所述数据任务所需的总时长；
    第二发送模块，被配置成向所述卫星发送确认指令，以使所述卫星中的卫星备份子系统根据所述确认指令中携带的单轨子时长，分轨执行与所述单轨子时长所对应的单轨任务；
    其中，所述确认指令中携带有多个单轨子时长，每个单轨子时长表示卫星在一次绕轨飞行中准许执行所述数据任务的时长，所述多个单轨子时长之和等于所述总时长。
  13. 一种卫星备份子系统，其特征在于，包括：备用存储器和处理器，所述备用存储器和所述处理器连接；
    所述备用存储器，被配置成存储备份数据；
    所述处理器中固化有计算机程序，所述处理器被配置成通过运行所述计算机程序，执行如权利要求1-9中任一项所述的方法。
  14. 一种计算机可读存储介质，其特征在于，该可读存储介质上存储有计算机程序，该计算机程序被处理器运行时执行如权利要求1-9任一项所述的方法。
  15. 一种计算机程序产品，其特征在于，所述计算机程序产品在计算机上运行时，使得计算机执行如权利要求1-9任一项所述的方法。
PCT/CN2020/092405 2019-11-29 2020-05-26 一种卫星数据处理方法、装置及卫星备份子系统 WO2021103451A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/419,703 US11416292B2 (en) 2019-11-29 2020-05-26 Satellite data processing method, apparatus, and satellite backup subsystem

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911210337.4A CN110968459B (zh) 2019-11-29 2019-11-29 一种卫星数据处理方法、装置及卫星备份子系统
CN201911210337.4 2019-11-29

Publications (1)

Publication Number Publication Date
WO2021103451A1 true WO2021103451A1 (zh) 2021-06-03

Family

ID=70032525

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/092405 WO2021103451A1 (zh) 2019-11-29 2020-05-26 一种卫星数据处理方法、装置及卫星备份子系统

Country Status (3)

Country Link
US (1) US11416292B2 (zh)
CN (1) CN110968459B (zh)
WO (1) WO2021103451A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110968459B (zh) * 2019-11-29 2020-12-11 成都星时代宇航科技有限公司 一种卫星数据处理方法、装置及卫星备份子系统
CN115037354B (zh) * 2022-06-06 2023-03-28 中国人民解放军32039部队 一种空间数据分发服务平台及方法
CN117833990B (zh) * 2024-01-04 2024-09-27 中国科学院空天信息创新研究院 卫星数据接收任务与质量闭环方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9684563B1 (en) * 2010-01-04 2017-06-20 Veritas Technologies Llc Techniques for backup management
CN107862145A (zh) * 2017-11-13 2018-03-30 中国运载火箭技术研究院 一种空天飞行器飞行时序与能源平衡耦合设计系统与方法
CN108053051A (zh) * 2017-11-16 2018-05-18 西安电子科技大学 基于任务拆分聚合的数据中继卫星系统任务规划方法
CN108897021A (zh) * 2018-04-20 2018-11-27 中国航天标准化研究所 一种导航卫星单轨位可用性确定方法
CN110968459A (zh) * 2019-11-29 2020-04-07 成都星时代宇航科技有限公司 一种卫星数据处理方法、装置及卫星备份子系统

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI409693B (zh) * 2010-01-15 2013-09-21 Micro Star Int Co Ltd A method of advising the battery power state
US9069103B2 (en) * 2010-12-17 2015-06-30 Microsoft Technology Licensing, Llc Localized weather prediction through utilization of cameras
CN103744733B (zh) * 2013-07-03 2017-03-22 中国人民解放军国防科学技术大学 成像卫星资源调用配置方法
CN104348886A (zh) * 2013-08-08 2015-02-11 联想(北京)有限公司 一种信息处理的方法及一种电子设备
CN103679352B (zh) * 2013-11-29 2017-06-16 中国资源卫星应用中心 一种基于协商对策冲突消解的卫星需求处理系统
JP6386674B2 (ja) * 2015-02-03 2018-09-05 クラウド コンステレーション コーポレイション 宇宙ベースの電子データストレージおよび転送ネットワークシステム
CA3018142C (en) * 2016-03-22 2023-02-07 Lyteloop Technologies, Llc Data in motion storage system and method
CN106324631B (zh) * 2016-07-28 2018-08-07 北京空间飞行器总体设计部 一种遥感卫星能源平衡约束分析系统及方法
CN106502837B (zh) * 2016-10-25 2019-06-14 Oppo广东移动通信有限公司 一种数据备份的方法、装置及系统
CN106888047B (zh) * 2017-02-20 2019-07-23 上海微小卫星工程中心 低轨卫星数据传输方法
US10749959B2 (en) * 2018-02-09 2020-08-18 Lockheed Martin Corporation Distributed storage management in a spaceborne or airborne environment
CN109992387B (zh) * 2019-04-01 2021-09-24 北京邮电大学 一种终端协同的任务处理方法、装置及电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9684563B1 (en) * 2010-01-04 2017-06-20 Veritas Technologies Llc Techniques for backup management
CN107862145A (zh) * 2017-11-13 2018-03-30 中国运载火箭技术研究院 一种空天飞行器飞行时序与能源平衡耦合设计系统与方法
CN108053051A (zh) * 2017-11-16 2018-05-18 西安电子科技大学 基于任务拆分聚合的数据中继卫星系统任务规划方法
CN108897021A (zh) * 2018-04-20 2018-11-27 中国航天标准化研究所 一种导航卫星单轨位可用性确定方法
CN110968459A (zh) * 2019-11-29 2020-04-07 成都星时代宇航科技有限公司 一种卫星数据处理方法、装置及卫星备份子系统

Also Published As

Publication number Publication date
US11416292B2 (en) 2022-08-16
CN110968459B (zh) 2020-12-11
CN110968459A (zh) 2020-04-07
US20220043674A1 (en) 2022-02-10

Similar Documents

Publication Publication Date Title
WO2021103451A1 (zh) 一种卫星数据处理方法、装置及卫星备份子系统
US9377964B2 (en) Systems and methods for improving snapshot performance
US8386841B1 (en) Systems and methods for improving redundant storage fault tolerance
US9250676B2 (en) Power failure architecture and verification
WO2016078202A1 (zh) 一种掉电保护方法及固态硬盘
EP1470483A1 (en) Method and apparatus for securing volatile data in power failure in systems having redundancy
CN106557143B (zh) 用于数据存储设备的装置和方法
US9032414B1 (en) Systems and methods for managing system resources allocated for backup validation
US10872018B2 (en) Memory data preservation solution
US10049023B1 (en) Optimizing application recovery in unmanaged clusters
CN106356097A (zh) 一种防止数据丢失的保护方法和装置
US20120131318A1 (en) Server and method for performing data recovery of the server
CN104035892A (zh) 服务器系统及集群系统
CN111737038A (zh) 一种基于小卫星双机系统切机的控制方法
US20130024719A1 (en) System and method for processing network data of a server
US9003139B1 (en) Systems and methods for recovering virtual machines after disaster scenarios
US9697081B2 (en) Storage control device and data recovery method
US10082969B2 (en) System and method for managing a storage system
US20070157047A1 (en) Computer platform system power state management method and system
CN103455448A (zh) 服务器防震方法及系统
CN103294169B (zh) 一种功耗优化的众核系统的冗余保护系统及方法
CN104020963A (zh) 一种防止误判硬盘读写错误的方法和装置
CN106294024A (zh) 一种快速磁盘增量备份方法
CN103440184B (zh) 一种皮卫星星载计算机状态回卷温备份的方法
US8060605B1 (en) Systems and methods for evaluating the performance of remote computing systems

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20891760

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20891760

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20891760

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 30.06.2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20891760

Country of ref document: EP

Kind code of ref document: A1