Processing of satellite motion and status data

The method of processing satellite status data and scheduling maneuvers addresses accuracy issues in satellite positioning and orbit determination for SAR imaging, enhancing precision and collision avoidance in small satellite operations.

JP2024541955AActive Publication Date: 2024-11-13アイサイ オサケユキチュア
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024525163
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-10-29
Filing Date
2022-10-14
Publication Date
2024-11-13
Estimated Expiration
2042-10-14

AI Technical Summary

Technical Problem

In the field of Synthetic Aperture Radar (SAR) imaging using small satellites, the accuracy of satellite positioning and orbit determination (OD) is compromised by anomalies in GPS measurements due to issues like loss of telemetry data or temporary damage to the GNSS receiver, leading to uncertainties in satellite placement and potential collisions or debris avoidance.

Method used

A method for processing satellite status data involves receiving and compiling raw data from multiple sources into a searchable dataset, filtering it using an orbit determination process, and incorporating maneuver data to improve accuracy, while also scheduling maneuvers to avoid collisions and maintain optimal orbits.

Benefits of technology

Enhances the accuracy of satellite positioning and orbit maintenance, reducing the risk of collisions and ensuring precise image formation by integrating filtered and predicted ephemerides with dynamic models, thus improving the reliability of satellite operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024541955000001_ABST
    Figure 2024541955000001_ABST
Patent Text Reader

Abstract

A method for scheduling maneuvers of a satellite is provided, the method including receiving parameters for one or more planned maneuvers for moving a satellite (100) from a current orbit to a new orbit, the parameters including a time and duration for each of the one or more planned maneuvers, receiving a time of a solar eclipse by the Earth during a future orbit of the satellite, and scheduling the maneuvers to be performed according to the determined parameters and the time of the solar eclipse.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention is in the field of satellite operations. [Background technology]

[0002] In the field of Synthetic Aperture Radar (SAR) imaging, especially using small satellites, a process essential for the accurate planning, acquisition and processing of images is the orbit determination (OD) of the satellite in question.

[0003] The OD process can result in accurate historical values ​​of satellite position and velocity, as well as predicted future values. OD is well known in the field of satellite motion and is generally described as a filtering method that integrates observations and orbital dynamic equations to estimate satellite position and velocity. That is, it estimates satellite state variables (position and velocity) based on observed measurement data or "raw" data and the orbital dynamic equations that form a dynamic model of the satellite's movement. The OD process tool is commonly called a filter and the output is called filtered data.

[0004] To achieve OD, satellites can use on-board Global Navigation Satellite System (GNSS) receivers to periodically measure position, velocity and time (almanac state vector), which can be downlinked while "passing" the antenna of a ground station. Due to the nature of this system, these measurements may contain anomalies, which are typically processed to achieve the desired accuracy with an OD tool in a so-called filtering process. Such anomalies may be due, for example, to lost telemetry data, invalid GPS indications (or other position indicators), or temporary damage to the GNSS receiver. This damage may be caused, for example, by solar radiation. OD tools exist that run various algorithms to generate both filtered history and predicted future orbital ephemerides.

[0005] Additionally, some of the measured raw state vector data may be filtered on-board the satellite. For example, the satellite's on-board processing system may filter raw position data. This position data may be collected by GPS measurements or the like. This pre-filtered data becomes part of the telemetry data downlinked to the ground station antenna. This may introduce uncertainty into the ground station antenna's estimation of the state vector.

[0006] For some SAR applications, it is desirable to improve the accuracy of satellite constellation or positioning at a particular time. This is particularly important for the formation of images, since the resolution depends on the accuracy of the satellite positions. Some satellite surveillance applications require the ability to detect movements of less than one meter.

[0007] Maintaining a satellite in a particular orbit is also important for many applications, and therefore the satellite position and / or state needs to be known in case it drifts. Maneuvers may be required at regular intervals to maintain the orbit. It may also be necessary to steer the satellite to avoid collisions with other satellites, debris, etc. This may involve temporarily steering the satellite out of orbit or scheduling maneuvers to avoid collisions.

[0008] Steering a satellite, for example to maintain a particular position and / or to avoid collisions, is sometimes called celestial mechanics.

[0009] The embodiments of the invention described below address some of these problems, however the invention is not limited to solving these problems and some embodiments of the invention may address other problems. Summary of the Invention

[0010] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

[0011] In a first aspect, there is provided a method for processing satellite state data, the method comprising the steps of receiving satellite state data in the form of a plurality of separate files via one or more ground stations, and compiling the received satellite state data into a single data set accessible via an application programming interface and searchable over a range of time.

[0012] In some embodiments, the satellite state data may include raw data.

[0013] In some embodiments, the method may further include filtering the raw satellite state data in an orbit determination process to provide filtered satellite state data, the filtering being performed in parallel with the compilation of received satellite state data, and each item of the filtered satellite state data may correspond to an item of the raw satellite state data.

[0014] In some embodiments, the method may include receiving steering data relating to one or more scheduled maneuvers of the satellite and compiling the received steering data into a data set accessible via an application programming interface and searchable by time range.

[0015] In some embodiments, the steering data may be used to filter the received raw satellite state data.

[0016] In another aspect, a method for processing satellite state data includes receiving steering data related to one or more scheduled maneuvers for the satellite, and filtering the received satellite state data in an orbit determination process to provide filtered satellite state data, wherein the steering data may be used to filter the received satellite state data.

[0017] In some embodiments, receiving the raw satellite state data may include receiving the raw satellite state data in the form of a plurality of separate files via one or more ground stations, and the method may further include compiling the received raw satellite state data into a single data set accessible via an application programming interface and searchable by time range.

[0018] In another aspect, a method for scheduling maneuvers for a satellite may include receiving parameters for one or more planned maneuvers for moving the satellite from a current orbit to a new orbit, the parameters including a time and duration for each of the one or more planned maneuvers; receiving a time of a solar eclipse by the Earth during a future orbit of the satellite; and scheduling the maneuvers to occur according to the determined parameters and the time of the eclipse.

[0019] The aspects described herein may be combined and features associated with any aspect may be implemented in one or more of the other aspects.

[0020] In some embodiments, the method may further include inserting the filtered satellite state data into the single data set.

[0021] In some embodiments, inserting the filtered satellite condition data into the single data set may include overwriting raw satellite condition data in the data set with the corresponding filtered satellite condition data.

[0022] In some embodiments, the filtered satellite condition data may include historical satellite condition data.

[0023] In some embodiments, the satellite historical state data may be actual data associated with one or more historical state vectors for the satellite.

[0024] In some embodiments, the filtered satellite condition data may include future satellite condition data.

[0025] In some embodiments, the future satellite state data may be projection data based on a dynamic model that predicts the future state vector of the satellite.

[0026] In some embodiments, the method may further include mapping metadata about the satellite to satellite status data.

[0027] In some embodiments, the metadata may include one or more of data related to the satellite's physical dimensions, satellite attitude data, satellite thrust data including information related to the satellite's history and future planned maneuvers.

[0028] In some embodiments, the method may further include providing the metadata for use in filtering the raw satellite state data.

[0029] In some embodiments, the received maneuver data may include one or more of maneuver duration, thrust duration, thrust magnitude, thrust direction, and / or thrust ratio impact for each of the one or more scheduled maneuvers.

[0030] In some embodiments, the one or more schedule maneuvers may include one or more future schedule maneuvers of the satellite.

[0031] In some embodiments, the method may further include maintaining a dynamic model of the satellite's movement and updating the dynamic model with data regarding the one or more future scheduled maneuvers.

[0032] In some embodiments, the satellite state estimates obtained from the dynamic model may be used to filter the received raw satellite state data.

[0033] In some embodiments, the estimate of the satellite state may include an estimate of the satellite position.

[0034] In some embodiments, the estimates of the satellites may include estimates of the satellites' velocities.

[0035] In some embodiments, the method may further include verifying that the satellite is commanded to execute one of the one or more future scheduled maneuvers.

[0036] In some embodiments, the one or more schedule maneuvers may include one or more historical maneuvers.

[0037] In some embodiments, the maneuver data relating to one or more historical maneuvers of the satellite may include one or more measurement data of maneuver time, thrust duration, thrust magnitude, thrust direction, and / or thrust specific impact, respectively, of the one or more historical maneuvers of the satellite.

[0038] After a scheduled maneuver has been scheduled to be performed, the measurement data may be used to determine whether the scheduled maneuver has been performed.

[0039] In some embodiments, the method may further include removing data relating to maneuvers that have been determined not to have been performed from the filtered satellite state data.

[0040] In some embodiments, the steering data may relate to steering over a period of time.

[0041] In some embodiments, receiving the steering data may include receiving the steering data periodically.

[0042] In some embodiments, the received steering data may relate to a contiguous time span.

[0043] In some embodiments, the satellite status data may include satellite position data.

[0044] In some embodiments, the satellite status data may include satellite velocity data.

[0045] In some embodiments, the satellite state data may include ephemeride state vector data.

[0046] In some embodiments, the satellite status data may be received in a queue.

[0047] In some embodiments, the method may include copying the satellite status data received since a previous interval to a working directory.

[0048] In some embodiments, the dataset may be stored in a relational database.

[0049] In some embodiments, the satellite state data is received as a file for each pass of the satellite, and data in the data set may be searchable over a period of time that includes multiple passes.

[0050] In some embodiments, the step of scheduling maneuvers for the satellite may further include scheduling the maneuver items to avoid a percentage of the orbit that maximizes the satellite's exposure to the sun.

[0051] In some embodiments, the proportion of the trajectory to avoid may be one-quarter of the trajectories.

[0052] In some embodiments, the duration of at least one of the planned maneuvers may be a duration that includes at least two orbits of the satellite around the Earth.

[0053] In some embodiments, a schedule maneuver may include at least two sub-maneuvers.

[0054] In some embodiments, each of the sub-pilots may be scheduled to be performed during a different orbit of the satellite.

[0055] In some embodiments, at least one of the planned maneuvers may be a maneuver to return the satellite to a predetermined orbit.

[0056] In some embodiments, at least one of the planned maneuvers may be a maneuver to avoid a collision.

[0057] In some embodiments, the step of scheduling maneuvers of the satellite may further include determining candidate parameters for one or more of the planned maneuvers for moving the satellite from a current orbit to a new orbit, the parameters including a candidate time and a candidate duration for each of the planned maneuvers; providing the candidate parameters to a collision avoidance system; receiving a respective collision probability from the collision avoidance system based on each set of candidate parameters; determining new candidate parameters for the one or more planned maneuvers if the respective collision probabilities exceed a predetermined threshold; and repeating the operations of determining candidate parameters for each of the one or more planned maneuvers until at least one of the respective collision probabilities falls below the predetermined threshold.

[0058] In some embodiments, the step of scheduling maneuvers for the satellite may further include receiving propulsion scheduling requirements and scheduling the maneuvers to occur in accordance with the propulsion scheduling requirements.

[0059] In another aspect, a method of steering a satellite is provided in which steering of the satellite is scheduled in accordance with the methods described herein.

[0060] In another aspect, a method for operating a satellite propulsion system is provided, comprising the steps of commanding a maneuver of a satellite based on maneuver data for one of one or more future scheduled maneuvers and based on an assumed relationship between the maneuver data for the commanded maneuver and an orbital change of the satellite, receiving satellite status data related to an orbit of the satellite after executing the commanded maneuver in accordance with the command, and verifying or updating the assumed relationship based on the received satellite status data, wherein the orbit of the satellite is determined in an orbit determination process subordinate to the method of the present invention.

[0061] In another aspect, a method for processing SAR image data is provided, comprising the steps of receiving image data acquired during a time span; receiving satellite state data processed according to the method of any one of the previous aspects, the received satellite state data corresponding to a time span associated with the received image data; estimating or determining a geographical position error associated with the satellite position estimate using the received satellite state data; if the geographical position error is greater than a predetermined threshold, requesting satellite state data for a longer time span and repeating the estimation of the geographical position error; and passing the image data to a stack for further processing only if the geographical position error is below a predetermined threshold.

[0062] In another aspect, there is provided a data processing apparatus for carrying out the methods described herein.

[0063] In another aspect, a distributed computing system configured to perform the methods described herein is provided.

[0064] In another aspect, a computer readable medium is provided that includes logic that, when executed by a computer, causes the computer to perform the methods described herein.

[0065] In another aspect, there is provided a computer program comprising instructions which, when executed by a computer, cause the computer to carry out the methods described herein.

[0066] In some embodiments of the present invention, a system is provided that includes one or more computing systems, each with at least one processor and memory, configured to implement any of the methods or processes described herein.

[0067] In some embodiments of the present invention, a computer readable medium is provided that includes instructions in the form of an algorithm that, when implemented in a computing system that forms part of a satellite operating system, causes the system to perform any of the methods or processes described herein.

[0068] The features of the various aspects and embodiments of the invention may be combined as appropriate and in any combination with any aspect of the invention, as will be apparent to the skilled artisan.

[0069] Embodiments of the present invention will now be described, by way of example only, with reference to the following drawings, in which: [Brief description of the drawings]

[0070] [Figure 1] 1 is a schematic diagram of a system for controlling the operation of a satellite according to some embodiments of the present invention. [Diagram 2] FIG. 2 is a schematic diagram illustrating in more detail the data exchanged between the OD server and the OD process tool of FIG. [Diagram 3] FIG. 2 is a block diagram of a quality control process that can be incorporated into the system of FIG. 1. [Figure 4] FIG. 2 is a block diagram showing a collision avoidance process that may be implemented in the system of FIG. 1. [Diagram 5] FIG. 2 is a block diagram showing operations that may be performed by a trajectory simulator in the system of FIG. 1. [Figure 6] FIG. 1 is a block diagram of the maneuver planning process. [Figure 7] 1 is a perspective view of a satellite in orbit around the Earth. [Figure 8] 2 is a block diagram illustrating operations that may be performed by an image scheduler in the system of FIG. 1. [Figure 9] 2 is a block diagram showing operations that may be performed by a propulsion system calibrator in the system of FIG. 1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0071] Common numbers are used throughout the drawings to denote like features. Embodiments of the present invention will now be described by way of example. These examples represent the best ways of practicing the invention currently known to applicant, but are not the only ways that may be accomplished.

[0072] System Architecture Figure 1 shows a system 10 for controlling the operation of a satellite 100. The same system may be used to control the operation of multiple satellites, for example in a constellation of satellites, also called a fleet. Figure 1 will be described generally with reference to a single satellite.

[0073] 1 may be configured to implement one or more of the methods for processing satellite position data and for operating a satellite propulsion and control system described below. Components of system 10 may be distributed across multiple locations, for example, but not necessarily at different terrestrial locations.

[0074] The system 10 is configured to receive raw data. The raw data may consist of ephemeride state vectors, typically in binary form, transmitted, for example, from satellite ADCS (Attitude Determination and Control System) units. The state vectors may include satellite position data, in this example GPS data held in GPS queue 102. This is performed automatically and for all satellites 100 in the fleet. GPS data originating from satellites 100 may be routed in various ways to and from the system 10, for example, from one or more ground stations in a ground station network 101 in communication with the satellites. The state vectors may further include satellite velocity data, indicating the traveling speed and direction of the satellite 100. The raw data is received in multiple separate files. In a specific example of the operation of the system, the binary data is parsed into a text-based form for use in the OD process tool 103, and the files containing the text-based data are placed in the ephemeris archive 110 or the GPS queue 102.

[0075] It should be noted here as background that an orbit is defined by six orbital parameters: 1. The semi-major axis of the eclipse (this represents the altitude), 2. The inclination, 3. The eclipse eccentricity, 4. The argument of perigee (where on the orbital arc the closest point to the Earth is located), 5. The longitude of the ascending node, 6. The true anomaly. Given that by estimating the satellite's acceleration, information can be derived about the orbital state and energy, the orbit can also be described by a state vector (position, velocity, time).

[0076] In the following description, the satellite position data is referred to as GPS data. However, other forms of data can be used in addition to or instead of GPS data, and the systems, methods and processes described herein are not limited to GPS data. Thus, the raw ephemeride state vector is taken as an example of position data.

[0077] The GPS data is transmitted from the GPS queue 102 to an orbit determination server 105 with an application programming interface "OD API". Here, the GPS data received from the satellites, usually in individual files, but sometimes from different ground stations, is compiled into a dataset accessible via the API and searchable by time range. For this purpose, the data may be organized in chronological order. The data may then be searchable, for example, via an http interface, so that it can be more easily accessed and provided for other purposes, for example, outside the system 10 or within the system 10. Upon request via the API, the data may be provided in such a way that the recipient or requester of the data does not need knowledge of the GPS data or the satellite constellation data to be able to use it. This compilation of the data may be done in various ways and further operations may be performed on the data. For example, the OD saver 105 may receive text-based files and further parse and store the data in a dataset, such as a relational database, searchable, for example, by time range, satellite, etc. Other methods of compiling received data files into datasets are well known to those skilled in the art and the system described herein is not limited to the use of a relational database.

[0078] In the system of FIG. 1, the OD server 105 is configured to control the OD process. To this end, an OD process tool 103 is provided, which may be integrated into the OD server 105 or may be standalone. The OD process tool 103 is also fed with raw GPS position data. The OD process tool 103 comprises a filter module (commonly referred to as an OD filter) that filters the data in one or more filtering stages, which will be described later. Thus, the filtering of the raw satellite state data may be performed in parallel with the compilation of the data into a data set. For this process, the OD process tool 103 may maintain a dynamic model of the movement of the satellites. This model is dynamic in the sense that it is periodically updated, which may be used to predict the satellite position and / or state at any time in the future. In some examples, the model may be updated each time one or more new state vectors are filtered by the filter module of the OD process tool 103. Additionally or alternatively, the model may be updated manually by a user of the system 100, who may update the model.

[0079] In an example mode of operation, the OD server 105 periodically copies measurements from queue 102 that have arrived from the previous interval to a working directory. It also maps any necessary additional metadata about the satellites to these measurements, which may be in the form of multiple separate ephemeris files. The OD server 105 may run the OD process tool 103, feeding it these measurements and metadata so that the OD process tool 103 generates the desired filtered and predicted ephemeris measurements.

[0080] The metadata mapped to the satellite measurements may include any one or more of the satellite's mass, the satellite's center of gravity, the location of the GPS antenna on the satellite's bus, NORAD (North American Aerospace Defense Command) tracking ID, an initial estimate of the ballistic coefficient, drag coefficient and SRP (solar radiation pressure), effective drag area and SRP, and other data well known to those skilled in the art.

[0081] Filtering of the satellite data may in principle be done prior to receiving the GPS data in the GPS queue 102, may be done in the OD server 105, or may be done elsewhere, e.g. to provide filtered historical and future predicted orbital ephemeride state vectors. As mentioned elsewhere herein, proprietary tools are available for doing this filtering and may be executed in the OD server 105 or separately.

[0082] In either case, it is particularly useful that the filtering is performed as a separate process from or in parallel with the organization and organization of the GPS data in the OD server 105, as appropriate. That is, the compilation of the data into a dataset may be performed on filtered or unfiltered data, e.g., raw data, to allow easy access via the OD API. For example, the filtered and unfiltered data may be stored in a database such that the OD API has both filtered and unfiltered data available. In some instances, the filtered and unfiltered data may be stored in a relational database as described above. In some cases, they are stored in separate tables in the relational database. Additionally or alternatively, the filtered data may be inserted into the dataset. One way to implement this is to replace or overwrite the unfiltered data with the filtered data in the OD API 105. Other methods are well known to those skilled in the art.

[0083] Separating filtering from compilation of the data set has many advantages. For example, it helps avoid delays in being able to access the data that may be caused by the filtering process. The filtering process typically requires a minimum amount of raw data before filtering can begin or before the required amount of confidence can be attributed to the filtered data. This may result in a time delay, for example, during the initial launch of a satellite before the minimum amount of raw data is acquired. The time it takes to acquire this minimum amount of data may cause a significant delay in the accessibility of the filtered data via the API, during which time it may be useful for the unfiltered data to be accessible via the API. For example, the time delay after the initial launch of a satellite before the minimum data acquisition may be 6 hours or more, 12 hours or more, 18 hours or more, 24 hours or more, 36 hours or more, 48 hours or more, 72 hours or more, 100 hours or more.

[0084] Separating the filtering process from compilation, and optionally other operations that occur in the OD server, allows for earlier availability of data via the API. Availability of raw data via the API may facilitate maneuvers to be performed on the satellite, especially at first launch. One such maneuver may be a manual calculation of the satellite position and / or state at first launch, which may be desirable, for example, if an anomaly is noted. Also, early availability of unfiltered data is useful, since several decisions about the health of the satellite may be made immediately after launch. For example, by ensuring early availability of unfiltered data, it is possible to verify that GPS data is being safely received in the GPS queue 102 and / or that associated subsystems are receiving the data and associated measurements. In some examples, this can be done by ensuring that the time gap between successively received state vectors is not large enough to indicate that one or more state vectors have not been successfully and safely received in the GPS queue 102, i.e., no state vectors are "missing" from the GPS queue 102.

[0085] Additionally, early availability of unfiltered data can facilitate early determination of the orbital state of satellite 100. Access to unfiltered GPS data allows the OD server to determine the orbital state of satellite 100, for example, by Two Line Element (TLE) generation. The TLEs may be used to define the orbital state of satellite 100 and may be distributed to external devices and / or servers, for example, ground stations or internal computers on the satellite, such as internal path planners. The TLEs may be distributed to such devices and / or servers such that data related to each orbital path of the satellite is synchronized between the devices and / or servers and / or the satellite is tracked by one or more antennas at the ground station.

[0086] As shown in FIG. 1, the OD server 105 provides a readily searchable, and ideally unfiltered, source of measurements of actual position, velocity, and time (ephemerid state vectors), and may also provide a readily searchable source of predicted future positions, velocities, and times, which will be described in more detail with reference to FIG. 2.

[0087] The OD server 105 and OD process tool 103 may be hosted and executed independently of any ground station and communication system, for example using a cloud computing provider.

[0088] As already mentioned, and as shown in Figure 1, the OD process tool 103 can output filtered ephemerides based on the raw data received, as well as future ephemerides that may be used in other parts of the system, such as image acquisition planning. If future maneuvers are performed, the predicted future ephemerides may change.

[0089] 1 can provide data regarding one or more future scheduled maneuvers of the satellite to the OD process tool for use in filtering the received satellite position data. Additionally, the OD process tool can receive data regarding historical scheduled maneuvers of the satellite for use in the filtering process.

[0090] Note that there are generally two types of maneuvers: those that change the satellite's orbit and those that do not. Maneuvers to change or correct the orbit, for example to maintain a certain orbit or to avoid collisions, are performed with the satellite's propulsion system, e.g. thrusters of the propulsion unit. Attitude maneuvers may also be commanded and executed from the ADCS unit. These maneuvers may not change the orbit. They may be used for downlink / imaging / etc. Attitude maneuvers may be executed by rotating components of the satellite. According to the principle of conservation of angular momentum, the satellite may rotate in a sense opposite to the rotation of the rotating components. The rotating components of the satellite may be actuators of the ADCS unit, for example. The actuators may comprise one or more of reaction wheels, torque rods, kinetic wheels or other rotating components.

[0091] In the system of FIG. 1, raw GPS ephemeris data is stored in an ephemeris archive 110.

[0092] The filtered prediction output from the OD server 105 may be in the form of a file that may be stored on a computer disk. When this is generated, the OD server 105 may transfer this file over a computer network using a predefined application programming interface (API) to the archive 112 to catalog and store the generated data. The archive 112 may provide the functionality to search the entire historical record of orbits over a continuous time span and provide this data in a standard response form. This archive 112 may be combined with the ephemeris archive 110. In some examples, the OD server 105 may be configured to provide users of the system 110 the functionality to search the archive 112 and / or the ephemeris archive 110. In this sense, the OD server 105 may be operable as a database interface to query the archive 112 and / or the ephemeris archive 110, which may operate separately or together, as a database in which the output of the GPS cues 102 and / or the OD server 105 are cataloged and / or stored. The data stored in the database may be searchable and accessible as a continuous data stream.

[0093] Like the OD server 105 and other components of the system 10, the archive may be hosted separately from the rest of the system and replicated geographically or across multiple networks for high availability or performance reasons.

[0094] Since new values ​​for predictions usually overlap in time span, the OD server 105 can remove older values ​​from the archive 112 and provide only the most recent generated values. Upon receiving confirmation of storage, the archive can permanently delete the downlinked file from the GPS queue 102 so that it will not be reprocessed. If an error occurs, it may be automatically reprocessed on the next run.

[0095] Additionally, business processes may use the OD server 105 to obtain time-dependent trajectory data rather than obtaining input from a discrete file. These processes may include programmatic submission of predicted trajectories for collision avoidance purposes, and automatically determine whether a planned maneuver is likely safe to execute.

[0096] 1, the filtered ephemeris data is shown provided to orbit simulator 115 and processor 120. The predicted data is shown provided to image scheduler 125.

[0097] In the OD server 105, various processes can take place as is known in the art. Processing can be performed in any suitable location and in any suitable manner, including, for example, using a cloud-based service. The ability to provide data via a server is particularly useful for providing data to a processing service. Post-acquisition image processing depends on the certainty of knowledge of the satellite state vector (position / velocity components) at a particular time (e.g., scheduled imaging time). A filtered ephemeris (post-orbit determination) can thus provide a low uncertainty state vector that improves image processing quality, as further described with reference to FIG. 8.

[0098] The predicted data may be used for image scheduling in the image scheduler 125. Image scheduling relies on accurate prediction of future positions and pass times of the satellite, e.g., used at each pass of the satellite over the position, so that the best possible image of a particular position is formed. Both image planning (location and time) and radar mode setup rely on the accuracy of the predicted ephemeris. In this context, a "radar mode setup" may be a computational script (i.e., a computer readable medium containing logic) that, when executed, sets or determines parameters related to the imaging procedure performed by the satellite. For example, the radar mode setup may set the time at which the imaging procedure is initiated. Additionally or alternatively, the radar mode setup may set or determine the repetition frequency at which the satellite emits the imaging signal, or may set or determine the pulse repetition frequency on the processing board of the satellite. In the system shown in FIG. 1, this is provided by the designed OD API, which improves accuracy with each pass with new ephemeris data downlink.

[0099] The image scheduler 125 may request data from the OD server 105. The data may be in JSON or other suitable form compatible with the API. Importantly, the predictions are no longer in the form of ephemeris files. The organization of the data in the OD server 105 allows the image scheduler to request data for a particular time span and only obtain a small amount of data. Operations that the image scheduler 125 may perform are further described with reference to FIG. 8.

[0100] For example, a satellite needs to be maneuvered from time to time to ensure that it is repeatedly in orbit, i.e., in the same place at the same time every day, or to comply with other requirements, or to change its orbit. This may be particularly important in large constellations of different satellites, where different satellites monitor different places at different times. Thus, orbit maintenance may be scheduled periodically, for example at regular time intervals such as weekly.

[0101] In the system of FIG. 1, for orbit maintenance purposes, satellite position and / or status data obtained, for example, via the server 105 API, may be fed into the orbit simulator 115.

[0102] Orbit simulator 115 may simulate the movement of the satellite to determine maneuver parameters to return the satellite to a desired orbit or to achieve a new orbit, such as time and thrust duration, as described below. After simulation, the determined maneuver parameters may be provided to a collision avoidance service, shown as collision avoidance API 130.

[0103] In the system shown in FIG. 1, the maneuver parameters are provided to an orbit determination module shown in block 127. The orbit determination module 127 may determine a new orbit for the satellite when a maneuver is performed, for example, using a dynamic model of the satellite's movement similar to that used in the OD process tool 103. That is, the model may be updated each time one or more new state vectors are filtered by the filter module of the OD process tool 103, as described above. Additionally or alternatively, the model may be updated manually by a user of the system 100, who may update the model. In this way, the determination of the new orbit may be based on the latest (i.e., most recent) measurement / determination of the satellite state vector.

[0104] Collision avoidance services are known in the art and are provided to avoid collisions between satellites or between satellites and space debris. Details of the planned maneuver may be provided to a collision avoidance API 130 which provides similar details from other satellite operators and existing orbits of other satellites and other objects in space. The collision avoidance service responds by providing a collision probability. In decision block 135 of FIG. 1, a decision is made as to whether the collision probability CP is low enough that a maneuver can be performed. If yes, then a command is given to the operational controller 140 to perform a maneuver to steer the satellite 100.

[0105] The collision avoidance service continuously monitors the movement of other satellites and objects in space to detect possible collisions. A satellite may therefore subscribe to the collision avoidance service and periodically notify the CA API of its status to alert it to a collision risk in the absence of a planned maneuver. Thus, the collision avoidance operations described with reference to FIG. 1 may be in addition to periodically notifying the collision avoidance API of satellite ephemerides and predictions not shown in FIG. 1.

[0106] An example of a collision avoidance process for planning maneuvers is described in more detail below with reference to FIG.

[0107] The dotted lines at the top of FIG. 1 indicate the flight parameters for the scheduled flight that are provided to the OD server 105.

[0108] In any of the methods and systems described herein, in response to receiving a collision probability, the planning of the maneuver may be performed automatically, i.e., without human intervention. In general, the system of FIG. 1 performs a method for scheduling a maneuver according to a collision probability. For example, if the collision probability is greater than a threshold, the maneuver may be postponed from the planned time. Rather than simply performing the maneuver at a time different from the determined time, it may be necessary to perform the collision probability determination again at a different time until a time is found where the collision probability is equal to or less than the threshold. This is further described with reference to FIG. 4 and FIG. 5.

[0109] The systems described herein may be used to ensure that satellites are in the correct orbit with minimal collision probability, and may be configured to perform maneuvers only after certain tasks have been performed.

[0110] Using Maneuvering Data in Position Data Filtering - Patent application Figure 2 is a schematic diagram illustrating in more detail the operations that may be performed by the OD server 105 and OD processing tools 103 of the system of Figure 1. In particular, Figure 2 illustrates how maneuvering data is used to filter the raw satellite position data.

[0111] FIG. 2 shows that raw position data, such as GPS data, provided from the ground station network 101 is provided to the ephemeris archive 110, the OD process tool 103, and the OD server 105. The OD server 105 is also provided with maneuver data from the maneuver process, including, for example, maneuver parameters, as shown in block 210. This data may relate to scheduled future maneuvers and / or performed maneuvers. For example, the received data related to historical maneuvers may confirm that a scheduled maneuver has occurred or that a satellite has been commanded to perform a scheduled maneuver. Additionally or alternatively, the received data related to historical maneuvers may include information related to the direction, magnitude, and / or orientation of any forces applied to perform the historical maneuver. Thus, in the OD process tool 103, data related to scheduled maneuvers, e.g., either or both of historical and future maneuvers, may be configured to be used in filtering the raw ephemerides in addition to the GPS data as inputs to the OD filter. This additional input data to the filter helps to reduce the margin of error in the filtered data.

[0112] The OD API in the OD Server 105 may be used to request and obtain data for use by other services, including services related to the operation of the satellites. Such services may include so-called path scheduling, which determines when a particular satellite will be within operational communication range of a particular ground station. This may help determine the time windows during which software updates can be delivered from the ground station to a particular satellite. An example message flow is shown in Figure 2.

[0113] The OD API may receive a request 211 for data, such as location and / or status data, for a particular time span. The time span may be in the history or future, and may span the history and future. Sometimes it may be 12 hours or more in the past, 24 hours or more in the past, 48 hours or more in the past, 72 hours or more in the past, or as far back in the past as possible. For example, the time span may extend 6 hours or more in the future, 12 hours or more in the future, 18 hours or more in the future, 24 hours or more in the future, 36 hours or more in the future, 48 hours or more in the future, 72 hours or more in the future, or 120 hours or more in the future. The OD process tool 103, for example under the control of the OD server 105, may send a request 212 to the OD server via the OD API to provide maneuver data over a particular time range. The sending of the request 212 may be in response to receiving the request 211 or may be for a particular time range specified in the request 211. Additionally or alternatively, the system of FIG. 2 may operate such that queries 212 are sent to the OD process tool 103 periodically, such that the queries 212 are already available via the API provided in response to the requests 211. The periodic requests may relate to the same time period compared to the moment they are sent, e.g., the previous and future 24 hours, or the previous and future 48 hours. That is, the OD server 105 or OD process tool 103 may receive the steering data periodically, such as for a continuous time span, or at a continuous time span. The OD process then has an easily accessible supply of steering data for use in the filtering process.

[0114] The OD API sends a response 213 to the OD process tool 103 that includes details of planned and / or historical maneuvers during the particular time period specified in the request 212. The details of the historical maneuvers may include the duration of the maneuver, the start time of the maneuver, the stop time of the maneuver, the magnitude of thrust / burns associated with the maneuver, and / or the attitude of the thrust / burns associated with the maneuver. The details of the planned maneuver may include the duration of the maneuver, the magnitude of thrust / burns associated with the maneuver, and / or the attitude of the thrust / burns associated with the maneuver. The details of the planned maneuver may further include the predicted / planned start and / or stop time of the maneuver. The OD process tool 103 outputs a filtered ephemeride 214 using the historical maneuver data in filtering the raw GPS ephemeride data if some or all of that time span is historical. For example, the OD process tool 103 may use the historical maneuver data as an input to update a statistical model of the satellite orbit (e.g., generated by an extended Kalman filter) to form a more accurate historical force model. Anomalous data points caused by unexpected maneuvers in the raw GPS ephemeris data can now be identified as maneuvers and smoothed to provide filtered ephemerides 214. Additionally or alternatively, if some or all of the time span of the query 212 or request 211 is in the future, the OD process tool uses this to generate future predicted ephemerides 215 that are sent from the OD process tool 213 to the OD server 105. The ephemerides output from the OD process tool 103 to the OD server 105 may be provided by the OD server 105 to a requesting service, which may be servicing processes internal or external to the satellite.

[0115] In a specific example of the operation of the OD filtering process, the OD filter in the OD process tool 103 is fed with maneuver data that may include the duration and time of each maneuver, each maneuver being a historical or future planned maneuver. The command sent to perform the maneuver may be notified to the OD filter by verifying that the planned maneuver was commanded to be performed. If the verification fails, i.e., it is determined that the maneuver is not performed or was not performed, the data related to the maneuver may be deleted. In some examples, there may be another process, e.g., a task service, that records whether the command to perform a particular maneuver was successfully sent to the satellite and, finally, whether the maneuver was successfully performed. The OD filter (re)creates the maneuver by importing the received maneuver data, e.g., models the maneuver, which can be used in determining the satellite position and / or state at any time in the history or future. As mentioned elsewhere, the OD filter may use a dynamic model of the satellite's movement in the filtering process, as known in the OD determination. Once the maneuver is imported into the OD process, it is used to redefine the dynamic model of the satellite for a particular period of the particular maneuver. Therefore, they are only used to generate the desired OD solutions (filtered data) or predictions (ephemeris created based on theoretical dynamics models rather than actual measurements).

[0116] The desired / predicted attitude of the spacecraft is also described in the OD process to fit the dynamic model of the satellite. This attitude data may be collected at every pass of the satellite. The attitude data may be stored, for example, in an attitude file that is appended to every pass of the satellite. By including the attitude data in the state vector data, the precise motion of the satellite can be modeled. This precise position model can be combined with state vector measurements (e.g. GPS measurements) and / or satellite dimensions to improve the reliability and accuracy of the dynamic model, thereby enabling more accurate filtering of the data by the OD filter. This improves the accuracy of predictions made based on the dynamic model, improves the planning of orbital maneuvers, and improves the accuracy of post-processing of orbital information.

[0117] More specifically, the OD filter may output filtered position data based on different estimates of position, the different estimates including the raw position data and an estimate of position based on a schedule maneuver. Additionally or alternatively, the OD filter may output state vectors (i.e., a data set including both position data and velocity data). These state vectors are predicted state vectors of the satellite's future state and may be derived from forward propagation in time of the orbit data, taking into account the created dynamic model. This may also take into account the satellite's schedule maneuvers. When predicting ephemeride state vectors, the raw state vector data, e.g., raw position data in the form of raw GPS ephemeride data, is only an initial starting point for the process of determining the satellite's future orbital direction. In instances where the initial state vector of the satellite is unambiguous and accurate, the reliability (i.e., confidence) of the predicted orbit / trajectory may be improved.

[0118] In one example of the operation of the OD process, in the OD filter, two types of filters (statistical processes) are applied in a process that includes the following steps:

[0119] 1) BWLS (Bayesian Weighted Least Squares) - This is basically a curve fitting process. It does not use a dynamic model and is used to give a better initial guess to move to the next filtering step. Here, all the data is processed at once.

[0120] 2) The next step is OSF (Ordered Statistical Filtering), which is a Kalman filter, where the data is processed sequentially. Here, we use the dynamic model to get the most accurate updates. The optimum minimizes the uncertainty in the state estimation. The model uncertainty is determined from the magnitude and variability of this uncertainty (process noise). Here, we move from old data to new data.

[0121] 3) The second OSF, also called the Smoother. Same as (2), but time-reversed. Kalman filters generally seek to minimize state uncertainty with knowledge of the convergence of previous states (uncertainty levels) and use a dynamic model to make a best guess.

[0122] In both stages 2 and 3, the dynamic model may be based on future scheduled maneuvers of the satellite. The dynamic model may be further based on data related to historical maneuvers of the satellite. Using data related to historical maneuvers of the satellite may improve the accuracy of the dynamic model, i.e., the uncertainty value associated with the dynamic model may decrease.

[0123] It should be noted that the OD process may not be aware of the path of the satellite over the Earth or other maneuvers. A system querying the API for orbital data is not aware of any maneuvers, either future or historical, and does not need to take them into account to perform its tasks. Maneuvers are well represented in both the predicted and filtered orbital data provided by the API. The OD process may be configured to request new data from the OD server 105, for example, periodically, or automatically when new raw data is received. The OD process may be configured to provide predicted ephemeride and / or position data continuously in another form for a predefined time in the future, for example, to always "think" 24 hours ahead. This process can be run anywhere on a suitable computing device, such as a laptop device, or theoretically could be run on a computing system on board the satellite.

[0124] The OD process tool 103 may provide an automated method of verifying that a planned maneuver has been performed. In one example, propulsion telemetry from the satellite may be monitored, for example programmatically. If the maneuver is to be performed, a particular thrust magnitude from a particular thrust module is expected. If this expected magnitude is not detected, the maneuver may be assumed to have failed, i.e., not been performed, and data relating to the maneuver may be automatically removed from the OD process, e.g., data relating to the planned maneuver previously provided to the OD process tool 103 may be removed or discarded. Data relating to the detected thrust magnitude may be measured directly from the thrusters and / or estimated from satellite position data after the thrust has been applied. That is, the thrust magnitude may be determined based on telemetry data indicative of the satellite position and / or velocity after the thrust has been applied. In some examples, there may be differences in the theoretical orbital behavior of the satellite (based on the predicted magnitude of thrust from the thrust module). The OD process tool 103 may determine a thrust correction that adjusts the magnitude and / or direction of thrust applied by the thrust module based on the difference between the historical actual orbital behavior and the theoretical orbital behavior to minimize the difference between the future actual orbital behavior and the theoretical orbital behavior. Also, a reinitialization of the scenario due to its thrust corrections may be commanded at a certain time (e.g. T-6Hrs). Reinitializing the scenario may include resetting the dynamic model of the satellite so that only a short period of recent measurements (e.g. measurements from the previous 6 hours) is calculated instead of being built from all measurements made previously. This can reduce the memory requirements of the OD process tool 103. In the context of image acquisition from the satellite, this procedure is performed for all passes of images scheduled at T+24hrs. Processing or tasking due to maneuver failures can be avoided. Since maneuver failures still need to be performed for purposes such as orbit keeping and collision avoidance, the orbit simulator 115 needs to be alerted of the maneuver failures, e.g. via an output from the OD server 105.The maintenance process may again be performed, for example, by commanding the propulsion system to generate additional burns (i.e., thrust), typically after proactively checking the collision probability via the collision avoidance API 130. In the case of a collision avoidance maneuver, the propulsion system may similarly be commanded to generate additional or corrective burns or thrust.

[0125] In the system described with reference to Figures 1 and 2, the OD server 105 is responsible for cataloging the received data, including but not limited to raw GPS ephemerides, filtered historical ephemerides, future predicted ephemerides, and maneuver data. Any of these data may be provided to the server 105 as separate items, such as individual files. For example, ephemerides may typically be provided to a file for each satellite pass, and maneuver data may be provided as a discrete item for each maneuver. This cataloging of data by the server or other suitable computing system allows the data to be searched in various ways, for example, by time or in a particular coordinate system. This cataloging may also be performed for multiple satellites in the same constellation by the same server or computing system. Then, for example, satellite positions over a period of time, satellite maneuvers over a period of time, and other information well known to those skilled in the art, may be obtained for one or a group of satellites.

[0126] Quality control of the OD process Figure 3 is a block diagram illustrating a quality control "QC" system used to ensure accurate predictions are sent to the API of the OD Server 105. The QC here may consist of creating statistics using proprietary tools along with proprietary decision making and retry logic implemented in the OD Server 105.

[0127] The QC process of Figure 3 may be incorporated into the system of Figure 1 such that only data of a particular quality is provided to the OD server 105. This process may be implemented as part of the OD process tool 103 or in a separate quality control module between the output of the OD process tool 103 and the input to the OD server 105. In any case, the operation of the process shown in Figure 3 may be controlled to operate automatically from the OD server 105 without the need for manual intervention.

[0128] In FIG. 3, a quality control process takes place in the OD process tool 103, receiving raw GPS ephemerides as input data. Additionally, details of planned and historical maneuvers can be used in the process. Next, an OD scenario is created as shown in 301, the results of which, in the form of filtered ephemerides, are subjected to statistical tests 303. The statistical tests may check the reliability of the scenario data in any suitable manner, for example, a confidence value exceeding a predefined threshold. The statistical tests may be performed using a proprietary third party statistical software tool. If the filtered ephemerides meet the confidence threshold at decision 305, the filtered ephemerides are sent to the OD server 105 at 307 by a flow similar to 214 in FIG. 2. If not, the flow returns to 301, this time with additional input data, for example spanning an earlier or longer period of time. Then, additional information may be requested from the GPS queue 102 to re-perform operations 301, 303, 305. In the example of FIG. 3, additional measurements from the previous 6 hours are requested, whereas in the first iteration, only data from the previous hour may have been used.

[0129] collision avoidance FIG. 2 is a block diagram illustrating in more detail a collision avoidance process that may be implemented in the system of FIG. 1. The trajectory simulator 115, the orbit determination module 127, the collision avoidance API 130, and the decision block 135 may operate in a similar manner as previously described with reference to FIG.

[0130] In general, the maneuver data output from orbit simulator 115 to orbit determination module 127 may include more than just the date of the maneuver, the exact time, the duration of the thrust, the magnitude and pointing direction of the thrust, the specific impulse of the thrust, and the attitude of the satellite. For simplicity, only the date and thrust duration are shown in FIG.

[0131] If the probability of collision is determined to be low in decision block 135, e.g., below a predefined threshold, a command is sent from the operational controller 140 to steer the satellite 100. Also, details of the planned maneuver, such as date and duration, are sent to the OD server 105. This may be all or part of the maneuver data passed to the OD server 105 in block 210 of FIG. 2, and may be used by the OD server 105 to control the operation of the OD process tool 105 to generate filtered OD ephemeris data that is fed back to the orbit simulator 115.

[0132] If the probability of collision is not low as determined in decision block 135, the orbit simulator is notified of the time when the potential collision is closest and feedback is provided to the orbit simulator to determine new maneuver parameters.

[0133] FIG. 2 is a block diagram showing operations that may be performed by orbit simulator 115.

[0134] As shown in FIG. 4, the orbit simulator 115 receives the filtered efmeds via the API of the OD server 105. In FIG. 5, it is shown that two processes of determining maneuver data are performed in parallel. One is performed at regular intervals, for example every two weeks, to maintain the satellite in a specific orbit. The other is triggered by a collision alert, for example a collision probability exceeds a predefined threshold, either for the satellite to continue in its current orbit or by a planned maneuver, for collision avoidance. The collision avoidance maneuver plan may be based on either or both the collision probability and the time of closest approach. It is ensured that the new maneuver data defines a maneuver that is unlikely to cause a collision. This new maneuver data is fed to the collision avoidance API 130, which again determines the collision probability. The steps of determining maneuver parameters, receiving a collision alert, and determining new collision parameters may be repeated until the new collision parameters do not result in a collision alert.

[0135] Satellite function operation plan In addition to planned maneuvers for orbit maintenance and collision avoidance, maneuver planning may also take into account the current state of the satellite, for example its propulsion system. Additionally or alternatively, the satellite position relative to the sun may be taken into account to avoid the propulsion system operating when the satellite is fully exposed to the sun and at risk of overheating. A possible maneuver planning process is shown diagrammatically in Figure 6 and may be implemented in the system of Figure 1.

[0136] In the process shown in FIG. 6, first an orbit simulation is performed in maneuver 601 to determine the maneuver parameters, such as time, duration, magnitude, pointing direction, etc. Then, a collision avoidance process, represented by CA block 603, is performed as described above. Then, it may be assumed that the maneuver parameters resulting from the CA process meet the requirement of low collision probability. Thus, the flow in block 600 starts with receiving parameters for a planned maneuver to move the satellite from a current orbit to a new orbit, the parameters including maneuver time and duration. The parameters may specify a time window for the execution of the maneuver, during which the maneuver may be scheduled to be performed, subject to one or more other constraints, including either or both of the exposure to the sun and the current capability of the satellite propulsion system, as to when the maneuver is to be performed.

[0137] Next, in operation 605, a propulsion scheduling requirement for performing the maneuver is determined, and in operation 607, a determination is made as to whether the requirement can be met. Factors considered in determining the propulsion scheduling requirement may include any power state or states, such as available batteries, propulsion temperature, propulsion state, etc. For example, a thruster may need to be heated to a certain temperature in order to fire. This temperature may be referred to as a propulsion temperature. The propulsion temperature may be 125° C. or greater, 150° C. or greater, 175° C. or greater, 200° C. or greater. For example, the propulsion temperature may be 173° C. The propulsion state may include data indicative of the status or performance of various components of the satellite. For example, the propulsion state may indicate which of the satellite's modules are damaged or have failed (e.g., Fault Detection, Isolation, and Recovery (FDIR) reset, etc.).

[0138] If the propulsion scheduling requirements are not met within the time window, then iterations of the orbit simulation 601 and CA process 603 are performed until maneuvering parameters that the satellite can perform are determined.

[0139] In operation, estimates of the times of eclipse 609 are obtained. These indicate when the sun is eclipsed by the earth and the satellite is in the shadow of the earth. Also, to ensure that the satellite does not overheat during maneuvers, it is preferable to perform the maneuvers when the sun is covered by the earth. The combination of heat from the sun and heat generated by the satellite's propulsion system can cause the satellite to overheat and become damaged. In some cases, it has been found that it is sufficient to avoid operations while the propulsion units are facing the sun. This can be achieved by scheduling the maneuvering time to avoid a percentage of the orbit where the satellite's exposure to the sun is maximum, for example, one-quarter of the orbit where the exposure is maximum. The operation of the thrusters is then such that no more than three-quarters of each complete orbit around the earth, or one-quarter of the orbit where the exposure to the sun is maximum, is avoided and passes.

[0140] FIG. 7 illustrates an example of a satellite 100 that may operate using the systems and processes described herein. The satellite comprises a generally rectangular body, referred to in the art as a "bus." A solar panel 702 is attached to a rectangular face of the body, to which additional solar panels are attached via supports. The satellite comprises a generally planar structure extending in two opposite directions from the body to provide two "wings" that may support an antenna array 704 and other components. When the satellite is in orbit, the surface of the "wings" opposite the body generally faces the surface of the Earth. The satellite comprises a propulsion system 706 that steers the satellite with the thrust generated. The propulsion system is attached to the body on the surface opposite the solar panel. The propulsion system comprises a number of thrusters 706 that generate thrust to steer the satellite as needed. The thrusters of FIG. 7 satellite may be located at the corners on one side of the body and spaced equally apart.

[0141] The propulsion system is used to steer the satellite 100 to change the satellite orbit or altitude. As noted elsewhere herein, this may be, for example, to keep the satellite in a particular orbit if the altitude changes slightly, or to avoid a collision with another object in space. Additional steering of the satellite is possible, for example, to change the attitude of the satellite for a particular imaging mode. Thus, whereas a large satellite imaging device may be steered relative to the satellite for a particular image acquisition procedure, the satellite 100 as shown in FIG. 7 may be a small, highly agile micro-satellite, but may be steered overall to change its attitude. Such steering may be performed using the satellite ADCS unit.

[0142] Satellites may be classified according to their mass: for example, satellites with a mass between about 1 kg and about 10 kg may be classified as cube satellites, satellites with a mass between about 50 kg and about 250 kg may be classified as microsatellites, satellites with a mass of about 500 kg may be classified as small satellites, and satellites with a mass between about 800 kg and about 1200 kg may be classified as regular satellites.

[0143] Satellite 100 may be, in one example, a microsatellite with a mass of 100 kg. Conventional satellites with masses of around 1000 kg are generally more expensive and less agile than microsatellites. Embodiments of the maneuvering plans, collision avoidance, orbit change, and other methods described herein may be applied to one or more microsatellites with masses between 50 kg and 250 kg.

[0144] From the above, it can be seen that for most of the path of the satellite 100, the propulsion system 706 is shielded from the Sun by the satellite body, but during the orbital quarter shown as 4 / 4 in Figure 7, the propulsion system 706 is exposed to the Sun and it is therefore desirable to avoid operating the propulsion system 706 during this period. Information about the time of the eclipse can therefore be used to plan maneuvers to avoid this part of the satellite orbit.

[0145] For example, at the beginning of an orbital quarter, shown as Q1 in FIG. 7, satellite 100 may be eclipsed by the Earth. Thus, maneuvers (using propulsion system 706) begin in Q1 of the orbit. Satellite 100 may end the eclipse at the end of Q2, as shown in FIG. 7. However, during Q3 of the orbit, the body of satellite 100 shields propulsion system 706 from exposure to radiation from the Sun. It is not until the satellite crosses the ecliptic, which marks the beginning of Q4 of the orbit, that propulsion system 706 is exposed to solar radiation. Thus, maneuvers (using propulsion system 706) end at or at the end of Q3 of the orbit.

[0146] For satellites in low Earth orbit, the eclipse typically lasts 34.5 minutes, with the orbit lasting 95.6 minutes.

[0147] In operation 611, as explained above, the maneuver is scheduled to occur at a time or times when the satellite is in the Earth's shadow, or at least its propulsion system is not fully exposed to the Sun.

[0148] Operation 611 results in the output of steering parameters to the satellite 100, or to the operational controller 140, as shown in Figure 1. These are also output to the OD server 105, as shown in block 210 of Figure 2.

[0149] Note that collision avoidance is prioritized over satellite capability and solar exposure avoidance in the process of Figure 6. In general, the process of determining maneuver parameters to satisfy the criteria of collision avoidance, satellite capability, solar exposure avoidance, and other criteria that apply to the determination of maneuver parameters may occur in any order and may vary depending on current conditions.

[0150] From the foregoing, it will be appreciated that the maneuver parameters resulting from the CA process, or whichever process prevails, can specify a time window for the execution of the maneuver, within which the maneuver can be more precisely timed to meet one or more other criteria.

[0151] To meet various criteria regarding the timing of a maneuver, a maneuver defined by parameters output from a first process, such as a CA process, may be performed as a series of sub-maneuvers. For example, a time span or window output from the CA process may include at least two orbits of a satellite around the Earth. The total period of the maneuver may then be divided into shorter durations occurring on different passes of the satellite. Thus, output parameters obtained from operation 611 may include the date / time and duration of the (sub)operation in addition to the magnitude, e.g., thrust (or burn) force magnitude.

[0152] Image Scheduling FIG. 8 illustrates operations that may be performed by the image scheduler 125 of FIG. 1. The image scheduler operates to compile image data acquired by image acquisition devices on the satellite into a composite image as is known in the SAR imaging art. This process is sometimes referred to as image stacking, as shown in FIG. 8. Newly acquired data is continually added to the image stack. In compiling the data, it is important to know precisely the satellite position at the time of data acquisition. The process shown in FIG. 8 adds image data to the stack only if the position estimate is sufficiently accurate.

[0153] The flow of FIG. 8 assumes that SAR image data acquired over a particular time span has been received.

[0154] As shown in Figure 8, the image scheduler 125 may request filtered ephemerides from the OD server 105 for a particular time span. The filtered ephemerides are used to estimate or determine the geolocation error associated with the particular image data. The request may be sent when new image data is received. Alternatively, the request may be sent for each batch of image data. Alternatively, this information may be provided to the image scheduler from the OD server periodically, not necessarily on demand.

[0155] As shown in FIG. 8, the filtered ephemerides can be used to estimate the geolocation error of the satellite at a particular time. The geolocation error may be determined at the end of each iteration of the OD process. Then, upon determining whether the error is high, e.g., above a predefined threshold, it is preferable not to import the image data for that time into the image processing stack. Instead, a request for new filtered ephemerides is sent from the image scheduler 125 to the OD server 105, after which the geolocation error is estimated again. Due to the fact that the estimation is based on a larger data set than the previous one, the resulting error should be low. The iterations of error estimation and requesting additional filtered ephemerides may be performed until the error is low enough to add the associated image data to the image stack processing.

[0156] It is important to note that since image scheduling is constantly running, there is no need to be aware of maneuvers, orbit changes, or collision avoidance performed by the satellite, as these will always be represented in the latest orbit determination provided by the OD API.

[0157] Propulsion System Calibration Some of the methods and systems described herein may provide an opportunity to more precisely control the operation of a satellite's propulsion system. For example, they can be used to calibrate the propulsion system. This is particularly useful for propulsion systems that cannot be easily tested on the ground. For example, ground testing is not recommended for some ion low thrust engines. In such cases, estimating the performance of the propulsion system may be done, for example, to estimate a position based on commands given to the propulsion system. Such calibration is useful not only for initial operation without ground testing, but also during operation as the performance of the propulsion system changes with use.

[0158] FIG. 9 is a block diagram illustrating operations that may be performed by a propulsion system calibrator in the system of FIG.

[0159] In the OD process 901, the position certainty derived from the maneuver data can be highlighted, for example, in one or both parameters, magnitude and pointing. In this way, the OD results can provide information about the performance of the propulsion systems, such as engines and thrusters, in a particular maneuver. Correction estimation reports and graphs can be generated and stored, allowing the systems engineering team to draw conclusions about performance and proceed with calibration actions that result in more accurate maneuvers / predictions and filtered solutions. Within the OD process 901, there may be uncertainty models of maneuver inputs that take into account uncertainties in thrust magnitude, pointing, etc.

[0160] In an example calibration process, a maneuver is commanded from the motion controller 140. The command includes thrust magnitude, duration, and direction and is based on an assumed relationship between these parameters and the expected changes in the satellite's orbit, or state vector. The command is intended to change the satellite's orbit by a predetermined amount. The command is implemented and the satellite orbit is changed. The amount of orbit change can be determined from the resulting filtered ephemerides, which can be used to confirm or update the assumed relationship. The filtering process for determining the filtered ephemerides takes into account the expected changes in the satellite's orbit.

[0161] The OD process 901 may receive raw GPS effect data and latest (stored) maneuver data based on the latest command maneuver. From this input, the OD process 901 generates an updated orbit model. This updated orbit model includes an uncertainty model capturing uncertainties in thrust magnitude and pointing of the satellite maneuvers, and performs a statistical consistency test 903. If the updated orbit model fails the statistical consistency test 903, the OD process 901 refines the orbit model and adjusts the uncertainties until the orbit model and the associated uncertainty model pass the consistency test 903. If the orbit model passes the consistency test 903, the final updated orbit model is passed to further modules to generate a correction model. This correction model may be in the form of an exported correction graph. The exported correction graph 905 may be used to compensate for uncertainties in maneuver parameters such as thrust magnitude and pointing in future maneuver planning simulations.

[0162] Any of the components of the systems described herein may be comprised of a computing system or may be incorporated into a computing system.

[0163] The computing systems described herein may be combined into a single computing system having multiple functions. Similarly, the functionality of any computing system described herein may be distributed across multiple computing systems.

[0164] Some operations of the methods described herein may be performed by software, for example in a machine-readable form, for example in the form of a computer program including computer program code. Thus, some aspects of the invention provide a medium readable by a computing system that, when implemented in a computing system, causes the system to perform some or all of the operations of any of the methods of the invention. The computer-readable medium may be in a transitory or tangible (or non-transitory) form, such as a storage medium, such as a disk, thumb drive, memory card, etc. The software is suitable for execution on a parallel or serial processor such that the method steps may be performed in any suitable order or simultaneously.

[0165] In embodiments of the present invention, the system may be implemented as any form of computing and / or electronic system, as described elsewhere herein. A device such as herein may include one or more processors, which may be microprocessors, controllers, or any other suitable type of processor, for processing computer-executable instructions for controlling the operation of the device to collect and record routing information. In some examples, for example when using a system-on-chip architecture, the processor may include one or more fixed function blocks (also called accelerators) that implement parts of the method in hardware (rather than software or firmware). Platform software, including an operating system or other suitable platform software, may be provided to the computing-based device to enable application software to run on the device.

[0166] As used herein, the term "computing system" is used to refer to any device having processing capability capable of executing instructions. Those skilled in the art will appreciate that such processing capability may be incorporated into many different devices, and thus the term "computing system" includes PCs, servers, smart cell phones, personal digital assistants, and many other devices.

[0167] It should be understood that the above benefits and advantages may relate to one embodiment or to several embodiments, and the embodiments are not limited to those that solve any or all of the problems mentioned or that have the benefits and advantages mentioned.

[0168] Any reference to an "item" or "piece" refers to one or more of those items unless otherwise specified. The term "comprising" is used herein to mean including the specified method steps or elements, but that such steps or elements do not constitute an exclusive list and that the method or apparatus may include additional steps or elements.

[0169] The accompanying figures illustrate exemplary methodologies. Although the methodologies are shown and described as a series of operations performed in a particular order, it is understood and should be understood that the methodologies are not limited by the order. For example, some operations may occur in a different order than described herein. Also, some actions may occur simultaneously with other actions. Furthermore, in some cases, not all operations may be required to implement the methodologies described herein.

[0170] Although the ordering of steps of the methods described herein is exemplary, the steps may be performed in any suitable order, or simultaneously where appropriate. Additionally, steps may be added or substituted to any method, or single steps may be deleted from any method, without departing from the scope of the subject matter described herein. Aspects of any of the above embodiments may be combined with aspects of any of the other embodiments described above to form further embodiments.

[0171] The above description of the preferred embodiment is given by way of example only, and it should be understood that various modifications may be made by those skilled in the art. The above includes one or more exemplary embodiments. Of course, it is not possible to describe all possible modifications and variations of the above-described device or method for the purpose of describing the above-described aspects, but those skilled in the art will recognize that many further modifications and substitutions of various aspects are possible. Thus, the described aspects are intended to include all such modifications, variations, and variations that fall within the scope of the appended claims.

[0172] Examples and embodiments of the present disclosure can be understood with reference to the following sections. 1. A method for processing satellite status data, comprising: receiving satellite status data in the form of a plurality of separate files via one or more ground stations; The method includes compiling the received satellite status data into a single data set accessible via an application programming interface and searchable over a range of time. 2. The method of claim 1, wherein the satellite state data includes raw data. 3. Filtering the raw satellite state data in an orbit determination process; providing filtered satellite state data; The filtering is performed in parallel with the compilation of the received satellite status data; 3. The method of claim 2, wherein each item of the filtered satellite state data corresponds to an item of the raw satellite state data. 4. The method of any one of the preceding claims, further comprising the step of receiving steering data relating to one or more scheduled maneuvers for the satellite, and compiling the received steering data into a data set accessible via an application programming interface and searchable by time range. 5. A method according to claim 4 dependent on claim 3, wherein the steering data is used to filter the received raw satellite status data. 6. A method for processing satellite status data, comprising: receiving raw satellite status data; receiving steering data relating to one or more scheduled maneuvers for the satellite; and filtering the received raw satellite state data in an orbit determination process to provide filtered satellite state data; A method, wherein the steering data is used to filter the received raw satellite state data. 7. The step of receiving the raw satellite status data comprises: receiving the raw satellite condition data in the form of a plurality of separate files via one or more ground stations; The method comprises: 7. The method of claim 6, further comprising compiling the received raw satellite state data into a single data set accessible via an application programming interface and searchable over a range of time. 8. The method of claim 7, further comprising the step of compiling the received steering data into a data set accessible via an application programming interface and searchable by time range. 9. The method according to claim 1, further comprising the step of scheduling the navigation of the satellite, the step of scheduling the navigation of the satellite comprising: receiving received parameters for one or more scheduled maneuvers for moving the satellite from a current orbit to a new orbit, the parameters including a time and duration of one or more of the scheduled maneuvers; receiving a time of a solar eclipse by the earth during a future orbit of the satellite; and scheduling the maneuver according to the determined parameters and a time of the eclipse. 10. A method for scheduling satellite steering, comprising: received parameters for one or more planned maneuvers to move the satellite from a current orbit to a new orbit, the parameters including a time and duration of the one or more planned maneuvers; receiving a time of a solar eclipse by the earth during a future orbit of the satellite; and scheduling the maneuver to occur according to the determined parameters and the time of the eclipse. 11. The received parameters include satellite status data; The method further comprises processing the satellite status data, the processing of the satellite status data comprising: receiving said satellite condition data in the form of a plurality of separate files via one or more ground stations; and compiling the received satellite state data into a single data set accessible via an application programming interface and searchable over a range of time. 12. The method of claim 11, wherein the satellite state data includes raw data. 13. The step of processing the satellite status data comprises: In an orbit determination process, further comprising filtering the raw satellite state data to provide filtered satellite state data; 13. The method of clause 12, wherein each item of the filtered satellite state data corresponds to an item of the raw satellite state data. 14. The method of claim 12 or 13, wherein the step of processing the satellite status data further includes receiving steering data relating to one or more scheduled maneuvers of the satellite, and compiling the received steering data into a data set accessible via an application programming interface and searchable by time range. 15. A method according to claim 14 dependent on claim 13, wherein the steering data is used to filter received raw satellite data. 16. The received parameters include raw satellite status data and steering data relating to one or more scheduled maneuvers for the satellite; The method further includes processing the satellite state data, the processing the satellite state data comprising: receiving the raw satellite status data; receiving steering data relating to one or more scheduled maneuvers for the satellite; filtering the received raw satellite state data in the orbit determination process to provide filtered satellite state data; 11. The method of claim 10, wherein the steering data is used to filter the received raw satellite state data. 17. The method of claim 16, wherein the step of processing the satellite state data further comprises the step of compiling the received raw satellite state data into a single data set accessible via an application programming interface and searchable over a range of time, the raw satellite state data being received in the form of a plurality of separate files via one or more ground states. 18. The method of any one of clauses 3, 7, 13, 17 or any dependent clause thereof, further comprising the step of inserting the filtered satellite state data into the single data set. 19. A method according to any one of claims 3, 6, 13, 16 or any dependent thereon, wherein the filtered satellite state data includes satellite state history data, which is optionally actual data associated with one or more historical state vectors of a satellite. 20. A method according to any one of clauses 3, 6, 13, 16 or any dependent clause thereon, wherein the filtered satellite state data includes future satellite state data, which is optionally projection data based on a dynamic model configured to predict a future state vector of a satellite. 21. A method according to any one of clauses 1-9 or 11-20, further comprising the step of mapping metadata relating to the satellite to the satellite status data. 22. The metadata is: Data relating to the physical dimensions of the satellite; Satellite attitude data, and / or 22. The method of claim 21, including one or more of the satellite thrust data including information related to the satellite's history and future planned maneuvers. 23. A method according to any one of clauses 3, 6, 13 and 16 or clauses 21 and 22 dependent thereon, further comprising the step of providing the metadata used to filter the raw satellite state data. 24. The received maneuver data, for each of the one or more scheduled maneuvers, Operation time, Duration of thrust, The magnitude of thrust, Thrust direction, and / or

[0033] including one or more of the thrust ratio shocks, A method according to any one of paragraphs 4, 6, 14, 16 or any clause subordinate thereto. 25. The method of any one of clauses 4, 6, 14, 16 or any dependent clause thereon, wherein the one or more scheduled maneuvers include one or more future scheduled maneuvers for the satellite. 26. The method of claim 25, further comprising the step of maintaining a dynamic model of the movement of the satellite and updating the dynamic model with data relating to the one or more future scheduled maneuvers. 27. A method according to clause 26 dependent on clause 3, clause 6, clause 13, clause 16 or any clause dependent thereon, wherein the estimate of the satellite state obtained from the dynamic model is used to filter received raw satellite state data. 28. The method of claim 27, wherein the step of filtering the raw satellite state data is performed based on different estimates of the satellite state, the different estimates including the raw state data and an estimate of the satellite state based on future scheduled maneuvers. 29. The method of claim 27 or 28, wherein the estimate of the satellite state includes an estimate of the satellite position. 30. The method of any one of paragraphs 4, 6, 14, 16, or any clause dependent thereon, wherein the one or more scheduled maneuvers include one or more historical maneuvers. 31. The steering data relating to one or more historical maneuvers of the satellite includes, for each of the one or more historical maneuvers of the satellite: Operation time, Duration of thrust, The magnitude of thrust, Thrust direction, and / or

[0023] including one or more measurements of thrust ratio impact; 31. The method according to claim 30. 32. The method of claim 31, further comprising using the measurement data to determine whether a scheduled maneuver has been performed after the scheduled maneuver has been scheduled to be performed. 33. The method of any one of clauses 1-9 or 11-32, further comprising copying the satellite status data received since the previous interval to a working directory. 34. The method of any one of paragraphs 1, 7, 11 or any dependent thereon, wherein the dataset is stored in a relational database. 35. A method according to any one of clauses 1, 7 or 11 or any dependent clause thereon, wherein the satellite state data is received as a file for each pass of the satellite and the data in the data set is searchable over a period of time including multiple passes. 36. The method of any one of clauses 9 or 10 or any dependent clause thereon, wherein the step of scheduling maneuvers for the satellite further comprises the step of scheduling the maneuvers to avoid a proportion of the orbit in which the satellite has maximum exposure to the sun. 37. The method of claim 36, wherein the proportion of the trajectory to be avoided is one-quarter of the trajectory. 38. A method according to paragraph 9 or paragraph 10, or any one of the paragraphs dependent thereon, wherein the duration of at least one of the planned maneuvers is a duration including at least two orbits of the satellite around the Earth. 39. The method of any one of paragraphs 9 or 10 or any dependent paragraph thereon, wherein at least one of the planned maneuvers is a maneuver for returning the satellite to a predetermined orbit. 40. A method according to any one of paragraphs 9 or 10 or any dependent paragraph thereon, wherein at least one of the planned maneuvers is a maneuver to avoid a collision. 41. The step of scheduling the satellite operations comprises: determining candidate parameters for one or more of the planned maneuvers for moving the satellite from a current orbit to a new orbit, the parameters including a candidate time and a candidate duration for each of the planned maneuvers; providing said candidate parameters to a collision avoidance system; receiving a respective probability of collision from the collision avoidance system based on each set of candidate parameters; 41. The method of claim 40, further comprising: determining new candidate parameters for the one or more planned maneuvers if the respective collision probabilities exceed a predetermined threshold; and repeating the operation of determining candidate parameters for each of the one or more planned maneuvers until at least one of the respective collision probabilities falls below the predetermined threshold. 42. The step of scheduling the satellite operations comprises: receiving a forwarding scheduling requirement; The method of claim 9 or 10, or any claim dependent thereon, further comprising the step of: scheduling the maneuver to occur in accordance with the propulsion scheduling requirements. 43. A method of operating a satellite, comprising scheduling satellite operations to occur in accordance with paragraph 9 or paragraph 10, or any one of the paragraphs subordinate thereto. 44. A method of operating a satellite propulsion system, comprising: commanding a maneuver for the satellite based on steering data for one of one or more future scheduled maneuvers and based on an assumed relationship between the steering data for the commanded maneuver and an orbital change of the satellite; receiving satellite status data relating to an orbit of the satellite after performing the command maneuver in accordance with the command; and verifying or updating the assumption relationship based on the received satellite status data; A method, wherein the orbit of the satellite is determined in an orbit determination process as described in any one of clauses 3, 6, 13, 16 or any clause dependent thereon. 45. A method for processing SAR image data receiving image data acquired during a time span; receiving satellite status data processed according to any one of the methods of clauses 1, 6, 11, 16 or any dependent clauses, the received satellite status data corresponding to a time span associated with the received image data; using the received satellite state data to estimate or determine a geographic position error associated with the satellite position estimate; if the geographical position error is greater than a predetermined threshold, requesting satellite status data for a longer time span and repeating the estimation of the geographical position error; and passing the image data onto a stack for further processing only if the geolocation error is below a predetermined threshold. 46. ​​A data processing device comprising a processor for carrying out the method of the preceding paragraph. 47. A distributed computing system configured to carry out the method of any one of clauses 1 to 45. 48. A computer-readable medium comprising logic that, when executed by a computer, causes the computer to perform any of the methods of paragraphs 1 to 45. 49. A computer program comprising commands which, when executed by a computer, cause the computer to carry out any of the methods of paragraphs 1 to 45.

Claims

1. 1. A method for scheduling satellite steering, comprising: receiving parameters for one or more planned maneuvers for moving the satellite from a current orbit to a new orbit, the parameters including a time and duration of the one or more planned maneuvers; receiving a time of a solar eclipse by the earth during a future orbit of the satellite; and scheduling the maneuver to occur in accordance with the determined parameters and a time of the eclipse.

2. 2. The method of claim 1, wherein the step of scheduling maneuvers for the satellite further comprises the step of scheduling the maneuver items to avoid a percentage of an orbit in which the satellite has maximum exposure to the sun.

3. The method of claim 2 , wherein the percentage of the trajectory to avoid is one-quarter of the trajectory.

4. 2. A method according to any one of the preceding claims, wherein the duration of at least one of the planned maneuvers is a duration including at least two orbits of the satellite around the Earth.

5. 10. The method of claim 1, wherein at least one of the planned maneuvers is a maneuver for returning the satellite to a predetermined orbit.

6. 10. The method of claim 1, wherein at least one of the planned maneuvers is a maneuver to avoid a collision.

7. The step of scheduling the steering of the satellite comprises: determining candidate parameters for one or more of the planned maneuvers for moving the satellite from a current orbit to a new orbit, the parameters including a candidate time and a candidate duration for each of the planned maneuvers; providing said candidate parameters to a collision avoidance system; receiving a respective probability of collision from the collision avoidance system based on each set of candidate parameters; determining new candidate parameters for the one or more planned maneuvers if the respective collision probabilities exceed a predetermined threshold; 7. The method of claim 6, further comprising repeating the act of determining candidate parameters for each of the one or more planned maneuvers until at least one of the respective collision probabilities falls below the predetermined threshold.

8. The step of scheduling the steering of the satellite comprises: receiving a forwarding scheduling requirement; 4. The method of claim 1, further comprising the step of: scheduling maneuvers to occur in accordance with said propulsion scheduling requirements.

9. the received parameters include satellite status data; The method further comprises processing the satellite status data, the processing of the satellite status data comprising: receiving said satellite condition data in the form of a plurality of separate files via one or more ground stations; and compiling the received satellite status data into a single data set accessible via an application programming interface and searchable over a range of time.

10. The method of claim 9 , wherein the satellite state data comprises raw data.

11. The step of processing the satellite status data further comprises: In an orbit determination process, further comprising filtering the raw satellite state data to provide filtered satellite state data; The method of claim 10 , wherein each item of the filtered satellite condition data corresponds to an item of the raw satellite condition data.

12. 12. The method of claim 10 or 11, wherein the step of processing the satellite status data further comprises the steps of receiving steering data relating to one or more scheduled maneuvers of the satellite, and compiling the received steering data into a data set accessible via an application programming interface and searchable by time range.

13. A method according to claim 12 when dependent on claim 11, wherein the steering data is used to filter received raw satellite data.

14. the received parameters include raw satellite status data and steering data relating to one or more scheduled maneuvers for the satellite; The method further includes processing the satellite state data, the processing the satellite state data comprising: receiving the raw satellite status data; receiving steering data relating to one or more scheduled maneuvers for the satellite; filtering the received raw satellite state data in the orbit determination process to provide filtered satellite state data; A method of processing data as claimed in any preceding claim, wherein the steering data is used to filter the received raw satellite status data.

15. 15. The method of claim 14, wherein the step of processing the satellite state data further comprises the step of compiling the received raw satellite state data into a single data set accessible via an application programming interface and searchable over a range of time, the raw satellite state data being received in the form of a plurality of separate files via one or more ground conditions.

16. The method of any one of claims 11 to 13 or 15, further comprising inserting the filtered satellite state data into the single data set.

17. 17. The method of claim 11, wherein the filtered satellite state data includes historical satellite state data, which is optionally actual data associated with one or more historical state vectors of a satellite.

18. 18. The method of any one of claims 11 to 17, wherein the filtered satellite state data comprises future satellite state data, optionally projection data based on a dynamic model configured to predict a future state vector of a satellite.

19. The method of any one of claims 9 to 18, further comprising the step of mapping metadata about the satellites to the satellite status data.

20. The metadata includes: Data relating to the physical dimensions of the satellite; Satellite attitude data, and / or 20. The method of claim 19, including one or more of the satellite thrust data including information related to historical and future planned maneuvers of the satellite.

21. 21. The method of claim 19 or 20, further comprising the step of providing the metadata for use in filtering the raw satellite state data.

22. The received maneuver data comprises, for each of the one or more scheduled maneuvers: Operation time, Duration of thrust, The magnitude of thrust, Thrust direction, and / or [0033] including one or more of the thrust ratio shocks; The method according to any one of claims 12 to 21.

23. The method of any one of claims 12 to 22, wherein the one or more scheduled maneuvers include one or more future scheduled maneuvers for the satellite.

24. 24. The method of claim 23, further comprising the steps of maintaining a dynamic model of the satellite's movement and updating the dynamic model with data relating to the one or more future scheduled maneuvers.

25. 25. The method of claim 24, wherein the estimates of satellite states obtained from the dynamic model are used to filter received raw satellite state data.

26. 26. The method of claim 25, wherein the step of filtering the raw satellite state data is based on different estimates of the satellite state, the different estimates including the raw state data and an estimate of a satellite state based on a future scheduled maneuver.

27. 27. The method of claim 25 or 26, wherein the estimate of the satellite state includes an estimate of the satellite position.

28. The method of any one of claims 12 to 27, wherein the one or more schedule maneuvers include one or more historical maneuvers.

29. The steering data relating to one or more historical maneuvers of the satellite includes, for each of the one or more historical maneuvers of the satellite: Maneuver time, thrust duration, The magnitude of thrust, Thrust direction, and / or Thrust ratio impact, 30. The method of claim 28, comprising one or more measurements of:

30. 30. The method of claim 29, further comprising using the measurement data after a scheduled maneuver has been scheduled to be performed to determine whether the scheduled maneuver has been performed.

31. The method of any one of claims 9 to 30, further comprising the step of copying the satellite status data received since a previous interval to a working directory.

32. 10. The method of claim 9 or any preceding claim dependent thereon, wherein the data set is stored in a relational database.

33. 10. A method according to claim 9 or any preceding claim dependent thereon, wherein the satellite state data is received as a file for each pass of the satellite, and data in the data set is searchable over a period of time including multiple passes.

34. A method for operating a satellite, the steering of which is scheduled according to a method according to any one of the preceding claims.

35. 1. A method of operating a satellite propulsion system, comprising: commanding a maneuver for the satellite based on steering data for one of one or more future scheduled maneuvers and based on an assumed relationship between the steering data for the commanded maneuver and an orbital change of the satellite; receiving satellite status data relating to an orbit of the satellite after performing the command maneuver in accordance with the command; and verifying or updating the assumption relationship based on the received satellite status data; A method, wherein the orbit of the satellite is determined in an orbit determination process according to claim 11, 14 or any preceding claim dependent thereon.

36. 1. A method for processing SAR image data, comprising the steps of: receiving image data acquired during a time span; receiving satellite status data processed according to a method according to claim 9, 14 or any preceding claim depending thereon, the received satellite status data corresponding to a time span associated with the received image data; using the received satellite state data to estimate or determine a geographic position error associated with the satellite position estimate; if the geographical position error is greater than a predetermined threshold, requesting satellite status data for a longer time span and repeating the estimation of the geographical position error; and passing the image data onto a stack for further processing only if the geolocation error is below a predetermined threshold.

37. A data processing apparatus comprising a processor for carrying out a method according to any one of the preceding claims.

38. A distributed computing system configured to carry out a method according to any one of claims 1 to 36.

39. A computer readable medium comprising logic which, when executed by a computer, causes the computer to perform the method of any one of claims 1 to 36.

40. A computer program comprising instructions which, when executed by a computer, cause the computer to carry out the method according to any one of claims 1 to 36.

Citation Information

Patent Citations

  • Optimized power balanced variable thrust transfer orbits to minimize an electric orbit raising duration

    EP3670359A1

  • Collision avoidance assistance device, satellite constellation formation system, collision avoidance assistance method, collision avoidance assistance program, collision avoidance assistance system, space situational awareness business device, satellite constellation business device, rocket launching business device, debris removal business device, space insurance management device, space object management business device, and space traffic management business device

    WO2021060492A1