Space traffic management archtecture for manageing satellites and space debris

Abstract

The present disclosure provides a space traffic management system. The system includes A space docking station system that includes a first rail having to mechanically and electrically couple and decouple at least one of a plurality of satellites thereto; a second rail to mechanically and electrically couple and decouple at least one of the plurality of satellites thereto; and thrust / maneuvering control circuitry disposed on the first rail or second rail, the thrust / maneuvering control circuitry configured to communicate with the satellite to exchange docking and undocking commands, and maneuvering and thrust commands with the at least one of the plurality of satellites.

Description

SPACE TRAFFIC MANAGEMENT ARCHTECTURE FOR MANAGEING SATELLITES AND SPACE DEBRISSTATEMENT OF GOVERNMENT INTEREST

[0001] This invention was made with government support under contract number 80NSSC19M0197 awarded by the National Aeronautics and Space Administration (NASA). The government has certain rights in the invention.Cross-Reference to Related Application

[0002] The present application claims the benefit of US Provisional Application Serial No. 63 / 742,318, filed January 6, 2025, which is hereby incorporated by reference in its entirety.Technical Field

[0003] The present disclosure is generally directed to a space traffic management architecture for managing satellites and space debris.Brief Description of the Drawings

[0004] The above-mentioned and other features of this disclosure, and the manner of attaining them, will become more apparent and better understood by reference to the following description of embodiments described herein taken in conjunction with the accompanying drawings, wherein:

[0005] FIG. 1 illustrates a space traffic management system according to embodiments of the present disclosure;

[0006] FIG. 2 illustrates an example deployment of multiple docking station systems along multiple orbital paths around the Earth;

[0007] FIG. 3 illustrates a trajectory plot of an orbital transfer according to one embodiment of the present disclosure;

[0008] FIG. 3A illustrates orbital transfer simulation equations according to one example embodiment; and

[0009] FIGS. 4A-4F illustrate examples of satellite maneuvering with respect to a docking station system and with respect to other satellites within a given orbital path

[0010] Although the following Detailed Description will proceed with reference being made to illustrative embodiments, many alternatives, modifications and variations thereof will be apparent to those skilled in the art.Detailed Description

[0011] The present disclosure provides a space traffic management system that is generally configured to be deployed along a selected orbital path and along a selected orbital plane. The system includes a docking station that includes a plurality of rails configured to couple and decouple satellites thereto, to enable, for example, refueling of a satellite, repair of a satellite, etc. and to control the traffic flow of satellites along the selected orbit. The system includes thrust / maneuvering control circuitry disposed on the first rail or second rail, to exchange thrust and maneuvering commands with the plurality of satellites, and to schedule docking and undocking times for satellites along the orbital path. The system may be configured with fueling depots for the satellites to enable refueling at scheduled times, and may also include mechanical / electrical component storage to retrofit, repurpose and / or repair a satellite. In some embodiments, satellites may be configured to capture space debris and to transport the space debris to the docking station.

[0012] FIG. 1 illustrates a docking station system 100 according to embodiments of the present disclosure. As a general matter, the system 100 of FIG. 1 is generally configured to be deployed in a selected orbital position, i.e., disposed on a selected orbital path and on a selected orbital plane. The system 100 of FIG. 1 is generally configured to control traffic of a plurality satellites that are orbiting along the selected orbital path and the selected orbital plane. The system 100 generally includes a first rail 102 and a second rail 104 disposed generally parallel to one another. Rail 102 and / or rail 104 may be formed of a plurality of rail segments, and thus may be expanded to accommodate a given number of satellites. In some embodiments, satellite trajectories associated with rail 102 are generally indicated by arrow 111, and satellite trajectories associated with rail 104 are generally indicated by arrow 113. Thus, the system 100 may manage traffic flow for satellites moving in the same direction in a selected orbital path. Thus, the docking station system 100 defines traffic lanes 111 and 113 within the orbital path to enable more accurate management of a variety of different types of satellites.

[0013] For example, traffic lane 111 may be designated as a “slow” lane such that the docking station system 100 exchanges commands and data with the satellites within the orbital path to cause selected satellites to orbit within the lane 111. Similarly, traffic lane 113 may be designated as a “fast” lane such that the docking station system 100 exchanges commands anddata with the satellites within the orbital path to cause selected satellites to orbit within the lane 113. In other embodiments, the lanes may be designated for distinct orbital operations. For example, lane 111 may be designated as a “space debris” lane and the docking station system 100 exchanges trajectory commands and data with the satellites within the orbital path to cause selected satellites to orbit within the lane 111 for depositing space debris onto the rail 102 of the docking station system 100. while the docking station system 100 exchanges trajectory commands and data with other selected satellites within the orbital path to cause selected satellites to orbit within the lane 113 for receiving fuel and / or repairs after docking with rail 104 of the docking station system 100. Of course, the foregoing represents example satellite management operations, and it should be noted that other management protocols may be performed, for example, changing orbital paths, timing of release and docking of satellites, etc.

[0014] A crossbar member 106 is coupled between rails 102 and 104 to provide a fixed distance, D, between each rail. In some embodiments, the distance D is selected, based on, at least in part, an overall orbital accuracy and resolution for the satellites within the selected orbital path. In some embodiments, the system 100 may include a plurality of crossbar members spaced apart along the lengths of the rails 102 and 104. Each rail, for example rail 102, may be formed of a plurality of modular segments, e.g., segments 116A, 116B, 116C,..., 116N, to form a rail having a desired length to accommodate, for example, management of a selected number of satellites as may be found in a given orbital path. The segments 116A, 116B, 116C,.... 116N may be mechanically coupled together, for example using latching mechanisms (not shown), friction-fit mechanisms (not shown), etc. and / or any known type of mechanical coupling such as screws, rivets, bolts, etc.

[0015] As illustrated, rail 102 is generally configured to dock and undock a plurality of satellites 103 along the length of the rail 102. Similarly, rail 104 is generally configured to dock and undock a plurality of satellites 105 along the length of the rail 104. To that end, each rail 102 and / or 104 may also include a plurality of pads 112 to mechanically and electrically couple a satellite to the rail, to enable a satellite to dock and undock from each rail.

[0016] The system 100 also includes at least one storage container 110 coupled to rail 102 and / or rail 104. The storage container 110 may be used to store fuel for the satellite(s). To that end, the rail 102 may include fuel conduits (not shown) to transport fuel from the storage container 110 to one or more satellites docked along the rail 102. In addition, the storage container 110 may beused to store mechanical and / or electrical equipment for repairing, repurposing and / or updating a satellite. The system 100 may also include a robotic arm 114 coupled to the first rail or second rail, the robotic arm being controlled to remove debris along an orbital path of the first and second rails.

[0017] The system 100 also includes thrust / maneuvering control circuitry 108 that generally includes communications circuitry to exchange commands and data with one or more satellites. Circuitry 108 is generally configured to generate thrust and / or maneuver commands for the plurality of satellites in the orbital path, to provide collision avoidance maneuvers, docking and undocking maneuvers, trajectory / lane / orbital changes, etc., as described herein. The thrust / maneuvering control circuitry 108 is also configured to schedule docking of satellites for repair / refueling, and to schedule undocking of a satellite into the traffic flow of other satellites along the orbital path, and to provide satellite trajectory commands and data, as described below. The thrust / maneuvering control circuitry 108 may also include one or more antenna systems to communicate with one or more satellites, one or more docking station systems and / or terrestrial communications.

[0018] FIG. 2 illustrates an example deployment of multiple docking station systems along multiple orbital paths around the Earth. To enable management of multiple satellites along an orbital path, and to enable movement of satellites between orbital paths, a first plurality of docking stations systems, e.g., 100A, 100B, 100C, 100D are deployed to be coincident along a first orbital path 202. Similarly, a second plurality of docking stations systems, e.g., 100E, 100F, 100G, 100H are deployed to be coincident along a second orbital path 204. In the example of FIG. 2, there are four first plurality of docking stations systems, e.g., 100A, 100B, 100C, 100D and four second plurality of docking stations systems, e.g., 100E, 100F, 100G, 100H, however, it should be understood that any number of docking station systems may be deployed along an orbital path, depending on, for example, anticipated satellite traffic density, anticipated space debris burden, etc. In addition, while two orbital paths 202 and 204 are depicted in FIG. 2, it should be understood that numerous other / additional orbital paths may be selected for deployment of one or more docking station systems. In addition, the docking stations 100 A, 100B, 100C, 100D in orbital path 202 and docking stations 100E, 100F, 100G, 100H in orbital path 204 are illustrated as being approximately equally spaced apart along their respective orbital paths. However, it should be noted that, in some embodiments, the docking stations may bedisposed along their respective orbital paths based on, for example, satellite traffic density such that the docking stations are not necessarily equidistant from each other, etc.

[0019] As is also shown in FIG. 2, docking station system 1001 has initiated a departure from orbital path 204 and targeting orbital path 202. To initiate redeployment of a satellite into a different orbital path, for example, from a lower orbital path to a higher orbital path and / or different traffic lane, in one embodiment the thrust / maneuvering control circuitry 108 may generate trajectory commands to a target satellite to initiate a change in orbital path. FIG. 3 illustrates a trajectory plot 300 of an orbital transfer according to one embodiment of the present disclosure. In the example of FIG. 3, a satellite 303, initially in orbit 302 applies a specified thrust (delta V) to initiate a change to orbit 304, causing the satellite to break out of orbit 302 along Path 2. At a determined time, a second specified thrust (delta V’) is applied to cause the satellite to move into orbit 304, shown at Path 3. To determine timing and thrust vectors, the thrust / maneuvering control circuitry 108 may utilize a Hohmann transfer and / or other known and / or proprietary trajectory control models. As a general matter, for a satellite to perform a Hohmann transfer, it has to accomplish two impulsive bums. Generally speaking, it is difficult for thrusters to produce enough delta-v in a single impulse to achieve the speeds required for the rendezvous maneuver. However, it is assumed that the thrusters are idealized and capable of producing such thrust. Thus, in the case of a smaller orbit to a larger orbit, it increases its velocity at the periapsis of the transfer ellipse and re-circularizes its orbit at the apoapsis of the transfer ellipse. The process is reversed, with a firing of known retro thrusters associated with the satellite to decrease speed for a larger to a smaller orbit.

[0020] Such orbital transfer and / or lane change transfer may be simulated using the equations 300 in FIG. 3A. The first five equations are used to calculate the total delta-v changes that the craft must make. The final four equations are used to determine the wait time for the launch period of the spacecraft. The first step is to determine the current and final speeds of the circular orbits for the interceptor. Then, the transfer semimajor axis, at, is calculated as the average of the two orbital radii. After that, the vis-viva equation can be used to find the velocities of the transfer ellipse at both the periapsis and the apoapsis. If the orbit goes from a smaller to a larger orbit, the fourth equation is utilized, and the fifth equation is used otherwise. Each mathematical expression within absolute bounds is used to find the magnitude of their respective delta-v maneuvers. To guarantee that the interceptor arrives at the precise location that the target will be,the concept of the phase angle is utilized. The phase angle is the angular distance between the interceptor and the target, measured counter-clockwise. The initial phase angle, Φᵢ is the current phase angle, and Φ_f is the angle that is required for the Hohmann transfer to be completed. The Hohmann transfer has a useful property where the ideal phase angle is 180°. By using the aforementioned phase angles and the angular speeds of the target and interceptor, the wait time can be calculated.

[0021] FIGS. 4A-4F illustrate examples of satellite maneuvering with respect to a docking station system 100 and with respect to other satellites within a given orbital path. As a general matter, the thrust / maneuvering control circuitry 108 may generate satellite maneuvering and / or trajectory commands and communicate these commands to a satellite to achieve a desired satellite position. FIG. 4A illustrates a satellite service scenario 400 in which a satellite 403 is commanded to dock with the docking station system 100 for servicing / repair. In this example, the satellite communicates, to the docking station system 100, that it is low on fuel. The docking station system 100 generates maneuvering and / or trajectory commands to cause the satellite 403 to begin maneuvering toward the docking station system 100, as illustrated by initial thrust 405. As the satellite is heading toward the docking station system 100, the satellite 403 encounters another satellite 403’ in its path. The docking station system 100 issues another thrust command 407 to cause the satellite to maneuver around satellite 403’ and begin a docking maneuver.

[0022] FIG. 4B illustrates a satellite debris capture and removal scenario 420 in which a satellite 403 is commanded to undock with the docking station system 100 to maneuver to capture space debris 421 and return to the docking station system 100. In this example, the docking station system 100 communicates thrust and trajectory commands to the satellite to undock and maneuver toward space debris 421, as illustrated by initial thrust 423. As the satellite is heading toward the space debris, the satellite performs a maneuver to intercept the space debris 421, as illustrated by thrust execution 425. Once captured, the satellite maneuvers to return to the docking station system 100, as illustrated by thrust 427. In some embodiments, the space debris is unloaded at the docking station system 100. In other embodiments, on its way back to the docking station system 100, the satellite may use its momentum to release the space debris 421 towards Earth, thus de-orbiting the space debris 421 and allowing the space debris 421 to bum up in Earth’s atmosphere.

[0023] FIG. 4C illustrates a satellite service scenario 440 in which a satellite 403 is commanded to dock with a first docking station system 100 A and travel to a second docking station 100B for servicing / repair of the second docking station 100B. In this example, the docking station system 100 A receives a communication from docking station 100B that docking station 100B has a malfunctioning component. Docking station 100A communicates thrust and trajectory commands to the satellite 403 to undock and maneuver toward docking station 100B, as illustrated by initial thrust 443. In some embodiments, the maneuvering commands, generated by docking station 100A may include raising and / or lowering the orbital phase of the satellite 403, depending on the relative position of docking station 100B (e.g., docking station 100B is ahead or behind in phase with respect to docking station 100A). The payload of satellite 403 may include the necessary components to repair and / or replace the broken component on docking station 100B. Thrust 445 causes the satellite 403 to dock with docking station 100B.

[0024] FIG. 4D illustrates a satellite lane changing scenario 460 in which a satellite 403 is requesting to change from a first lane 411 to a second lane 413. In this example, the docking station system 100 receives a communication from satellite 403 that satellite 403 is seeking to change lanes. Alternatively, the docking station 100 may determine that congestion factors and / or mission factors require that the satellite change from lane 411 to lane 413. In either scenario, docking station 100 communicates thrust and trajectory commands to the satellite 403 to dock and maneuver toward docking station 100, as illustrated by initial thrust 463. The satellite 403 undocks and maneuvers into another lane (e.g., increases or decreases the semimajor axis of the satellite 403), as shown by thrust 465.

[0025] FIG. 4E illustrates a “heavy” reverse maneuver to avoid satellite collisions while docking. In this example, satellite 403 encounters another satellite 403’ in its path as satellite is headed toward the docking station 100. Satellite 403 executes a thrust maneuver, as indicated by thrust 481, to avoid satellite 403. However, in making this avoidance maneuver, the satellite 403 has passed the docking station 100. Thus, satellite 403 is commanded to execute a “heavy” reverse thrust (via, for example, retro rocket bursts, etc.) to reverse course to meet up with the docking station 100, as indicated by thrust 483. As satellite approaches the docking station 100, the satellite performs a docking maneuver to dock with docking station 100, as indicated by thrust 485.

[0026] Of course, the above description of FIGS. 4A-4E are provided as non-limiting examples of the types of maneuvering and thrust control commands that are generated by the docking station, as described herein. In addition, scheduling docking and / or undocking of one or more satellites may be based on, for example, overall density of satellites within a given orbit, tasking of “debris fields” in which numerous satellites may be released in rapid succussion as a docking station approaches a known debris field, emergency (e.g., low power) satellite requirements, and / or other scheduling scenarios.

[0027] Accordingly, a first example embodiment the present disclosure provides a space traffic management system that includes a first rail having a first plurality of docking pads disposed along the length of the first rail, each of the first plurality of docking pads configured to mechanically and electrically couple and decouple at least one of a plurality of satellites thereto; a second rail having a second plurality of docking pads disposed along the length of the second rail, each of the second plurality of docking pads configured to mechanically and electrically couple and decouple at least one of the plurality of satellites thereto; a crossbar member disposed between the first and second rails to dispose the first and second rails at a fixed distance apart relative to each other; and thrust / maneuvering control circuitry disposed on the first rail or second rail, the thrust / maneuvering control circuitry configured to communicate with at least one of the plurality of satellites to exchange docking and undocking commands, and maneuvering and thrust commands for the at least one of a plurality of satellites.

[0028] A second example embodiment includes the first example embodiment, wherein the first and second rails configured to be deployed in a selected orbital path to control traffic flow of one or more satellites travelling along the selected orbital path; wherein the first rail defines a first travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a first satellite of the plurality of satellites to travel within the first travel lane; and wherein the second rail defines a second travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite of the plurality of satellites to travel within the second travel lane.

[0029] A third example embodiment includes the first example embodiment, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to undock the at least one of the plurality of satellites from the first or second rail.

[0030] A fourth example embodiment includes the first example embodiment, wherein the thrust / maneuvering control circuitry of the first example embodiment is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to avoid a collision between two or more satellites.

[0031] A fifth example embodiment includes the first example embodiment, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for the one or more satellites dock the at least one of the plurality of satellites to the first or second rail.

[0032] A sixth example embodiment includes the first example embodiment, wherein the thrust / maneuvering control circuitry is further configured to schedule docking and / or undocking of at least one of the plurality of satellites based on, at least one of, overall density of satellites within a given orbit, debris field cleanup operations, and / or in response to an emergency scenario associated with the one or more satellites.

[0033] A seventh example embodiment of the present disclosure provides a space traffic management system that includes a first plurality of docking stations disposed along a first orbital path; a second plurality of docking stations disposed along a second orbital path; wherein each of the first and second plurality of docking stations comprising: a first rail having a first plurality of docking pads disposed along the length of the first rail, each of the first plurality of docking pads configured to mechanically and electrically couple and decouple at least one of a plurality of satellites; a second rail having a second plurality of docking pads disposed along the length of the second rail, each of the second plurality of docking pads configured to mechanically and electrically couple and decouple at least one of the plurality of satellites thereto; a crossbar member disposed between the first and second rails to dispose the first and second rails at a fixed distance apart relative to each other; and thrust / maneuvering control circuitry disposed on the first rail or second rail, the thrust / maneuvering control circuitry configured to communicate with at least one of the plurality of satellites to exchange docking and undocking commands, and maneuvering and thrust commands for at least one of the plurality of satellites.

[0034] An eighth example embodiment includes the seventh example embodiment, wherein the first rail of each of the first plurality of docking stations defines a first travel lane within the first orbital path, and wherein the thrust / maneuvering control circuitry to control at least a firstsatellite to travel within the first travel lane of the first orbital path; and wherein the second rail of the first plurality of docking stations defines a second travel lane within the first orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite to travel within the second travel lane of the first orbital path.

[0035] A ninth example embodiment includes the eighth example embodiment, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to cause the at least one of the plurality of satellites to change between the first and second travel lanes.

[0036] A tenth example embodiment includes the seventh example embodiment, wherein the first rail of each of the second plurality of docking stations defines a first travel lane within the second orbital path, and wherein the thrust / maneuvering control circuitry to control at least a first satellite to travel within the first travel lane of the second orbital path; and wherein the second rail of the second plurality of docking stations defines a second travel lane within the second orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite to travel within the second travel lane of the second orbital path.

[0037] An eleventh example embodiment includes the tenth example embodiment, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to undock the at least one of the plurality of satellites from the first or second rail.

[0038] A twelfth example embodiment includes the seventh example embodiment, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to avoid a collision between two or more satellites.

[0039] A thirteenth example embodiment includes the seventh example embodiment, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to dock the at least one of the plurality of satellites to the first or second rail.

[0040] A fourteenth example embodiment includes the seventh example embodiment, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations is further configured to schedule docking and / or undocking of at least one of the plurality of satellites based on, at least one of, overall density of satellites within a given orbit, debris field cleanup operations, and / or in response to an emergency scenario associated with the one or more satellites.

[0041] A fifteenth example embodiment includes the seventh example embodiment, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to cause the at least one of the plurality of satellites to change between the first and second travel lanes.

[0042] A sixteenth example embodiment includes the seventh example embodiment, wherein the thrust / maneuvering control circuitry of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to cause the at least one of the plurality of satellites to change between the first and second travel lanes.

[0043] An eighteenth example embodiment includes the seventh example embodiment, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to cause the at least one of the plurality of satellites to change between the first and second orbital paths.

[0044] A nineteenth example embodiment of the present disclosure provides a space docking station system that includes a first rail having to mechanically and electrically couple and decouple at least one of a plurality of satellites thereto; a second rail to mechanically and electrically couple and decouple at least one of the plurality of satellites thereto: and thrust / maneuvering control circuitry disposed on the first rail or second rail, the thrust / maneuvering control circuitry configured to communicate with the satellite to exchange docking and undocking commands, and maneuvering and thrust commands with the at least one of the plurality of satellites.

[0045] A twentieth example embodiment includes the nineteenth example embodiment, and further includes a storage container coupled to the first rail and / or second rail, the storage containerfor storing fuel for at least one of the plurality of satellites, mechanical equipment for at least one of the plurality of satellites, and / or electrical equipment for at least one of the plurality of satellites.

[0046] A twenty-first example embodiment includes the nineteenth example embodiment, and further includes a robotic arm coupled to the first rail or second rail, the robotic arm being controlled to remove debris along an orbital path of the first and second rails.

[0047] A twenty- second example embodiment includes the nineteenth example embodiment, wherein the first rail being formed of a plurality of rail segments.

[0048] A twenty-third example embodiment includes the nineteenth example embodiment, wherein the second rail being formed of a plurality of rail segments.

[0049] A twenty-fourth example embodiment includes the nineteenth example embodiment, wherein the first and second rails configured to be deployed in a selected orbital path to control traffic flow of one or more satellites travelling along the selected orbital path; wherein the first rail defines a first travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a first satellite to travel within the first travel lane; and wherein the second rail defines a second travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite to travel within the second travel lane.

[0050] A twenty-fifth example embodiment includes the nineteenth example embodiment, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to undock the at least one of a plurality of satellites from the first or second rail.

[0051] A twenty-sixth example embodiment includes the nineteenth example embodiment, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of a plurality of satellites to avoid a collision between two or more satellites.

[0052] A twenty-seventh example embodiment includes the nineteenth example embodiment, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of a plurality of satellites dock the one or more satellites to the first or second rail.

[0053] A twenty-eighth example embodiment includes the nineteenth example embodiment, wherein the thrust / maneuvering control circuitry is further configured to schedule docking and / or undocking of at least one of the plurality of satellites based on, at least one of, overall density ofsatellites within a given orbit, debris field cleanup operations, and / or in response to an emergency scenario associated with at least one of the plurality of satellites.

[0054] The foregoing represents non-exhaustive embodiments that are provided by the teachings of the present disclosure. It should be understood that the foregoing example embodiments may be combined in a manner not specified above, but fully supported by the present disclosure. In addition, it should be understood that the teachings of the present disclosure provide other embodiments not specifically listed above.

[0055] As used in this application and in the claims, a list of items joined by the term “and / or” can mean any combination of the listed items. For example, the phrase “A, B and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C. As used in this application and in the claims, a list of items joined by the term “at least one of’ can mean any combination of the listed terms. For example, the phrases “at least one of A, B or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0056] Any of the operations described herein may be implemented in a system that includes one or more non-transitory storage devices having stored therein, individually or in combination, instructions that when executed by circuitry perform the operations. Such instructions may embodied as, for example, machine code, and / or “higher level” implementations such as software programing, application (app) programming, etc. “Circuitry”, as used in any embodiment herein, may comprise, for example, singly or in any combination, hardwired circuitry, programmable circuitry such as processors comprising one or more individual instruction processing cores, state machine circuitry, and / or firmware that stores instructions executed by programmable circuitry and / or future computing circuitry including, for example, massive parallelism, analog or quantum computing, hardware embodiments of accelerators such as neural net processors and non-silicon implementations of the above. The circuitry may, collectively or individually, be embodied as circuitry that forms part of a larger system, for example, an integrated circuit (IC), system on-chip (SoC), application-specific integrated circuit (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, etc.

[0057] The storage device includes any type of tangible medium, for example, any type of disk including hard disks, floppy disks, optical disks, compact disk read-only memories (CD-ROMs), compact disk rewritables (CD-RWs), and magneto-optical disks, semiconductor devices such asread-only memories (ROMs), random access memories (RAMs) such as dynamic and static RAMs, erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), flash memories. Solid State Disks (SSDs), embedded multimedia cards (eMMCs), secure digital input / output (SDIO) cards, magnetic or optical cards, or any type of media suitable for storing electronic instructions. Other embodiments may be implemented as software executed by a programmable control device. Also, it is intended that operations described herein may be distributed across a plurality of physical devices, such as processing structures at more than one different physical location.

[0058] The terms and expressions which have been employed herein are used as terms of description and not of limitation, and there is no intention, in the use of such terms and expressions, of excluding any equivalents of the features shown and described (or portions thereof), and it is recognized that various modifications are possible within the scope of the claims. Accordingly, the claims are intended to cover all such equivalents. Various features, aspects, and embodiments have been described herein. The features, aspects, and embodiments are susceptible to combination with one another as well as to variation and modification, as will be understood by those having skill in the art. The present disclosure should, therefore, be considered to encompass such combinations, variations, and modifications.

Claims

CLAIMSWhat is claimed is:

1. A space traffic management system, comprising:a first rail having a first plurality of docking pads disposed along the length of the first rail, each of the first plurality of docking pads configured to mechanically and electrically couple and decouple at least one of a plurality of satellites thereto;a second rail having a second plurality of docking pads disposed along the length of the second rail, each of the second plurality of docking pads configured to mechanically and electrically couple and decouple at least one of the plurality of satellites thereto;a crossbar member disposed between the first and second rails to dispose the first and second rails at a fixed distance apart relative to each other; andthrust / maneuvering control circuitry disposed on the first rail or second rail, the thrust / maneuvering control circuitry configured to communicate with at least one of the plurality of satellites to exchange docking and undocking commands, and maneuvering and thrust commands for the at least one of the plurality of satellites.

2. The system of claim 1. further comprising a storage container coupled to the first rail and / or second rail, the storage container for storing fuel for at least one of the plurality of satellites, mechanical equipment for at least one of the plurality of satellites, and / or electrical equipment for at least one of the plurality of satellites.

3. The system of claim 1, further comprising a robotic arm coupled to the first rail or second rail, the robotic arm being controlled to remove debris along an orbital path of the first and second rails.

4. The system of claim 1, wherein the first rail being formed of a plurality of rail segments.

5. The system of claim 1, wherein the second rail being formed of a plurality of rail segments.

6. The system of claim 1, wherein the first and second rails configured to be deployed in a selected orbital path to control traffic flow of at least one of the plurality of satellites travelling along the selected orbital path; wherein the first rail defines a first travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a first satellite of the plurality of satellites to travel within the first travel lane; and wherein the second rail defines a second travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite of the plurality of satellites to travel within the second travel lane.

7. The system of claim 1, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to undock the at least one of the plurality of satellites from the first or second rail.

8. The system of claim 1, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to avoid a collision between two or more satellites.

9. The system of claim 1, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to dock the at least one of the plurality of satellites to the first or second rail.

10. The system of claim 1, wherein the thrust / maneuvering control circuitry is further configured to schedule docking and / or undocking of at least one of the plurality of satellites based on, at least one of, overall density of satellites within a given orbit, debris field cleanup operations, and / or in response to an emergency scenario associated with at least one of the plurality of satellites.

11. A space traffic management system, comprising:a first plurality of docking stations disposed along a first orbital path;a second plurality of docking stations disposed along a second orbital path;wherein each of the first and second plurality of docking stations comprising:a first rail having a first plurality of docking pads disposed along the length of the first rail, each of the first plurality of docking pads configured to mechanically and electrically couple and decouple at least one of a plurality of satellites;a second rail having a second plurality of docking pads disposed along the length of the second rail, each of the second plurality of docking pads configured to mechanically and electrically couple and decouple at least one of the plurality of satellites thereto; a crossbar member disposed between the first and second rails to dispose the first and second rails at a fixed distance apart relative to each other; and thrust / maneuvering control circuitry disposed on the first rail or second rail, the thrust / maneuvering control circuitry configured to communicate with at least one of the plurality of satellites to exchange docking and undocking commands, and maneuvering and thrust commands for the at least one of the plurality of satellites.

12. The system of claim 11, further comprising a storage container coupled to the first rail and / or second rail of at least one of the first plurality of docking stations or at least one of the second plurality of docking stations, the storage container for storing fuel for at least one of the plurality of satellites, mechanical equipment for at least one of the plurality of satellites, and / or electrical equipment for at least one of the plurality of satellites.

13. The system of claim 11, further comprising a robotic arm coupled to the first rail or second rail of at least one of the first plurality of docking stations or at least one of the second plurality of docking stations, the robotic arm configured to be controlled to remove debris along an orbital path of the first and second rails.

14. The system of claim 11, wherein the first rail of at least one of the first plurality of docking stations or at least one of the second plurality of docking stations being formed of a plurality of rail segments.

15. The system of claim 11, wherein the second rail of at least one of the first plurality of docking stations or at least one of the second plurality of docking stations being formed of a plurality of rail segments.

16. The system of claim 11, wherein the first rail of each of the first plurality of docking stations defines a first travel lane within the first orbital path, and wherein the thrust / maneuvering control circuitry to control at least a first satellite to travel within the first travel lane of the first orbital path; and wherein the second rail of the first plurality of docking stations defines a second travel lane within the first orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite to travel within the second travel lane of the first orbital path.

17. The system of claim 11, wherein the first rail of each of the second plurality of docking stations defines a first travel lane within the second orbital path, and wherein the thrust / maneuvering control circuitry to control at least a first satellite to travel within the first travel lane of the second orbital path; and wherein the second rail of the second plurality of docking stations defines a second travel lane within the second orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite to travel within the second travel lane of the second orbital path.

18. The system of claim 11, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to undock the at least one of the plurality of satellites from the first or second rail.

19. The system of claim 11, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is furtherconfigured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to avoid a collision between two or more satellites.

20. The system of claim 11, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to dock the at least one of the plurality of satellites to the first or second rail.

21. The system of claim 11, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations is further configured to schedule docking and / or undocking of at least one of the plurality of satellites based on, at least one of, overall density of satellites within a given orbit, debris field cleanup operations, and / or in response to an emergency scenario associated with the at least one of the plurality of satellites.

22. The system of claim 16, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to cause the at least one of the plurality of satellites to change between the first and second travel lanes.

23. The system of claim 17, wherein the thrust / maneuvering control circuitry of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for at least one of the plurality of satellites to cause the at least one of the plurality of satellites to change between the first and second travel lanes.

24. The system of claim 11, wherein the thrust / maneuvering control circuitry of each of the first plurality of docking stations and of each of the second plurality of docking stations is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to cause the at least one of the plurality of satellites to change between the first and second orbital paths.

25. A space docking station system, comprising:a first rail having to mechanically and electrically couple and decouple at least one of a plurality of satellites thereto;a second rail to mechanically and electrically couple and decouple at least one of the plurality of satellites thereto; andthrust / maneuvering control circuitry disposed on the first rail or second rail, the thrust / maneuvering control circuitry configured to communicate with the satellite to exchange docking and undocking commands, and maneuvering and thrust commands with the at least one of the plurality of satellites.

26. The system of claim 25, further comprising a storage container coupled to the first rail and / or second rail, the storage container for storing fuel for at least one of the plurality of satellites, mechanical equipment for at least one of the plurality of satellites, and / or electrical equipment for at least one of the plurality of satellites.

27. The system of claim 25, further comprising a robotic arm coupled to the first rail or second rail, the robotic arm being controlled to remove debris along an orbital path of the first and second rails.

28. The system of claim 25, wherein the first rail being formed of a plurality of rail segments.

29. The system of claim 25, wherein the second rail being formed of a plurality of rail segments.

30. The system of claim 25, wherein the first and second rails configured to be deployed in a selected orbital path to control traffic flow of one or more satellites travelling along the selected orbital path; wherein the first rail defines a first travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a first satellite to travel within the first travel lane; and wherein the second rail defines a second travel lane within the orbital path and wherein the thrust / maneuvering control circuitry to control at least a second satellite to travel within the second travel lane.

31. The system of claim 25, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for the at least one of the plurality of satellites to undock the at least one of a plurality of satellites from the first or second rail.

32. The system of claim 25, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of a plurality of satellites to avoid a collision between two or more satellites.

33. The system of claim 25, wherein the thrust / maneuvering control circuitry is further configured to generate thrust and maneuvering commands for at least one of a plurality of satellites dock the one or more satellites to the first or second rail.

34. The system of claim 25, wherein the thrust / maneuvering control circuitry is further configured to schedule docking and / or undocking of at least one of the plurality of satellites based on, at least one of, overall density of satellites within a given orbit, debris field cleanup operations, and / or in response to an emergency scenario associated with at least one of the plurality of satellites.

Images