JPWO2020150242A5 - - Google Patents

Description

PRIORITY CLAIM This application is the filing date of U.S. Provisional Patent Application No. 62/792,779, entitled "Spacecraft Servicing Devices and Related Assemblies, Systems, and Methods," filed January 15, 2019 claims the interests of

Embodiments of the present disclosure relate generally to servicing devices for spacecraft (eg, satellites). In particular, embodiments of the present disclosure relate to work systems having one or more removable work devices (eg, pods or modules), as well as related devices, systems, assemblies, and methods.

Thousands of spacecraft orbit the earth to perform a variety of functions, including, for example, telecommunications, GPS navigation, weather forecasting, and mapping. Like all machines, spacecraft periodically require work to extend the useful life of the spacecraft's functions. Operations may include, for example, repairing components, refueling, orbit raising, holding a stationary position, balancing momentum, or other maintenance. To accomplish this, a working spacecraft may be sent into orbit for docking with a client spacecraft in need of maintenance, and after docking, the client spacecraft may be given a life extension. carry out maintenance and management of Without life-extending maintenance, these spacecraft may become inactive. Typically, replacements are very expensive and lead times can be years.

Various patent documents and patent publications have been issued discussing the operation and related features of such spacecraft, including U.S. Pat. No. 3,508,723; , U.S. Patent No. 4,391,423, U.S. Patent No. 4,588,150, U.S. Patent No. 4,664,344, U.S. Patent No. 4,898,348, U.S. Patent No. 5,005,786 , US Patent No. 5,040,749, US Patent No. 5,094,410, US Patent No. 5,299,764, US Patent No. 5,364,046, US Patent No. 5,372,340 , U.S. Patent No. 5,490,075, U.S. Patent No. 5,511,748, U.S. Patent No. 5,735,488, U.S. Patent No. 5,803,407, U.S. Patent No. 5,806,802 , US Patent No. 6,017,000, US Patent No. 6,299,107, US Patent No. 6,330,987, US Patent No. 6,484,973, US Patent No. 6,523,784 , US Patent No. 6,742,745, US Patent No. 6,843,446, US Patent No. 6,945,500, US Patent No. 6,969,030, US Patent No. 7,070,151 , US Patent No. 7,104,505, US Patent No. 7,207,525, US Patent No. 7,216,833, US Patent No. 7,216,834, US Patent No. 7,240,879 , US Patent No. 7,293,743, US Patent No. 7,370,834, US Patent No. 7,438,264, US Patent No. 7,461,818, US Patent No. 7,484,690 , US Patent No. 7,513,459, US Patent No. 7,513,460, US Patent No. 7,575,199, US Patent No. 7,588,213, US Patent No. 7,611,096 , US Patent No. 7,611,097, US Patent No. 7,624,950, US Patent No. 7,815,149, US Patent No. 7,823,837, US Patent No. 7,828,249 , US Patent No. 7,857,261, US Patent No. 7,861,974, US Patent No. 7,861,975, US Patent No. 7,992,824, US Patent No. 8,006,937 , U.S. Patent No. 8,006,938, U.S. Patent No. 8,016,242, U.S. Patent No. 8,056,864, U.S. Patent No. 8,074,935, U.S. Patent No. 8,181,911 , US Patent No. 8,196,870, US Patent No. 8,205,838, US Patent No. 8,240,613, US Patent No. 8,245,370, US Patent No. 8,333,347 , US Patent No. 8,412,391, US Patent No. 8,448,904, US Patent No. 8,899,527, US Patent No. 9,108,747, US Patent No. 9,302,793 , U.S. Patent No. 9,321,175, and U.S. Patent No. 9,399,295; U.S. Patent Application Publication No. 2004/0026571; , US2007/0228220, US2009/0001221, US2012/0112009, US2012/0325972, US2013/0103193 , US2015/0008290, US2015/0314893, US2016/0039543, and US2016/0039544; EP0541052, EP0741655B1, EP0741655B2, and EP1654159 ; PCT Pub. 2005/110847, PCT Pub. 2005/118394, PCT Pub. 2014/024199, and PCT Pub. 2016/030890; Japan Patent No. JPH01282098; "Automated Rendezvous and Docking of Spacecraft" Fehse, Wigbert, eds., Cambridge University Press, 2003; "On-Orbit Serving Missions: Challenge es and Solutions for Spacecraft Operations, Sellmaier, F.; SpaceOps 2010 Conference, AIAA 2010-2159, 2010; and "Towards a Standardized Grasping and Refueling On-Orbit Servicing for Geo Spacecraft," Medina, Albert. ed., Acta Astronautica 134 1-10, 2017; The In-Flight Technology Demonstration of German's Robotics Approach to Dispose Malfunctioned Satellites,” Reintsema, D.; eds., the disclosures of each of which are incorporated herein by reference in their entireties.

However, highly reliable and rugged working spacecraft that provide versatile working options for the spacecraft can be prohibitively expensive. On the other hand, lower-cost options may not offer the widest variety of working options, nor may they provide the highly reliable and robust working capabilities required in many applications. have a nature.

Embodiments of the present disclosure provide a body configured to be deployed from a carrier spacecraft in an initial non-geosynchronous orbit that remains stationary with respect to the rotation of the earth, and a target spacecraft. ) and at least one spacecraft work component configured to perform at least one work operation on a target spacecraft while coupled to a spacecraft work device; and a docking mechanism for coupling the body to the target spacecraft, the thruster assembly being configured to change at least one of After deployment of the body, it is configured to transport the body from the initial orbit to a geosynchronous orbit.

A body configured to be deployed from a carrier spacecraft in an initial orbit that is not the destination orbit of the spacecraft working device, and coupled to a target spacecraft, according to embodiments of the present disclosure. a spacecraft work device comprising at least one spacecraft work component configured to perform at least one work operation on a target spacecraft; and a docking mechanism for coupling a body to the target spacecraft. Further comprising, the body configured to be transported from the initial orbit to the final destination orbit after deploying the body from the carrier spacecraft, and the docking mechanism configured to hold and position the body relative to the target spacecraft. configured to be coupled to a target spacecraft with the aid of another coupling spacecraft that is connected to the target spacecraft.

An embodiment of the present disclosure is a thruster assembly comprising at least one thruster, the thruster assembly for thrusting from a first orbit to a second spacecraft when the spacecraft working device is not coupled to another spacecraft. a thruster assembly configured to change the orbit of the spacecraft working device up to an orbit of 2 and a body configured to be coupled to the target spacecraft by the carrier spacecraft at a location adjacent the target spacecraft; and at least one spacecraft working component configured to perform at least one work operation on the target spacecraft when the body is coupled to the target spacecraft, the at least one spacecraft working component comprising: The shipwork component includes a thruster assembly that changes at least one of trajectory, velocity, or momentum of the target spacecraft when the body is coupled to the target spacecraft. at least one spacecraft working component and a transmission location remote from the spacecraft working device, further configured to determine at least one of trajectory, velocity, or momentum of the target spacecraft; and a communication device configured to receive data.

Embodiments of the present disclosure further include methods of working with spacecraft. The method comprises deploying the pod in an initial orbit below a geosynchronous orbit; transporting the pod from the initial orbit to a substantially geosynchronous orbit; coupling the pod to a spacecraft in the geosynchronous orbit; and performing at least one spacecraft work operation after being coupled to the spacecraft.

The above summary is not intended to describe each embodiment shown, nor is it intended to describe every implementation of the present disclosure.
The drawings included in this application are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure. The drawings depict only certain embodiments and are not intended to limit the disclosure.

FIG. 1A is a simplified schematic diagram illustrating a system for spacecraft work and a target spacecraft on which work is to be performed, in accordance with one or more embodiments of the present disclosure. FIG. 1B illustrates an embodiment of a fuel tank supply device that may be implemented on one or more devices of the spacecraft working system of FIG. 1A. 1 is a simplified schematic diagram illustrating a spacecraft work device in accordance with one or more embodiments of the present disclosure; FIG. 1 is a simplified schematic diagram illustrating a spacecraft work device in accordance with one or more embodiments of the present disclosure; FIG. [0014] Fig. 5 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [00103] Fig. 13 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [0014] Fig. 5 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [00103] Fig. 13 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [00103] Fig. 13 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [00103] Fig. 13 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [0014] Fig. 5 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [0014] Fig. 5 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; [0014] Fig. 5 illustrates an embodiment of a coupling mechanism in accordance with one or more embodiments of the present disclosure; 1 is a perspective view of a spacecraft work device in accordance with one or more embodiments of the present disclosure; FIG. 1 is a simplified schematic diagram of a mission extension pod in accordance with one or more embodiments of the present disclosure; FIG. 1 is a simplified schematic diagram illustrating a mission extension pod attached to a spacecraft in two propulsion vector orientations, in accordance with one or more embodiments of the present disclosure; FIG. FIG. 4B is another simplified schematic diagram illustrating a mission extension pod attached to a spacecraft in two thruster vector orientations, in accordance with one or more embodiments of the present disclosure; 1 is a simplified schematic diagram illustrating a refeed device of a system for spacecraft work in accordance with one or more embodiments of the present disclosure; FIG. [0014] Fig. 4 illustrates an embodiment of a spacecraft working device having multiple pods coupled to the spacecraft working device in accordance with one or more embodiments of the present disclosure; [0014] Fig. 4 illustrates an embodiment of a spacecraft working device having multiple pods coupled to the spacecraft working device in accordance with one or more embodiments of the present disclosure; [0014] Fig. 4 illustrates an embodiment of a spacecraft working device having multiple pods coupled to the spacecraft working device in accordance with one or more embodiments of the present disclosure; [0014] Fig. 4 illustrates an embodiment of a spacecraft working device having multiple pods coupled to the spacecraft working device in accordance with one or more embodiments of the present disclosure; 1 is a simplified schematic diagram illustrating another configuration of a system for spacecraft work and a target spacecraft on which work is to be performed, in accordance with one or more embodiments of the present disclosure; FIG.

The figures presented herein are not intended to be physical representations of any particular device, assembly, system, or components thereof, but are employed to illustrate illustrative embodiments. 1 is a simply idealized diagram of the Drawings are not necessarily to scale.

The term "substantially" as used herein in reference to a given parameter means that the given parameter, with an insignificant amount of variation, such as within acceptable manufacturing tolerances, Ranges are meant and inclusive as a person skilled in the art would understand a property or condition to be compatible. For example, a substantially matching parameter can be at least about 90% matching, at least about 95% matching, or at least 99% matching. , or at least 100% match.

Embodiments of the present disclosure generally provide spacecraft (e.g., , satellite, or other vehicle) related to working devices. A spacecraft working system, spacecraft working assembly, or spacecraft working device (e.g., spacecraft, vehicle), spacecraft working device (e.g., MEP mother ship (MEPM) or mission robot) One or more deployable spacecraft work devices, pods, or modules (e.g., mission extension pods) initially attached to or later captured by a mission robotic vehicle (MRV) (MEP: mission extension pod) A spacecraft working device can then transfer the pod to/from the client spacecraft A spacecraft working re-supply device can have a Additional pods for shipboard devices can be provided.

Pods (e.g., 1 pod, 5 pods, 6 pods, 10 pods, 15 pods, or more pods provided by the mothership) may be provided to the target spacecraft ( for example, can be individually deployed and/or attached to the spacecraft), thereby providing the spacecraft with life-extending tasks, including, for example, component repair, refueling, orbit raising. or other modifications (e.g., deorbit), repositioning, inclination pull-down, holding stationary position, momentum balancing, momentum adjustment, supply replenishment, provision of new supply or parts, and / or other maintenance is included. In some embodiments, the pods may be utilized for spacecraft speed, placement, and/or orbit adjustments, including stationkeeping, inclination reduction, orbit relocation, and abandonment. In some embodiments, pods may be used to manage momentum and to provide spacecraft attitude control. In some embodiments, pods can supply replacements and additional components. For example, configurations in which pods can be utilized to replace faulty parts, supplement existing parts, and/or add parts, selected features and structures, etc. to the spacecraft. elements (e.g., flight control components, avionics components such as reaction wheels, motor components, communication components, power system components, sensor components, optical components, thermal control components, telemetry components, combinations thereof, etc.). As a further example, a pod may have telemetry features, such as optical devices that measure star positions using photocells or cameras (eg, star trackers). Such devices may be provided on the pod to monitor and/or modify the flight characteristics (eg, attitude) of the spacecraft.

In some embodiments, the spacecraft working device is a robotic spacecraft working device (e.g., one or more end effectors for various tasks) for in-orbit satellite work. deploying one or more of the pods when required to work with one or more robotic arms capable of one or more degrees of freedom, including It can be attached to a spacecraft. For example, a spacecraft working device deploys one or more of the pods to a portion of the spacecraft (e.g., separation ring, engine, external appendage, or any other suitable mechanical device). attachment or coupling structure). In some embodiments, a spacecraft working device can capture one of the pods using a robotic working device. In some embodiments, the spacecraft work device itself may perform some work tasks before, during, and/or after deployment of the pod to the spacecraft.

A spacecraft working device can travel in outer space to or between spacecraft to mount the mission extension pod on the spacecraft when work is required. In some embodiments, a spacecraft work device can attach a pod to a spacecraft and leave the attached pod for work. For example, the pod can be permanently attached to the spacecraft and can effectively be a separate component of the spacecraft, which may or may not be connected to existing systems of the spacecraft. It doesn't have to be. In such embodiments, the pods may be configured to perform work over a selected period of time (e.g., for short periods of time, such as minutes, weeks, months, or years). and/or long hours of work, or a combination thereof). In some embodiments, the spacecraft work device or another similar device can remove the pod or refuel the pod after a selected amount of work. and/or pods can be replaced. For example, a portion of a working system (e.g., a spacecraft working device, or another portion such as the resupply device discussed above) may have one or more consumables (e.g., fuel, gas, parts, etc.) can be revisited to the pod to resupply (eg, replenish, replenish, supplement, etc.). In some embodiments, the spacecraft work device can attach additional devices (eg, tanks) to the pod that have such consumables. In some embodiments, the spacecraft working device is capable of detaching a pod from a spacecraft, resupplying and/or refurbishing a pod, and redoing the pod to the same or another spacecraft. can be worn (eg, pods can be reused).

Once the pod is attached to the spacecraft, it can be activated, including, for example, changing the orientation of the spacecraft (e.g., by changing the trajectory, position, or otherwise orientation of the spacecraft), By varying the velocity (eg, by providing ΔV), track keeping, for example, can be achieved. By imposing a velocity change on the combined mass of the spacecraft and the mission extension pod at an appropriate time and direction, the mission extension pod can, for example, replace the spacecraft's propulsion capabilities (e.g., complete ), or by reducing the fuel consumption rate of the spacecraft required to maintain the desired speed, position, and orbit, the in-orbit life of the spacecraft can be extended. A mission extension pod can provide such velocity changes to the spacecraft according to a schedule provided by data associated with the spacecraft. In some embodiments, the data needed for the maneuver schedule can be pre-programmed into the mission extension pod. In some embodiments, such schedules and other data may be transmitted to the mission extension pod after the pod is launched and/or coupled to the spacecraft. In some embodiments, the pod only provides propulsion (e.g., relatively small propulsion) to the spacecraft without otherwise interacting with other systems or ancillaries of the spacecraft. can be configured to do so. In some embodiments, the pod may be configured to provide a torque about the spacecraft so that the spacecraft can modulate its momentum. In other embodiments, the pod can perform other tasks (e.g., as discussed herein) and/or at least partially with one or more systems or subsystems of the spacecraft. can communicate to

In some embodiments, after the number of pods on the spacecraft work device is reduced or exhausted, by a mission extension pod supply or resupply device (MEPR) , the satellite working system may be configured to supply or re-supply the pod to the spacecraft working device. For example, when the supply of mission extension pods is depleted or depleted, the spacecraft working device can obtain a new supply of pods (e.g., 1 pod, 5 pods, 6 pods). pods, 10 pods, 15 pods, or more pods), thereby continuing to provide life extension work to the prospective spacecraft.

A mission extension pod resupply device (e.g., spacecraft) has multiple pods (e.g., 1, 2, 3, 4, 5 or more pods). For example, a pod resupply device with a mission extension pod may be placed in a geosynchronous orbit (GEO) or other orbit that remains stationary with respect to the rotation of the earth while the spacecraft work device rendezvous to its location. obtain. When the spacecraft working device approaches the mission extension pod resupply device, one or more devices (e.g., the robotic arm of the spacecraft working device) on the spacecraft working device and/or on the pod resupply device ) can relocate the mission extension pod from the mission extension pod resupply device to the spacecraft working device. In other embodiments, the pod resupply device may be configured to travel to the spacecraft work device. In other embodiments, one or more devices on the pod re-supply device may be configured to supply pods to the spacecraft working device or the pod re-supply device, wherein the spacecraft working device It may be configured to be coupled together or otherwise physically connected for the purpose of transporting one or more of the pods. In other embodiments, the pod resupply device drives multiple pods (eg, 1, 2, 4, 8, 16, or more pods) to a different orbit than the spacecraft work device. At this point the pod can travel under its own propulsion and/or power to the spacecraft work device.

In some embodiments, the mission extension pod re-supply device may provide additional supply to or the work of the spacecraft working device. For example, a pod resupply device can provide additional propellant for maneuvering spacecraft work devices when needed. In some embodiments, the pod resupply device performs a refueling operation and/or transfers a tank filled with propellant from the resupply device to the spacecraft task device (e.g., spacecraft task Using one or more robotic arms on one or both of the spacecraft and resupply devices), propellant can be transferred to the spacecraft work device.

In some embodiments, one or both of the spacecraft working device and spacecraft for delivery of mission extension pods, known as ESPAStar, was developed by Northrup Grumman of Falls Church, Va. A spacecraft of the Evolved Expandable Launch Vehicle (EELV) Secondary Payload Adapter (ESPA or ESPA ring) class, such as a spacecraft, or capable of a geosynchronous or alternative orbit that remains geostationary with respect to the appropriate earth rotation may be managed with and/or comprise any other suitable type of device, spacecraft, or launch vehicle.

In some embodiments, one or more devices or components of the satellite working system are transported, for example, from a selected geosynchronous orbit to a geosynchronous graveyard orbit ( For example, in the case of spacecraft working devices and/or mission extension pod resupply devices), or by being discarded in place on the spacecraft (eg, in the case of mission extension pods).

FIG. 1A shows a simplified schematic diagram of a spacecraft working system 10 in which at least a portion of the spacecraft working system 10 approaches a device (eg, another vehicle or spacecraft 20). As such, it can be operated to capture the device, dock to the device, and/or perform operations on the device. However, in some embodiments, the spacecraft working device 100 approaches the spacecraft 20 and one or more modules or pods 102 (e.g., A mission extension pod 102 ) may be configured to be transported to the spacecraft 20 .

Such spacecraft 20 may be in low-earth orbit, intermediate-earth orbit, geosynchronous orbit, beyond geosynchronous orbit, or may be located on Earth or the like. It may be in another orbit of the celestial body. Spacecraft 20 may be used to provide mechanical coupling of pod 102 to spacecraft 20, such as those known and/or implemented in the art of engines, isolation rings, and spacecraft It may have components such as any other type of structure (eg, propulsion device or system 22, fuel tank 24, etc.). For example, the engine may be a liquid apogee engine, solid fuel motor, thruster, or other type of engine or motor. The engine may be located on the zenith deck of spacecraft 20, which in the case of a spacecraft orbiting the Earth, is the spacecraft deck that is located substantially opposite the Earth.

As shown in FIG. 1A, spacecraft working device 100 may be a separate spacecraft designed to work in close proximity to spacecraft 20 . The spacecraft work device 100 can be used to maintain stationary position, orbit climb, modulate momentum (e.g., unload momentum about one or more axes), attitude control, reposition, deorbit, fuel Operations may be facilitated to be performed on spacecraft 20, including resupply, repair, delisting, or other operations that may be performed on-orbit. A spacecraft working device 100 has one or more deployable pods or modules 102 that are initially attached to the spacecraft working device 100 or later captured by the spacecraft working device. A pod 102 may be provided (e.g., deployed and/or attached to) a spacecraft 20 to, for example, repair, replace, and/or add components, refuel, orbit elevation, geostationary position, etc. to perform tasks (e.g., provide life extension tasks to spacecraft 20), including maintaining , balancing momentum, replenishing supplies, providing new supplies, and/or other maintenance. , working parts 103 (eg, only one instance of pod 102 is shown for clarity).

As depicted in FIG. 1A, at least one pod may be provided from spacecraft work device 100 and coupled to spacecraft 20 (e.g., the spacecraft's center of mass) for the purpose of supplying these tasks. or along an axis extending through the center of mass of the spacecraft).

In some embodiments, the spacecraft working system 10 adds pods to the spacecraft working device 100 after, for example, the number of pods 102 on the spacecraft working device 100 is reduced or exhausted. There may be a mission extension pod supply or resupply device 30 configured to supply or resupply 102 . For example, after the supply of mission extension pods 102 is depleted or exhausted, work device 100 may obtain a new supply of pods 102 (e.g., 1 pod, 5 pods, , 10 pods, 15 pods, or more pods), thereby allowing potential spacecraft 20 to continue to provide work for life extension. In some embodiments, the pod resupply device 30 with the mission extension pod 102 may be placed in a geosynchronous orbit (GEO) while the spacecraft work device 100 rendezvous to its location. As spacecraft working device 100 approaches mission extension pod resupply device 30, one or more devices (e.g., rear A robotic arm on spacecraft working device 100 (discussed in ) moves one or more of mission extension pods 102 from mission extension pod resupply device 30 to space. It can be relocated to the shipwork device 100 . In some embodiments, one of the pod resupply device 30 and the spacecraft working device 100 may be configured to hold the other for purposes of relocating the mission extension pod 102 . For example, the spacecraft work device 100 can approach the pod resupply device 30 and can be docked or otherwise engaged with the pod resupply device 30 . Once docked, spacecraft working device 100 can transfer one or more pods 102 from refeed device 30 to spacecraft working device 100 (eg, using a robotic arm). The spacecraft work device 100 can then be disconnected and another pod can be deployed to the other device. In other embodiments, pod resupply device 30 may be configured to travel to spacecraft working device 100 . In other embodiments, one or more devices (eg, robotic arms) on pod resupply device 30 may be configured to deliver pods 102 to spacecraft working device 100 .

One or more spacecraft working devices 100 configured to place, move, and/or mount the pod for the purpose of placing the pod 102 on the target spacecraft 20 Pod 102 can be placed and stored within reach of mechanism 122 (FIG. 2A). This mechanism is configured to secure one or more robotic arms 122, and/or the spacecraft work device 100 to the pod 102, as will be discussed later. Another type of deployment device (eg, a coupling mechanism), such as an extendable and/or expandable boom, similar to the deployed device 160 may be provided. In some embodiments, one or more robotic arms 122 may have one or more degrees of freedom that allow movement of the arms 122 along one or more axes of motion. For example, the arm 122 can in some embodiments comprise an extendable boom (eg, similar to the deployment device 160 discussed below) that can translate along one axis of motion, or A device can be provided that can rotate and/or translate along one or more axes of motion. Optionally, a second mechanism (eg, a second arm, or pod 102 can be moved or Some other device that can be redirected) may be implemented to move the pod 102 within reach of the first mechanism used to mount the pod 102 on the target spacecraft 20. be able to.

For example, pod 102 may be placed on or within the structure of spacecraft work device 100 within reach of a robotic arm. An optional second arm or other device may be used to mount the pod 102 onto the target spacecraft 20 if the reachable range by a single arm is insufficient. is used to move the pod 102 within reach of the .

In some embodiments, the pod 102 may be placed on one or more separable structures within reach of the robotic arm. Once the pod 102 is depleted (eg, completely depleted), the separable structure can be detached from the spacecraft working device 100 . In such embodiments, fuel consumption of spacecraft work device 100 may be reduced for subsequent rendezvous or work activities.

In some embodiments, pod 102 may be carried on another device (eg, pod re-supply device 30 launched with spacecraft work device 100), and then pod 102 may be placed on spacecraft work device 100 after launch. can be transported to For example, the spacecraft working device 100 can be used to pull the pod resupply device 30 to a geosynchronous or other orbit, and then the vehicles can separate. Spacecraft working device 100 may be docked to pod resupply device 30 using a docking mechanism on spacecraft working device 100 and a complementary structure or device on pod resupply device 30 . Once docked, a robotic arm on spacecraft work device 100 can transfer one or more pods 102 from pod resupply device 30 to a storage location on spacecraft work device 100 . . In this way, due to its repeated transits and rendezvous with the target spacecraft 20, the total mass of the spacecraft working device 100 is minimized, thereby minimizing fuel usage over the life cycle of the mission. A pod resupply device 30 may be cooperatively controlled to be placed at a desired orbital location for returning or resupplying the pod 102 by the spacecraft working device 100 .

In some embodiments, as discussed below, pod 102 uses its own propulsion and/or power to change its orbit for the purpose of rendezvous with satellite work device 100. be able to. Once at the desired location, spacecraft working device 100 can capture pod 102 using a docking mechanism, robotic arm, or other functionality present on spacecraft working device 100 . Prior to capture, pod 102 may remain in orbit close to satellite working device 100 or target spacecraft 20 to reduce transit time to target spacecraft 20 .

As discussed above, one portion of system 10 (e.g., pod 102, spacecraft work device 100, and/or resupply device 30) may interact with another portion of system 10 or an external device (e.g., pod 102, spacecraft). (e.g., replenishment, resupply, resupply, resupply, resupply, resupply, resupply, resupply, resupply, resupply, or resupply) of one or more consumables (e.g., fuel, gas, parts, etc.) to the device. completion, etc.). In some embodiments, such supplies may be supplied in additional external tanks attached to the device and/or via replacement (e.g., refueling) procedures using existing components. can be supplied

Spacecraft will generally use propellant (eg, xenon, hydrazine) to maintain positioning and pointing during mission life. When this propellant is exhausted, mission life generally ends. In some embodiments, spacecraft working device 100, pod 102, and/or refueling device 30 (“fueling device”) may be installed in another part of system 10 or in an external device (e.g., pod 102, spacecraft). Additional propellant may be provided to the shipwork device 100 and/or the spacecraft 20 (“target device”). In other embodiments, the fuel supply device is, for example, a tank full of high pressure xenon, hydrazine, helium, nitrogen tetroxide (NTO), low toxicity propellant, combinations thereof, or any other suitable fuel. can serve to supply other fuels or fluids, such as the fuel of the In some embodiments, the propellant or fuel selection may be based on the application of the pod 102 (eg, based on the configuration of the spacecraft 20).

FIG. 1B depicts an embodiment of a fuel tank supply device 140 of a fuel supply device such as may be implemented on one or more devices of system 10 (FIG. 1A). As shown in FIG. 1B, in some embodiments, tubing 142 on fuel tank supply device 140 regulates fuel (eg, high pressure xenon) in tank 141 through regulators 143 (eg, mechanical and/or mechanical). or an electrical regulator). A regulator 143 can control (eg, reduce) the pressure to a level that can be used by the system of the target device. Additional tubing 144 may be positioned downstream of regulator 143 and connected to a mating adapter 145 . A mating adapter 145 may be connected to a target device coupling (eg, a working port valve) that communicates with the target device's fuel. In some embodiments, such a mating adapter 145 of the fuel delivery device is provided with a connecting fitting (e.g., quick disconnect fitting, cooperative working valves, and/or simple forms of mechanical working valves). For example, such mating adapters 145 can include valves (eg, rotary valves or nuts) that open and close flow paths. A mating adapter 145 can have a coupling member (eg, a female coupling member) that can be attached to a coupling device (eg, a valve port) of a target device (eg, a complementary male coupling member). .

In some embodiments, the mating adapter 145 is primed for coupling with a target device by removing the cap or plug so that the target device can attach any structure (e.g., blanket and/or cap or plug). It can be ready by removing. Once primed, a mating adapter 145 can be mechanically attached to the working valves of the target device and one or more valves (e.g., on the target device or on the fuel tank supply device 140). ) can be opened and the pressure can be monitored (eg, pressure can be detected within the system of the target device). This pressure drop may indicate an improper mating between the adapter of the fuel tank supply device 140 and the mating adapter 145 of the fuel tank supply device 140 . Once the connection is confirmed, the valve upstream of the mating adapter 145 can be moved to the open position, causing the tank 141 to supply fuel to the tank of the target device. In embodiments in which the tank 141 of the fuel tank supply device 140 lacks pressure telemetry, the target device's system is designed to determine whether the tank 141 of the fuel tank supply device 140 has reached depletion. It can be used to monitor fuel usage. When the tank 141 of the fuel supply device 140 approaches depletion, the tank 141 of the fuel tank supply device 140 can be taken out of communication by closing valves upstream of the mating adapter 145 and the target device, allowing a new tank to flow. so that it can be connected to a target device (e.g., by replacing the previous tank, can be placed on the same fuel tank supply device 140 or allow the previous tank to remain connected, may be placed on a separate fuel tank supply device). This fuel tank supply device 140 initially includes a working valve 146 for pressurizing the system, mechanical supports for equipment and for attachment to target devices, gripping attachments, and/or Alternatively, it can have a passive thermal control device.

FIG. 2A depicts a simplified schematic diagram of an embodiment of a spacecraft working device 100 (eg, spacecraft working device 100 of FIG. 1A). As shown in FIG. 2A, a spacecraft working device 100 has one or more deployable pods or modules 102 initially attached to the spacecraft working device 100 . Space work device 100 may be a satellite or other spacecraft positioned in orbit around a celestial body.

to capture the pod 102, to deliver the pod 102 to another spacecraft, to attach the pod 102 to another spacecraft, and/or to retrieve the pod 102 to another spacecraft; Spacecraft working device 100 may have a chemical or other type of recoil engine and/or may have an electrically powered propulsion system. For example, spacecraft work device 100 houses one or more thrusters 104 and a chemical and/or electrical propulsion source (e.g., xenon propellant and/or hydrazine propellant for ion thrusters). It may have a power system with a fuel tank 106 ) and a power processing unit 108 . A propulsion system (eg, having thrusters 104) of spacecraft working device 100 may enable spacecraft working device 100 to move in one or more axes of motion (eg, three axes). 6 axes of translation, 3 axes of rotation). Spacecraft work device 100 includes solar array 110 (e.g., removable solar array), battery 112, power conditioning electronics such as power distribution assembly 114, and control subsystem 116 (e.g., command and data processing, thermal control, induction, navigation, and control), communication subsystem 118 (e.g., radio frequency (RF) communication with an associated antenna 120), and accessory tools 121 (e.g., work parts and/or an end effector for a robot arm, discussed later). These components may enable the spacecraft work device 100 to be maneuvered to a location near another spacecraft to be worked on.

To capture the pod 102, to deploy the pod 102 onto another spacecraft, to mount the pod 102 onto another spacecraft, and/or to retrieve the pod 102 to another spacecraft. To do so, the spacecraft working device 100 includes a deployment and/or detachment device (e.g., one or more movable arms (e.g., 1, 2, 3, 4, 5 degrees of freedom). , or a robotic arm 122)) having six degrees of freedom, a lance and/or an extendable deployment device (discussed later) that may be coupled to a portion of the pod 102, such as an internal portion of the engine), which deploys and /or the detachment device includes an accompanying imaging system (eg, camera 124) and control and power system (eg, robot avionics 126 and power supply 128). These devices and components may be utilized to engage (eg, attach to) pod 102 on spacecraft work device 100 . For example, one or more of robotic arms 122 may be coupled to one pod 102 (eg, using end effectors) to move pod 102 into proximity with a target spacecraft. It can be used to attach to the spacecraft and to release the pod 102 after attachment.

In some embodiments, other devices and methods may be utilized to deliver the pod 102 to the spacecraft and/or attach the pod 102 to the spacecraft. For example, the spacecraft working device 100 itself can be oriented with respect to the spacecraft for the purpose of placing a selected pod 102 in contact with the spacecraft, or the spacecraft working device can 100 itself is capable of capturing or otherwise holding a spacecraft while applying pod 102, or pod 102 is capable of controlling and mounting pod 102. Reuse where spacecraft work device 100 is individually controllable with a propulsion unit controller configured to deliver pod 102, which can have one or more on-board systems It is possible to have a possible unit, or it is possible to combine the above.

In some embodiments, the spacecraft working device 100 can deliver the pod 102 to the spacecraft, attach the pod 102 to the spacecraft, and/or Alternatively, pod 102 can be retrieved to space. For example, with one or more pods 102 attached, the spacecraft work device 100 can rendezvous with a target spacecraft (eg, the target spacecraft's location and/or sensor to detect orientation). While the pod 102 is attached to the spacecraft work device 100, the coupling mechanism of the pod 102, discussed later, can be deployed at and engaged with the target spacecraft. Pod 102 may be released from spacecraft work device 100, and any remaining docking procedures for securing pod 102 to the target spacecraft may be completed before, during, and/or after release. .

Spacecraft operations regardless of the particular mechanism or structure utilized to capture pod 102, deploy pod 102, attach pod 102, and/or retrieve pod 102 Device 100 is configured to use one or more portions of spacecraft working device 100 to directly deliver pod 102 to a target spacecraft location (eg, via mechanisms and/or structures). obtain. For example, the spacecraft working device 100 may include a deployment mechanism residing on (eg, on a portion of) the spacecraft working device 100 and/or a structure for deployment (eg, robotic arm 122, extension). pod 102 can be captured, pod 102 deployed, pod 102 attached, and/or Or the pod 102 can be retrieved. In some embodiments, only the deployment mechanisms and/or structures for deployment resident on the spacecraft work device 100 are utilized, while any steering devices (e.g., propulsion devices) on the pod 102 are utilized. is also not used. For example, the pod 102 may be directly operated by the spacecraft work device 100 while the pod 102 is independently maneuvered and/or maneuvered to a location adjacent to the target spacecraft under power or propulsion of the pod 102 itself. not. After being moved into position, the mechanisms and/or structures of spacecraft work device 100 (eg, robotic arm 122, extendable and/or expandable docking mechanisms) and/or the structures of pod 102 (eg, A coupling mechanism, such as deployment device 160, for example, may be utilized to secure pod 102 to the target spacecraft. In some embodiments, pod 102 may be secured to a target spacecraft while pod 102 remains at least partially in contact with spacecraft work device 100 . For example, pod 102 may be released from spacecraft work device 100 once pod 102 is at least partially in contact with (eg, secured to) the target spacecraft.

In some embodiments, spacecraft work device 100 has sensor assemblies such as rendezvous and proximity operations 130 (eg, light detection and ranging 132, infrared sensor 134, and/or visible light sensor 136). . Such components allow spacecraft effects device 100 to monitor and/or detect other objects (eg, pod 102, other spacecraft when work-related functions are being performed, etc.). can be made possible. For example, one or more of these sensors (eg, light detection and ranging 132, infrared sensor 134, and/or visible light sensor 136) deploys pod 102 (FIG. 1A); Spacecraft working device 100 may facilitate rendezvous and proximity operations with respect to target spacecraft 20 (FIG. 1A) for the purposes of loading and/or unloading.

In some embodiments, one or more of the sensors (eg, light detection and ranging 132, infrared sensor 134, and/or visible light sensor 136) are detected by spacecraft working device 100 in target space. It may be possible to detect one or more structures on ship 20 (FIG. 1A). For example, one or more of the sensors of the spacecraft work device 100 may be used for docking of the target spacecraft 20 for the purpose of determining the manner in which the pod 102 is attached to the target spacecraft 20 . Structures (eg, docking, mooring, or docking mechanisms) or other structures (eg, structural features) of target spacecraft 20 may be detected.

In some embodiments, spacecraft working device 100 may be at least partially reconfigured to facilitate operations performed by spacecraft working device 100 . For example, when coupled (eg, docked) to spacecraft 20 (FIG. 1A), device 100 may include various structures and/or components (eg, struts used to dock to spacecraft 20). can be relocated (e.g., can be stowed or moved). These structures and/or components may be detached by one or more tools (eg, robotic arm 122) and placed in a temporary storage location. These structures and/or components may be attached when spacecraft working device 100 is docked to target spacecraft 20 (eg, as well as when performing work).

In some embodiments, structures overlying spacecraft working device 100 may be used to reconfigure other devices (eg, spacecraft). For example, one or more tools (e.g., robotic arm 122) of spacecraft working device 100 remove structure to facilitate stacking secondary payloads above spacecraft working device 100 after launch. can be used. In some embodiments, spacecraft work device 100 (eg, also attached pod 102 (FIG. 1A)) may be attached to an ESPA ring or some other suitable structure. After launch (e.g., in orbit), the robotic arm 122 can detach the pod 102 and relocate it to a storage location, as well as being used during launch disposal or temporary storage. The accessory structure can be attached and detached.

FIG. 2B depicts a simplified schematic diagram of an embodiment of a spacecraft working device 150 that may be substantially similar to spacecraft working device 100 of FIG. As shown, some, most, or all of the components of spacecraft work device 100 may be included. As shown in FIG. 2B, a coupling mechanism for coupling spacecraft working device 150 to other devices (e.g., other spacecraft such as spacecraft 20, pod 102, resupply device 30, etc.). 152 (eg, docking, anchoring, retaining, or other form of attachment mechanism).

As discussed above, once in orbit with the pod 102 as its initial supply, the spacecraft working device 100 will cause the target spacecraft 20 (FIG. 1A) to attach the pod 102. ) to the target spacecraft 20 . In some embodiments, the spacecraft working device 100 determines the optimal position relative to the spacecraft 20 in order to allow the pod 102 to be donned (eg, robotically docked). Additional control techniques can be employed to maintain. This optimal position may or may not be at the center of spacecraft 20 and is a distance selected to provide space for moving pod 102 and robot 122 onto the spacecraft. may be distanced from spacecraft 20 by as much as . Data from the rendezvous sensors can be sent to the robotic control computer on the spacecraft work device 100 so that the machine vision robot motion control algorithms have prior knowledge of the relative position and motion of the two spacecraft. be able to

Figures 2C-2K depict various embodiments of coupling mechanisms according to one or more embodiments of the present disclosure. As shown in FIGS. 2C and 2D, coupling mechanism 152 may provide a spacecraft receiving portion (eg, engine 156) (eg, an engine portion, or mechanical coupling) of at least one of spacecraft 20. An expandable docking mechanism 160 (eg, having a spear shape) configured to be received on any other portion possible). Expandable docking mechanism 160 is guided into position by spacecraft working device 100 (FIG. 2A) alone or by robotic arm guiding the final docking while spacecraft working device 100 is guided into position. will hold its position relative to spacecraft 20 . Once in position, one or more expandable portions may be deployed and allowed to contact receiving portion 156 , thereby securing expandable docking mechanism 160 to spacecraft 20 .

Such an expandable docking mechanism 160 is disclosed, for example, in U.S. patent application Ser. , the entire disclosure of which is incorporated herein by this reference. For example, expandable docking mechanism 160 may be inserted into engine 156 of spacecraft 20 as shown in FIG. 2C. When inserted into engine 156, one or more portions of expandable docking mechanism 1560 may be moved (eg, expanded, extended) to contact engine 156 and expandable. A docking mechanism 160 is secured to engine 156 to secure pod 102 (FIG. 1A) to spacecraft 20 . Before, during, and/or after anchoring, expandable docking mechanism 160 has extension arms that are retracted to position pod 102 (FIG. 1A) closer to spacecraft 20. can have

As shown in FIGS. 2E and 2F, the coupling mechanism 152 is configured to engage a receiving portion 156 of the spacecraft 20 with an expandable and/or retractable docking mechanism 162 (e.g., in the form of a chuck). ) can be provided. Docking mechanism 162 may be guided into position in a manner similar to that described above. Once in position, the docking mechanism 162 can be retracted or extended, thereby securing the extendable docking mechanism 162 to the spacecraft 20 .

As shown in Figures 2G and 2H, the coupling mechanism 152 is a snare docking mechanism 164 (e.g., a plurality of wires, e.g., meshed metal wires, positioned at the opening of the cavity). ) can be provided. A snare-style docking mechanism 164 may be guided into position in a manner similar to that described above. A snare-style docking mechanism 164 is configured to engage receiving portion 156 of spacecraft 20 by allowing receiving portion 156 to enter an opening in the wire. Once in position, the snare docking mechanism 164 moves (e.g., rotates) such that the wire at least partially constrains the opening defined by the wire, thereby allowing the snare to move. A docking mechanism 164 is secured to spacecraft 20 .

As shown in FIGS. 2I and 2J, the coupling mechanism 152 is a clamping docking mechanism 166 (e.g., having a movable member and two fixed members) configured to engage a receiving portion 156 of the spacecraft 20. 3-point clamping mechanism). Docking mechanism 166 may be guided into position in a manner similar to that described above. Once in position, the movable member of docking mechanism 166 can move toward the stationary member, thereby securing expandable docking mechanism 166 to spacecraft 20 .

As shown in FIG. 2K, the coupling mechanism 152 is configured to engage an inflatable clamping docking mechanism 168 (e.g., an outer portion of the receiving portion 156 and/or a receiving portion 156 of the spacecraft 20). or one or more inflatable bags configured to be received on the inner portion). Docking mechanism 168 may be guided into position in a manner similar to that described above. Once in position, an inflatable bag (e.g., an annular bag) or multiple inflatable bags (e.g., two opposing bags) can be inflated, thereby allowing the expandable docking mechanism 168 to attach to the spacecraft. Fixed at 20. In some embodiments, the bag may be filled with a fluid (eg, liquid) that at least partially solidifies to form a rigid connection that is at least partially between the structures.

FIG. 2L is a perspective view of a spacecraft working device 180, which may be similar to the devices described above. As depicted, the spacecraft work device 180 has a body 182 with an ESPA ring around which the pod 102 is coupled. Each pod 102 may have a coupling mechanism 184 for coupling to target spacecraft 20 (FIG. 1A) and optional solar array 186 . Similar to the above, the coupling mechanism 184 may comprise a spear-shaped extendable device configured to be engaged with the engine of the target spacecraft 20 .

Referring to FIG. 1A, in additional embodiments, structural portions (eg, struts or other frame members) of pod 102 may be utilized to dock to spacecraft 20 . For example, a robotic arm or other structure (e.g., a non-robotic method) first determines the geometry and structure of spacecraft 20 and the geometry and structure of spacecraft 20 components (e.g., isolation rings). A pod 102 is placed at a predetermined location according to the object. Spacecraft working device 100 may then dock with spacecraft 20 using the structural portion of pod 102 . Once docking is complete, structural portions of pod 102 can be secured to spacecraft 20 (e.g., by actuating clamps or electromechanically driven via electronic commands through or from the robot interface). by strengthening the bond in other ways via force). A portion of spacecraft working device 100 (eg, a robotic arm) can then release pod 102 and spacecraft working device 100 can be detached from spacecraft 20, attaching pod 102 to spacecraft 20. Leave on (e.g. on an isolation ring).

In additional embodiments, a portion of spacecraft working device 100 (eg, a robotic arm) extends to pod 102 to extend pod 102 to a portion of the spacecraft (eg, an isolation ring of spacecraft 20 or other suitable device). mechanical structure). Electronic commands to pod 102 or spacecraft 20 to activate coupling mechanisms or electromechanical drives on either device are then used to lock pod 102 in place on spacecraft 20. obtain.

Referring to FIG. 2A, in examples where a robotic arm is used to position the pod 102, the robotic arm 122, end effectors, and/or other tools control the zero-gravity contact dynamics between the two vehicles. Techniques associated with the docking mechanism 166 can be employed to minimize this. Such techniques include, but are not limited to, minimizing friction at the contact interface, the time between initial contact and consolidation (e.g., time to complete docking or otherwise bonding). ) and giving some margin to the path. In some embodiments, passive and active first-contact electrostatic discharge (ESD) mitigation techniques are applied to the pod 102 , robotic arm 122 , spacecraft work device 100 , and refeed device 30 . It can be employed in designs to minimize or eliminate ESD on first contact. Such ESD mitigation is described, for example, in U.S. patent application Ser. No. 2003/0002000, the entire disclosure of which is incorporated herein by reference.

Referring to FIG. 1A, when mounting pod 102 onto spacecraft 20, it may be desirable to make the connection between spacecraft work device 100 and spacecraft 20 as simple as possible. be. In some embodiments, during installation of pod 102, spacecraft 20 and spacecraft work device 100 may free-drift together for only a short period of time (eg, seconds to minutes), where this short period of time is At , attachment of pod 102 is established and spacecraft work device 100 releases pod 102 to break the mechanical connection between the two vehicles. The propulsion system of spacecraft working device 100 may then be reactivated and spacecraft working device 100 may retreat to a safe location. Shortly thereafter, the attitude control system of spacecraft 20 may be reactivated, allowing target spacecraft 20 to re-establish its positioning.

1A and 2A, in some embodiments, after installation, the pod 102 can be activated via, for example: ground commands to transceivers within the pod 102, electronic commands from the robotic arm 122. , here for example timers and sensors (such as For example, a break-wire timer or similar sensor) is used. In some embodiments, such sensors may have one or more mechanical limit switches that are activated by the completion of mechanical actions for docking or mounting.

In additional embodiments, pod 102 may be activated via structure incorporated into the interface between spacecraft work device 100 and pod 102 . For example, a portion of the deployment device of the spacecraft work device 100 (eg, a tool drive or end effector on the robotic arm 122) activates the appendage and/or initially deploys the appendage to the pod 102. can assist in deploying on. Such techniques potentially involve the ability of the robotic arm 122 of the spacecraft work device 100 (e.g., robot The use of an end effector on arm 122 simplifies the mechanics of pod 102 . The robotic arm 122 and/or the components and tools of the robotic arm 122 may at least partially perform the in-orbit assembly of the pod 102 . For example, the use of robotic arm 122 for final assembly of appendages to pod 102 simplifies, lightens, and/or reduces the components of pod 102 for launch. It can allow packaging to be low cost.

FIG. 3 depicts a simplified schematic diagram of an embodiment of a pod of spacecraft work device 100 (eg, mission extension pod 102 of FIG. 1A). As shown in FIG. 3, the mission extension pod 102 is one for controlling (eg, directing and moving) the pod 102 and any other structure attached to the main body 201 of the pod 102. Or have multiple devices. For example, pod 102 may have a chemical or other type of recoil engine and/or may have an electrically powered propulsion system. Additionally, pod 102 may have a hybrid propulsion system (eg, any combination of chemical thrusters, electric thrusters, or cold gas thrusters). As depicted, one or more thruster assemblies 200 are attached (eg, movably mounted) to pod 102 using moveable (eg, rotatable) couplings (eg, gimbal 204 and boom 206). can have one or more thrusters 202 (eg, electric propulsion (EP) thrusters). In some embodiments, the positioning of thrusters 202 with respect to main body 201 is determined by one or more characteristics of the spacecraft to which the pod is attached (e.g., size, dimensions, mass, center of mass, combinations thereof, etc.). In some embodiments, the thrusters 202 may achieve relatively low acceleration to minimize or eliminate disturbances caused by propellant moving about within the propellant tank.

Although the embodiment of FIG. 3 shows one thruster assembly 200 on a single boom 206, in other embodiments the pod 102 may have multiple thruster assemblies on multiple booms. (eg, two, three, or more thruster assemblies and associated booms). For example, two thruster assemblies may be provided on two booms, where one thruster assembly is substantially a mirror image of the other thruster assembly. Additionally, in some embodiments, multiple thruster assemblies may be provided on a single boom. In such an embodiment, multiple thrusters may be implemented to achieve sufficient system lifetime throughput capability and to ensure that the desired propulsion level is reached. For example, in embodiments in which pod 102 is configured to move on its own to a particular orbit, the thrusters may be placed in orbit along with subsequent maintenance procedures performed by pod 102 after it is coupled to target spacecraft 20 . It can be selected to implement a lift operation. In some embodiments, one or more thruster assemblies 200 may not be provided on the boom and may be mounted directly on pod 102 . In some embodiments, a single thruster assembly 200 may be used to reposition the spacecraft, hold a stationary position, reduce inclination, adjust momentum, and/or be retired at end of life (EOL). It can be used for work to extend life, including. In some embodiments, each of the plurality of thruster assemblies 200 may be used for all life extension operations or may be separated for different life extension operations. For example, one or more thruster assemblies 200 may be provided on one or more booms for stationary position maintenance tasks, whereas one or more thruster assemblies 200 may be used for orbital repositioning. , tilt angle down, and disposal at EOL.

In some embodiments, antenna 208 may be positioned on thruster assembly 200 . In some embodiments, antenna 208 may be located on a separate deployable boom. In some embodiments, additional solar cells may be placed on thruster boom assembly 200 to generate power.

Pod 102 may have a power and propulsion system 210 having one or more power sources and associated components (eg, where at least a portion of the power system may be an electric propulsion power system). For example, power and propulsion system 210 contains one or more propellant tanks (eg, xenon propellant, or any other suitable propellant for an electrical or chemical propulsion system); It can have thrusters (eg, electronic thrusters) and associated power processing units. A pod 102 may have a solar array 212 and one or more batteries 214 . In some embodiments, the solar array 212 can be rigidly coupled to the main body 201 or movable (e.g., rotatable) with one or more axes of motion to orient the solar array 212 toward the sun. ) may be attached to a coupling device (eg, one or more gimbals 216 or other movable joints and boom 218 that provide movement about one, two, or more axes).

In some embodiments, a gimbaled solar array 212 can have many advantages over similar inflexible arrays. For example, the gimbaled solar array 212 allows the solar array 212 to be detached/spaced from the thrusters of the target spacecraft 20 so that the target spacecraft 20 moves up to the pod 102 solar array. Orbital keeping can be accomplished while minimizing the concern of 20 thruster entrapment. The gimbaled solar array 212 can further thermally decouple the pod 102 from the target spacecraft 20 and improve the effectiveness of the solar array 212 by allowing the sun to track. The increased effectiveness of the gimbaled solar array 212 allows the thrusters of the pod 102 to operate longer and also allows the use of smaller, lighter, and less expensive batteries. Become. A propulsion system that operates longer may facilitate operations on heavy target spacecraft 20 . In some embodiments, a gimbaled solar array 212 may be articulated to an orbiting target 20 in a manner that conserves momentum (e.g., such that no net momentum is imparted).

In some embodiments, the solar array 212 is designed to maximize the power generation of the solar array 212, thereby minimizing the size of the solar array 212 and the battery. Logic stored in the pod 102 can be utilized to track the sun while performing. In some embodiments, for example, for purposes of simplifying the mechanical design, and for spacecraft array shadowing, thruster plumes impacting pods 102 and/or spacecraft 20, Movement of the solar array 212 is restricted in order to eliminate or minimize sensors or antennas from interfering with the pod 102 and/or spacecraft 20 or creating other system constraints. you can In some embodiments, solar array 212 can have two separate wings with one or two axes of motion. In some embodiments, the gimbaled solar array 212 can have one axis of motion configured to resist rotation of the pod 102 .

In some embodiments, the solar array 212 is oriented to track the sun to provide sufficient power to the propulsion system, and as a result is attached to the host spacecraft 20 or work spacecraft 100. Continuous electrical propulsion for trajectory correction of the pod 102 is enabled in the absence of the pod 102 .

Embodiments of pod 102 use low power (e.g., electric) propulsion systems such as gridded ion thrusters, Hall effect thrusters, colloidal/field effect thrusters, arcjets, and resistjets. Tasks for spacecraft can thereby be provided for spacecraft vehicle 20 (FIG. 1A) in a relatively small physical package and low footprint. Such an electric propulsion system can produce the required amount of propulsion over a selected period of time (e.g., 24 hour 2 injections), where each propulsion lasts for a selected time. In some embodiments, the pod 102 may be placed on the zenith-facing side of the spacecraft and the solar array 212 of the pod 102 (e.g., opposite the Earth), thereby providing power for at least 12 hours of the day. Sunlight can be received without being disturbed. In some embodiments, one thruster burn may occur while the solar array 212 of the pod 102 is fully illuminated, whereas the solar array 212 of the pod 102 is completely obscured by the spacecraft body. A second thruster injection is performed in between.

In some embodiments, each thruster firing during a 24-hour period may occur while the body of spacecraft 20 obscures solar array 212 of pod 102 . In some embodiments, each thruster firing during a 24-hour period may occur while the solar arrays 202 of the pods 102 are fully illuminated. A battery (eg, a battery 214, such as a lithium-ion battery) may be used to store energy during times when the pod 102 is illuminated by the sun, and the battery 214 may be used to store energy for the pod 102 during times when the pod 102 is not exposed to sunlight. It can be sized to support the power of the bus power draw as well as thruster firing. In some embodiments, thruster firing is performed using chemical thrusters.

In some embodiments, propellant in power and propulsion system 210 of pod 102 is required to maintain stationary position (e.g., spacecraft 20 (FIG. 1A) of spacecraft 20 (FIG. 1A) for a selected period of time (e.g., at least multiple years). (e.g., about 25 kg, 50 kg, 100 kg, 150 kg, or more) to support (eg, about 25 kg, 50 kg, 100 kg, 150 kg, or more). In some embodiments, propellant fuel facilitates delivery from the initial launch insertion orbit of pod 102 to its intended trajectory using pod 102's power system and/or propulsion system. can have an additional amount of propellant to The pod 102 may be filled with propellant prior to launch, so that no propellant transfer is required once in orbit. If spacecraft 20 needs to be relocated to a different orbital location for the continuation of its operational life or is nearing the end of its operational life, for extended operational life or for disposal at end of life. In order to move spacecraft 20 to different orbits, to different orbital positions, or a combination thereof, the propulsion schedule and position of pods 102 effect velocity changes in the direction of spacecraft 20's orbital velocity. so that it can be adjusted.

In some embodiments, fuel or propellant in pod 102 may be utilized to perform work on spacecraft 20 without relying on one or more systems of spacecraft 20 . For example, only propellant in pod 102 may be utilized to perform tasks on spacecraft 20 (eg, maneuver and/or adjust at least one momentum, including the attitude of spacecraft 20).

Referring to FIGS. 1A and 3, in some embodiments, fuel tanks 24 of spacecraft 20 may be bypassed (eg, not utilized) to perform operations on spacecraft 20 . For example, the propellant for pod 102 (eg, supplied from tank 141 in a configuration similar to that shown in FIG. 1B or supplied from the tank of propulsion system 210 of pod 102) may 20 (bypassing the fuel tanks 24 of 20) into a portion of the propulsion system 22 of the target spacecraft 20 (eg, directly). In such an embodiment, pod 102 may be used to perform work on spacecraft 20 without transferring (eg, refueling) propellant to tanks 24 of spacecraft 20 (eg, via a refueling procedure). A propellant may be utilized. For example, the propellant of pod 102 may be in communication with a portion of the fuel system of spacecraft 20 (eg, may be in fluid communication via coupling mechanism 152, mating adapter 145 (FIG. 1B), etc.). In some embodiments, such existing connections may exist on spacecraft 20 . In some embodiments, one or both of spacecraft work device 100 and pod 102 may be mounted on spacecraft 20 at least partially at a connection.

Propellant from the pod 102 may be transferred into the propellant system 22 of the target spacecraft 20 to perform work on the spacecraft 20 (e.g., using one or more thrusters of the propellant system 22, for example). steering and/or adjustment of at least one of the trajectory, velocity, or momentum of spacecraft 20).

In some embodiments, pods 102 may not have propulsion devices to independently move pods 102 .
In some embodiments, the pod 102 can have a relatively small total mass, such as less than 700 kilograms (kg) (eg, less than 600 kg, less than 500 kg, less than 400 kg, less than 350 kg, less than 300 kg, less than 200 kg, less than 100 kg, or less).

In some embodiments, pod 102 is configured to remain permanently on spacecraft 20 and not be retrieved or replaced. In some embodiments, pod 102 may be detached from spacecraft 20 and used on another client spacecraft. In some embodiments, pod 102 may be detached from spacecraft 20 , refueled by spacecraft working device 100 or resupply device 30 , and reattached to spacecraft 20 . In some embodiments, the pod 102 can be detached from the client spacecraft 20, and the pod's trajectory modified for subsequent rendezvous with and capture by the spacecraft working device 100. The propulsion system of the pod 102 can be utilized for this purpose.

A power controller (eg, a single circuit board power controller 220) and a flight controller (eg, a single a single circuit board avionics controller 222). In some embodiments, redundant devices (eg, circuit cards, avionics, thrusters, sensors, actuators, or other components) are installed in pod 102 to improve pod 102 reliability, longevity, and/or throughput. can be included in

Pod 102 may have a communication subsystem 224 (eg, radio frequency (RF)) that communicates or is in communication with antenna 208 and transceiver (XCVR). The communication subsystem 224 of the pod 102 may be designed to operate with commercial communication services that use intermittent contact rather than requiring continuous contact. In some embodiments, one or more additional antennas are mounted on the pod 102 depicted in FIG. 3 for the purpose of establishing omnidirectional communication coverage with the pod 102. or contained at multiple suitable locations. In this context, coverage may be established when the boom is oriented to propel in one direction when the boom antenna is not pointing toward the earth. In some embodiments, such as when pod 102 is in free flight and using on-boom thrusters 202 to correct the trajectory of pod 102, refeed device 30 and host spacecraft 20 , or one or more additional antennas provide a communication link to pod 102 when not connected to satellite work device 100 .

In some embodiments, a communication device (eg, communication subsystem 224) of pod 102 is associated with at least one of the trajectory or velocity of target spacecraft 20 (FIG. 1A) (eg, the momentum of spacecraft 20). ) can receive data. Such data may be transmitted or otherwise communicated (e.g., directly or indirectly) from a location remote from pod 102 to pod 102 through one or more communication channels. typically via ground stations, satellite relays, direct transmissions, and/or direct electrical connections from the target spacecraft 20, etc.). Such data may include calculations for associated jetting and/or the system of pod 102 may perform calculations for jetting based on the data. In some embodiments, telemetry data may be provided from target spacecraft 20 to pod 102 either directly or indirectly via a ground station (eg, via a radio frequency link). In some embodiments, telemetry data may be provided to pod 102 directly or indirectly from one or both of target spacecraft 20 and spacecraft work device 100, or from a ground station. .

In some embodiments, telemetry data may be updated at selected intervals within the closed loop system, and subsequent injections may be calculated based on the updated data.
In some embodiments, a predetermined firing schedule may be provided to pod 102 or another portion of system 10 .

In some embodiments, pod 102 incorporates onboard functionality including any suitable technology for determining the range, position, and/or velocity of pod 102 while in orbit. In some embodiments, the communication subsystem 224 of the pod 102 can provide ranging capabilities so that the orbital location of the pod 102 can be determined using standard ranging techniques with ground systems. can be accurately determined by In some embodiments, pod 102 is controlled whether pod 102 is in free flight, attached to satellite work device 100 , or attached to host spacecraft 20 . An on-board GPS transponder can be incorporated that provides accurate orbital location and velocity. In some embodiments, pod 102 may utilize optical trajectory determination (eg, via a camera or other suitable device). In some embodiments, trajectory range data, position data, and/or velocity data, via communications subsystem 224, are used by an operator (e.g., a work personnel and/or computers) on the ground. In some embodiments, a computer on board pod 102 uses the orbital position and velocity data to calculate a new thruster firing schedule. In some embodiments, ground-based or pod-calculated thruster firing schedules may be used to modify the pod's trajectory when attached to the host spacecraft 20 for purposes of life extension or trajectory correction. . In some embodiments, a ground-based or pod-calculated thruster firing schedule is used to correct the pod's trajectory when not attached to the host spacecraft 20 or satellite work device 100 .

In some embodiments, the pod 102 is updated on the ground for the purpose of calculating thruster firing schedules that are used to correct the pod's position and orientation relative to another object in orbit. The trajectory position data generated on-board and the velocity data generated on-board can be used in combination with data generated by sensors on the pod 102 . In various embodiments, the pod 102 can rendezvous with the satellite working device 100, avoid collision with another orbiting object, or can Performing stationkeeping for stationary position keeping relative to another object, and host spacecraft relative to one or more other objects in orbit when attached to host spacecraft 20 It can modify its position or orientation with respect to another object in its trajectory for the purpose of enforcing 20 stationary position retention.

In some embodiments, pod 102 has any independent system for determining telemetry data (eg, velocity, altitude, momentum, position, trajectory, etc.) of pod 102 and/or target spacecraft 20 . not, it may be necessary to rely on external sources for such information (eg, target spacecraft 20, ground station, working mothership device 100).

A pod 102 can store telemetry data for a period of time (eg, 8 to 12 hours) and this data when polled based on a selected schedule (eg, twice or three times a day). can be returned to the communication network. The overall data set may be relatively small, allowing relatively short contact times, thereby providing a low cost footprint in operating a large number of pods 102 over a multi-year period. do. In some embodiments, pod 102 may be located on the non-Earth-facing side of target spacecraft 20 (FIG. 1A). Transceiver antennas 208 may be positioned on the same boom carrying thruster assemblies 200 to provide line-of-sight to ground station antennas and/or to orbiting communications services, thereby providing clear line of sight is obtained. Given the geosynchronous orbital range and the inherently low power components of pod 102, along with the gain antenna 208 being relatively reasonable, pod 102 is capable of relatively low data rates (e.g., Transfer and return data at less than 1 kb/sec, less than a few kb/sec, etc.). Thus, the pod 102 can receive a limited set of commands to adjust its propulsion schedule and boom pointing to comply with the adjustments specified by the spacecraft operator for the spacecraft 20 from Earth.

In some embodiments, one or more portions (e.g., pod 102) of system 10 (FIG. 1A) can utilize flexible frequency transceivers that are attached to spacecraft 20. An associated ground station and pod 20 may be enabled to communicate. By using flexible frequency transceivers and using existing ground systems for spacecraft 20, pod 102 can provide command and telemetry between pod 102 and ground stations for spacecraft 20. No additional periodic agency licensing or third party work may be required in establishing connectivity. This allows spacecraft 20 operators to exercise control over pod 102 with relatively little additional investment and with little or no periodic disclosure or licensing. (e.g. full control) can be established. Considering that the market base of target spacecraft 20 includes a relatively large number of spacecraft 20 that utilize C-band or Ku-band RF frequencies for communication, the pod 102 to be launched should: It may be configured with a C-band or Ku-band transceiver. Pre-launch coordination can establish the proportion of pods 102 equipped with C-band-based or Ku-band-based communication systems to be launched with initial capability or launched in resupply spacecraft. If target spacecraft 20 does not utilize C-band or Ku-band communications, pod 102 may be configured to implement a type of communication system that substantially matches that of target spacecraft 20; Alternatively, C-band or Ku-band pods 102 may be utilized with target spacecraft 20 having different types of communication systems. In some embodiments, the pod 102 can store its telemetry data for a selected period of time (eg, 8 to 12 hours) and poll (eg, twice or three times a day). Sometimes this data can be returned to the communication network.

In some embodiments, the frequency of the flexible frequency transceiver may be modified based on the in-orbit target spacecraft 20 (e.g., one or more of the frequency bands utilized by the target spacecraft 20 that have not yet been used). A flexible frequency transceiver may allow the pod 102 to be coupled to a variety of target spacecraft 20 because of the utilization of the available portion. In some embodiments, a flexible frequency transceiver included in pod 102 enables frequency interference avoidance between multiple nearby pods and/or pod 102 and other nearby spacecraft. Such features allow pod 102 to provide efficient non-interfering communication with the ground when pod 102 is not attached to either satellite working device 100, resupply device 30, or host spacecraft 20. allow to maintain.

In some embodiments, an inter-space command and telemetry link between the pod 102 and the spacecraft work device 100 is used by the spacecraft work device 100 to connect the pod 102 to the spacecraft 20 ground systems. can be implemented to take advantage of high gain and power. In some embodiments, this technique may be employed when spacecraft work device 100 is in close proximity to pod 102 and/or due to the schedule of thruster firings of pod 102, an occasional May be employed when spacecraft working device 100 may be installed for long term operation only when adjustments may be required (e.g., adjustments may be performed weekly or may be performed monthly). or at longer intervals).

In some embodiments, the communication system of pod 102 can use transceivers designed to take advantage of the proximity of the antenna of pod 102 to the uplink antenna of spacecraft 20, which transmits spread spectrum telemetry signals from pod 102 into spacecraft 20's uplink. This signal then receives a high gain boost by the communication system of spacecraft 20, thereby transmitting telemetry data from pod 102 to the ground.

Various communication systems within the pod 102 disclosed herein can enable near real-time monitoring of the function of the pod 102 and the achievements achieved by the pod 102, here in a geosynchronous orbit. Only the speed of light from Earth to Earth causes time lag. Such a configuration may allow pod 102 to perform multiple functions (eg, such as those described above), where these functions may transmit performance data back to the ground station. In addition, software within the ground station as well as within the target spacecraft 20 or pod 102 can be utilized to "close the loop" with a time lag of the speed of light so that the pod 102 can be used to control the target spacecraft 20. Data from 102 or target spacecraft 20 can be delivered into software associated with target spacecraft 20 or pod 102 . In some embodiments, pod 102 may not need to communicate directly with spacecraft 20 that host pod 102; good. In such an embodiment, it is possible to "close the loop" for complex functions that may be implemented in the manner in which pod 102 performs work relative to the spacecraft. For example, this complex function may include ground-based software using telemetry data from the spacecraft 20 or gimbal control logic in the pod's software to power the spacecraft 20 using the thruster assemblies 200 of the pod 102 . The ability to manage 3-axis momentum may be included.

In order to deploy and mount the pod 102 on another spacecraft 20 (FIG. 1A), the pod 102 is docked to a mounting structure configured to be attached to the spacecraft 20 (eg, the target spacecraft 20). moored to the target spacecraft 20; attached to the target spacecraft 20; holding the target spacecraft 20; or combinations thereof. mechanism 226) and/or one or more coupling structures (eg, gripping mechanism 228) that can be engaged by a structure (eg, robotic arm 122) of spacecraft work device 100 (FIG. 2A). be able to. A coupling mechanism 226 may be movably mounted on the main body 201 (eg, using a gimbal 230).

In some embodiments, the thruster assemblies 200 of the pod 102 may be arranged on a multi-axis actuator system (eg, defined by multiple gimbals and/or translational or rotational devices). For example, gimbals 204 may be configured to move thruster assembly 200 in a first axis, and gimbals 205 may move thruster assembly 200 in a second axis that is transverse to the first axis. It can be configured to move. In some embodiments, gimbals 204 , 205 may be arranged at thruster assembly 200 . In some embodiments, gimbals 204, 205 may be separated by a boom. Pod 102 may have a third gimbal 230 for positioning gimbals 204, 205 relative to the spacecraft body (eg, rotating main body 201 with respect to spacecraft 20 (FIG. 1A)). In some embodiments, pod 102 can have a third gimbal 230 near gimbal 204 (eg, between main body 201 and boom 206). Such a third gimbal 230 can work in conjunction with gimbals 204, 205 to provide three degrees of freedom (eg, three rotational degrees of freedom).

In some embodiments, gripping mechanism 228 is separated from main body 201 by one or more structures 232 to facilitate coupling to robotic arm 122 of spacecraft work device 100 (FIG. 2A). can be spaced apart.

Pod 102 may have features that are utilized to secure pod 102 to spacecraft work device 100 (FIG. 2A). For example, pod 102 can have a containment mechanism 234 coupled to a portion of spacecraft work device 100 (eg, which can be spaced apart from main body 201 by structure 232). In other embodiments, one or more of the existing structures described above (e.g., coupling mechanism 226 and/or gripping mechanism 228), or another structure, attaches pod 102 to a spacecraft. It can be used to secure to working device 100 .

As discussed above, pod 102, for example, while uncoupled (e.g., untethered) from the control system of spacecraft 20, effects changes in orbital velocity for spacecraft 20 (FIG. 1A). (eg, hold static position, reposition, discard at EOL). In other words, only pod 102 can change the path (eg, trajectory) of spacecraft 20 while attached to spacecraft 20 but not coupled to spacecraft 20's control system. Velocity change is achieved by thrusters 202 (e.g., ion thrusters, Hall current thrusters, gridded ion thrusters, Hall effect thrusters, or any other suitable type of electrical or chemical thrusters that provide any level of thrust). can be brought down.

In some embodiments, as discussed above, pod 102 is at least partially coupled to spacecraft 20 (FIG. 1A) (e.g., to the outside of spacecraft 20) in an auxiliary fuel tank (e.g., high pressure fuel tank). xenon, hydrazine, helium, nitrogen tetroxide (NTO), low toxicity propellant, combinations thereof, or any other suitable fuel). For example, pod 102 may have one or more of such tanks within power and propulsion system 210 . In other embodiments, as discussed below, pod 102 may include only fuel tanks with associated components configured to attach the tanks to spacecraft 20 and to communicate the tanks with the spacecraft. .

In some embodiments, the pod 102 can comprise substantially only the auxiliary tank system and may have most or none of the above components. you can Such an auxiliary tank system pod 102 initially includes working valves to pressurize the system, mechanical supports for equipment and for attachment to the spacecraft, gripping attachments, and /or may have a passive thermal control device. In some embodiments, a deployment device (e.g., a robotic arm) may be used to place the auxiliary tank system pod 102 at its destination, the destination being a tank host or a tank host. can be cooperatively designed so that The target spacecraft 20 for this transfer tank system pod 102 may have cooperatively designed interfaces for gas and fluid transfer, or the spacecraft 20 does not have such interfaces. If so, the auxiliary tank pod 102 may have an interface configured to accommodate various sizes and configurations of attachments on this spacecraft 20 .

FIG. 4 is a simplified illustration of pod 102 attached to spacecraft 20 in first configuration 300 with first propulsion vector orientation 301 and in second configuration 302 with second propulsion vector orientation 303 1 is a simplified schematic diagram; FIG. 3 and 4, gimbals 204, 205, 230 provide a selected number of degrees of freedom (e.g., 2 degrees of freedom, 3 degrees of freedom) for directing the thrust vector through spacecraft 20's center of mass. degree) can be provided. Propulsion is based on the initial position of the spacecraft 20 in orbit, on command (e.g., from a remote ground station) and/or on a schedule (e.g., a predetermined schedule) and/or actively delivered to the pod 102. Schedule transmitted) can be caused to reduce or even eliminate the load in maintaining a stationary position and in removing momentum from the subsystems of the spacecraft 20 . In some embodiments, the thrust magnitude and/or thrust vector may be transmitted to pod 102 via a communication link to pod 102 on any desired schedule.

As shown in a first configuration 300 (eg, 3 rotational degrees of freedom) of gimbals 204, 205, 230 that achieves a first thrust vector orientation 301, thrust may be applied primarily in the south direction, i.e. It can be applied in a direction that is non-perpendicular to the spacecraft orbit direction. Similarly, as shown in a second configuration 032 of gimbals 204, 205, 230 that achieves a second thrust vector orientation 303, thrust may be applied primarily in the north direction, or in the spacecraft orbit direction can be added in a direction perpendicular to As shown in FIG. 4, each configuration can have propulsion vector components in the positive and negative directions of orbital velocity. As shown in FIG. 5, the propulsion vector in each configuration (eg, a south facing configuration and a north facing configuration) can also have a significant magnitude component in the radial direction of the spacecraft's orbit. Subtle changes in thruster vectors and burn durations by command (e.g., from a remote ground station) and/or schedules (e.g., predetermined schedules and/or schedules actively transmitted to pods 102) may result in subsequent , is used to perform stationary position maintenance as well as momentum adjustment of the spacecraft 20 . In some embodiments, a propulsion vector may be applied at various locations around the spacecraft at various times while in orbit, thereby controlling the orbital elements of the spacecraft and controlling the momentum of the spacecraft. Optimize management.

This additional propulsion from pod 102 can reduce the rate of propellant consumption from spacecraft 20 by, for example, more than 90% and up to 100%, thereby increasing spacecraft 20 mission life. It works like a prolongation.

Considering that in general propulsion cannot be provided to completely eliminate drift in the orbital elements of spacecraft 20 in one firing duration (i.e., firing), each single thruster firing duration Over time, the pod 102 can induce a slight directional velocity relative to the spacecraft 20 in one or more orbital directions (e.g., radial, vertical, non-perpendicular, plane of orbit). and even through combining multiple activation durations, control of all orbital elements of spacecraft 20 can be achieved. For example, for selected intervals in one orbital cycle (e.g., two 12-hour durations in a day) and for durations of 1 week, 2 weeks, 3 weeks, 1 month, or longer A propulsion schedule for pods 102 may be planned for various orbits. Such schedules can be implemented to combine thrust burns with attendant gimbal angles, thereby causing velocity changes that control some or all orbital elements, and even velocity changes. Adjust spacecraft momentum with change or independently of speed change.

FIG. 5 shows pod 102 (e.g., FIG. 4 provides another simplified schematic view (rotated 90 degrees from the view of FIG. 4). 3 and 5, gimbals 204 , 205 can provide two degrees of freedom for directing thrust vectors 305 , 307 through center of mass 158 of spacecraft 20 . As depicted, a propulsion schedule for pods 102 is planned for two periods of 12 hour intervals in a day (or for any interval that provides desired results for target spacecraft 20). can be Such a schedule can be implemented to combine thrust burns 305, 307, thereby causing velocity changes that can cancel each other out or be used to control the eccentricity of the spacecraft's orbit. be done.

In some embodiments, propulsion commands and/or schedules may be formulated and communicated to pod 102 to establish a desired trajectory, position, orbit for spacecraft 20 based, at least in part, on spacecraft 20 characteristics. , and/or speed.

In some embodiments, the coupling portion 310 of the pod 102 (eg, including the docking mechanism, such as the expandable docking mechanism 160 discussed above) can have a movable (eg, rotatable) joint. . For example, rotatable coupling portion 310 may secure pod 102 to target spacecraft 20 while allowing pod 102 to be rotated with respect to target spacecraft 20 (e.g., to rotate engine 314 of the target spacecraft). by welding to one part). Such a configuration allows for degrees of freedom of the thruster boom arm 312 (e.g., eliminates the need for a separate movable joint such as the third gimbal 230 (FIG. 3), as well as two or more eliminates the need for a thruster gimbal assembly).

FIG. 6 is a simplified schematic diagram of a refeed device of a spacecraft working system (eg, refeed device 30 of spacecraft working system 10 (FIG. 1A)). As shown in FIG. 6, refeeding device 30 can have multiple pods 102 attached to or housed within structure 400 (eg, an ESPA ring). In some embodiments, each pod 102 can have a respective attachment mechanism 401 for coupling to structure 400 . Structure 400 can have multiple coupling devices. These are, for example, a first coupling device 402 and a second coupling device 404 for connection to one of the payloads of the launch vehicle or for connection to the launch vehicle itself. The structure 400 includes a bus 406 comprising one or more spacecraft systems for controlling the re-supply device 30, monitoring the re-supply device 30, powering the re-supply device 30, etc. can have Structure 400 can have a gripping structure 408 configured to be coupled to another portion of system 10 (FIG. 1A) (eg, spacecraft work device 100 (FIG. 2A)). For example, the gripping structure 408 can comprise a structure to which the robotic arm 122 of the spacecraft work device 100 can be coupled (FIG. 2A). In some embodiments, the structure of the refeed device 30 can have an isolation ring and/or a similar structure of a spacecraft engine (e.g., a structure having a similar shape and/or configuration), which As a result, the spacecraft work device 100 can be docked to them.

In some embodiments, the structure of the refeed device 30 may be entirely passive (eg, an ESPA ring without an active spacecraft bus system 406 or gripping structure 408). In such embodiments, the pod 102 may be released from the refeed device 30 while in some orbit that is not the orbit of the spacecraft work device 100 . Pods 102 cannot receive any power, thermal, or data services from re-provisioning device 30 . For example, pod 102 may be powered before or during launch, or may not be powered until released from refeed device 30 .

7-10 depict various embodiments of a spacecraft working device having multiple pods coupled to the spacecraft working device, according to one or more embodiments of the present disclosure. As shown in FIG. 7, a spacecraft working device 500 may be defined by one or more annular structures 502 (eg, two ESPA rings axially stacked on top of each other). Pods 102 may be coupled around annular structure 502 (eg, as a stack of at least two pods 102). For example, a pod 102 may be coupled to each port defined around annular structure 502 . A tool (eg, robotic arm 506) may be coupled to an annular feature of one of annular structures 502 (eg, may be coupled to a radially extending surface on one side of annular structure 502).

As shown in FIG. 8, a spacecraft work device 500 can have different configurations of pods 102 coupled around an annular structure 502 . For example, a pod 102 may be coupled to each port defined around annular structure 502 . A second row of pods 102 may be coupled to each pod 102 positioned next to (eg, adjacent to and/or coupled to) the annular structure 502 . Another set of pods 102 may be disposed between (eg, coupled to) two sets of pods 102 extending from annular structure 502 . In some embodiments, a selected amount of clearance may be provided between pods 102 (eg, including no clearance). In some embodiments, the outermost pod 102 is positioned within, extends up to, or exceeds the diameter of a portion of the launch vehicle (e.g., payload fairing). can be configured to extend through the

As shown in FIG. 9, a spacecraft work device 500 can have different configurations of pods 102 coupled around an annular structure 502 . For example, a pod 102 may be coupled to each port defined around annular structure 502, but spaced from each port. A second row of pods 102 may be positioned adjacent (eg, coupled to) each pod 102 positioned next to the annular structure 502 . Another set of pods 102 may be disposed between (eg, coupled to) two sets of pods 102 extending from annular structure 502 .

As shown in FIG. 10, a spacecraft work device 500 can have different configurations of pods 102 coupled around an annular structure 502 . For example, a selected amount of pods 102 (eg, three pods 102) may be coupled to each port defined around annular structure 502. FIG. A second row of pods 102 may be positioned adjacent (eg, coupled to) each pod 102 positioned next to the annular structure 502 . Another set of pods 102 may be positioned (eg, coupled) on either side of each pod 102 positioned next to annular structure 502 .

FIG. 11 depicts another configuration of spacecraft working device 10 that may be similar to the configuration discussed above and may include various structural parts and operations of the structure discussed above. However, the configuration of FIG. 11 may be deployed in orbit (e.g., a carrier that may be similar or the same as spacecraft work device 100 and/or resupply device 30 discussed above). spacecraft or launch spacecraft 50 or structure), as transported to the target spacecraft 20 (eg, under power of the pod 102 or by another spacecraft), and then to the target spacecraft. 20 may have one or more free-flying pods 102 configured (eg, by being coupled to the target spacecraft 20).

As shown in FIG. 11, system 10 places one or more pods 102 in a first orbit different from (eg, lower than) the desired final orbit, such as a substantially geosynchronous orbit, for example. may have a hostship or transport ship (eg, carrier spacecraft 50) that delivers to the initial orbit of For example, the initial orbit may be partially surrounded by a geosynchronous orbit or may be within a geosynchronous orbit (e.g., the majority of the initial orbit is closer to the Earth than the majority of the geosynchronous orbit). ). In some embodiments, the initial orbit may include a low earth orbit (LEO), a medium earth orbit (MEO), a geostationary orbit, a cislunar orbit, or other orbit. .

As discussed above, in some embodiments, pod 102 may have a propulsion system for independent movement (e.g., from carrier spacecraft 50 to proximate target spacecraft 20). to a location or to another spacecraft configured to deliver pod 102 to target spacecraft 20). In other embodiments, pod 102 may not have its own propulsion system entirely or may have no propulsion system for moving pod 102 independently of another spacecraft (e.g., (if all propulsion to pod 102 is for adjusting the trajectory of target spacecraft 20 and not for independent movement).

In some embodiments, pod 102 can utilize on-board features of pod 102 to correct the trajectory of pod 102 after release of pod 102 from carrier spacecraft 50 (e.g., , as described above or below), where pod 102 is now at The same spacecraft or another spacecraft (e.g., satellite working device 100, carrier spacecraft 50, resupply spacecraft 30) located closer to target spacecraft 20 (e.g., closer to geosynchronous orbit). ) is prepositioned to be captured by In embodiments in which pod 102 does not have a system or device for prepositioning, another spacecraft (eg, spacecraft working device 100 or resupply device 30) retrieves pod 102 from the initial orbit. Pod 102 can be transported to a substantially geosynchronous orbit.

In some embodiments, prepositioning of pod 102 may be performed in one or more of the following ways: pod 102 ( Placement of pods in general locations where they can be collected (e.g., substantially simultaneously); no frequency utilization constraints and thus low probability of collision with other resident space objects or debris and/or minimizing orbital changes of the satellite working device 100 in the process from capture of the pod 102 to attachment of the pod 102 to the client spacecraft 20; A technique for pre-positioning close to the intended client spacecraft 20 so as to do so.

In some embodiments, pods 102 may be utilized to deliver payloads to satellite work devices 100 . Prior to launch, one or more pods 102 are attached to or integrated into pods 102 intended to update or augment the utilitarian functionality of satellite work device 100 . It can have multiple payloads 101 (eg, robotic arms). In some embodiments, the pod 102 may be separate from the carrier spacecraft 50 and may modify its trajectory for eventual capture by the satellite working device 100, allowing the satellite working device 100 to The payload 101 can be captured by a satellite work device 100 and removed by a robotic function included in the satellite work device 100 . In this case, a pod 102 may be loaded onto the target spacecraft 20 by the satellite working device 100 . Such a configuration may allow the entire functional portion of the satellite work device 100 to be updated in the future without the need to launch an entirely new spacecraft, while the enables maintenance to be performed on the target spacecraft 20 by the pod 102 at .

As depicted in FIG. 11, pod 102 can travel directly to target spacecraft 20 (eg, can also be coupled to target spacecraft 20) or can be prepositioned in a substantially geosynchronous orbit. It may be required to be mounted on the target spacecraft 20 and/or delivered to the target spacecraft after being installed. For example, the pod 102 itself may not be able to independently dock with the target spacecraft 20 and/or may not be able to rendezvous with the target spacecraft 20 (e.g., it may not have the necessary systems). by not). In such embodiments, pod 102 may use its own propulsion and/or power to change its orbit for the purpose of rendezvous with satellite work device 100 . Once at the desired location, spacecraft working device 100 can capture pod 102 using a docking mechanism (eg, docking mechanism 152 shown in FIG. 2B) on spacecraft working device 100 . . Prior to capture, pod 102 may remain in orbit close to satellite working device 100 or target spacecraft 20 to reduce transit time to target spacecraft 20 .

In some embodiments, one or more thrusters on the boom assembly (eg, a single boom assembly 206 as shown in FIG. 3) move the pod 102 from the initial launch plunge trajectory to its intended position. can be used to facilitate delivery to an orbit where the As shown in FIG. 3, pods 102 optionally launch one or more pods 102 as either primary or secondary payloads with one or more payloads 101 shown in FIG. It can have all of the structural and functional parts that allow it to be mounted on a vehicle. One or more pods in an initial orbit where the launch vehicle (e.g., carrier spacecraft 50) is not the final orbit where the pods 102 are to be populated (e.g., the orbit where the pods 102 are resupplied) 102 can be released. In some embodiments, the orbit of pod 102 is determined in order to allow pod 102 to be captured by spacecraft working system 100 for later mounting on host spacecraft 20 . The propulsion system can be used to modify the In some embodiments, pod 102 may correct its trajectory using a single (or multiple) thruster boom (eg, boom assembly 206 shown in FIG. 3). The carrier spacecraft 50 will launch one or more pods at any orbit where the pod 102 will have sufficient fuel and power to produce a delta velocity to correct the orbit of the pod 102 to the desired orbit. 102 can be released. In some embodiments, the pod 102 may be maneuvered to a trajectory to be captured (e.g., loaded, re-fed, etc.), which capture may be performed in any trajectory that accomplishes tasks for life extension. (eg, low earth orbit (LEO), medium earth orbit (MEO), geosynchronous orbit (GEO), geosynchronous orbit, cislunar orbit, or other orbit).

In some embodiments, the pod 102 can independently determine its state by itself when not attached to any of the re-delivery device 30, the carrier spacecraft 50, the target spacecraft 20, or the satellite working device 100. Additional devices as payloads 101 may be included in pod 102 to maintain or allow pod 102 to deliver supplies in payload 101 to another spacecraft. These additional devices in the separate or integrated payload 101 of the pod 102 include reaction wheel assemblies, inertial reference units (eg, gyroscopes), GPS transponders (eg, with GPS antennas), Any suitable combination of spacecraft control and support devices may be included, such as thrusters, antennas, star trackers, and/or additional solar cells. Pod 102 may have any of the components discussed above in spacecraft work device 100 or pod 102 of FIGS. 2A, 2B, and 3 . In some embodiments, the pod 102 is configured to maintain the orientation of the pod 102 in space (e.g., altitude control sensors and actuators), to change speed (e.g., propulsion system thrusters, tanks, and fuel), to determine the orbit of the pod (e.g. ranging transponders or GPS transponders), to augment power to support these functions (e.g. additional solar cells), and to augment ground communications. An on-board computer can be utilized to use these additional devices (eg, an auxiliary antenna) to do so.

The embodiments disclosed above and illustrated in the accompanying drawings do not limit the scope of the present disclosure. for these embodiments are merely examples of embodiments of the present disclosure as defined by the appended claims and their legal equivalents. Any equivalent embodiments are intended to be within the scope of this disclosure. Indeed, from this description it will become apparent to those skilled in the art that various modifications of the disclosure, including alternative and useful combinations of the elements described, in addition to those shown and described herein. Let's be Such modifications and embodiments also fall within the scope of the appended claims and their legal equivalents.

Claims (20)

A spacecraft working pod , wherein the spacecraft working device:
a body configured to be deployed from a carrier spacecraft in an initial orbit that is not geosynchronous orbit that remains stationary with respect to the rotation of the earth;
at least one spacecraft work component configured to perform at least one work operation on a target spacecraft while coupled to the target spacecraft;
a thruster assembly configured to vary at least one of orbit, velocity, or momentum of the spacecraft work pod ;
a docking mechanism for coupling the body to the target spacecraft;
The thruster assembly is configured to transport the body from the initial orbit to the geosynchronous orbit after deployment of the body from the carrier spacecraft , and the spacecraft work pod is mounted on the target spacecraft. requiring a separate spacecraft separate from the carrier spacecraft to be coupled;
Spacecraft work pod . 2. The spacecraft work pod of claim 1, wherein a thruster assembly is positioned on a boom arm coupled to said body . said another spacecraft rendezvous with said spacecraft working pod , delivering said spacecraft working pod to said target spacecraft, and coupling said spacecraft working pod to said target spacecraft. 3. The spacecraft work pod of claim 1 , configured to: The thruster assembly is further configured to change at least one of trajectory, velocity, or momentum of the target spacecraft when the body is coupled to the target spacecraft. A spacecraft working pod according to item 1. 2. The spacecraft work pod of claim 1, further comprising a payload configured to be delivered with the spacecraft work pod to the target spacecraft and carried by the spacecraft work pod . 2. The universe of claim 1, wherein the thruster assembly is configured to modify the trajectory of the spacecraft work pod to position the spacecraft work pod in close proximity to the target spacecraft. Shipwork pod . A spacecraft work pod , said spacecraft work pod :
a body configured to be deployed from a carrier spacecraft in an initial trajectory that is not the final destination trajectory of the spacecraft working device;
at least one spacecraft work component configured to perform at least one work operation on a target spacecraft while coupled to the target spacecraft;
a docking mechanism for coupling the body to the target spacecraft;
wherein the body is configured to be transported from the initial orbit to the final destination orbit after deployment of the body from the carrier spacecraft, the docking mechanism holding and holding the body relative to the target spacecraft; configured to be coupled to said target spacecraft with the aid of another coupling spacecraft configured to deploy said spacecraft working pod for independently rendezvous with said target spacecraft; and having no capability to dock with said target spacecraft;
Spacecraft work pod . 8. The spacecraft work pod of claim 7, further comprising a thruster assembly configured to transport the body from the initial orbit to the final destination orbit after deployment of the body from the carrier spacecraft. . 8. The spacecraft work pod of claim 7 , wherein the spacecraft work pod does not have one or more prepositioning systems or devices . 8. The spacecraft task of claim 7, wherein the spacecraft task pod is configured to be positioned at a location adjacent to the target spacecraft using only another separate spacecraft mechanism. Pod for. A method of working on a spacecraft, the method comprising:
deploying a pod to an initial orbit below a geosynchronous orbit; and transporting the pod from the initial orbit to the substantially geosynchronous orbit;
coupling the pod to the spacecraft with an additional spacecraft in the geosynchronous orbit;
and performing at least one spacecraft work operation after being coupled to said spacecraft. 12. The method of claim 11 , further comprising assisting coupling the pod to the spacecraft using the additional spacecraft that are separate from both the pod and the spacecraft. after transporting the pod from the initial orbit to the substantially geosynchronous orbit;
approaching the spacecraft to the additional spacecraft holding the pod, separate from both the pod and the spacecraft;
causing the additional spacecraft holding the pod to rendezvous with the spacecraft;
coupling the pod to the spacecraft using the additional spacecraft ;
12. The method of claim 11, further comprising: 12. The method of claim 11, wherein transporting the pod from the initial orbit to the geosynchronous orbit comprises moving the pod from the initial orbit to the geosynchronous orbit using thruster assemblies of the pod. . The step of transporting the pod from the initial orbit to the geosynchronous orbit includes deploying the pod to the initial orbit by a separate launch spacecraft and then using the separate spacecraft to move the pod from the initial orbit to the earth. 12. The method of claim 11, comprising transporting the pod to a synchronous orbit. 12. The method of claim 11, wherein performing at least one spacecraft work operation comprises adjusting at least one of trajectory, velocity, or momentum of the spacecraft using the pod's thruster assemblies. described method. 12. The method of claim 11, wherein performing at least one spacecraft work operation comprises delivering at least one spacecraft component to the spacecraft using the pod. A spacecraft work pod , said spacecraft work pod :
A thruster assembly comprising at least one thruster, said thruster assembly extending from a first orbit to a second orbit when said spacecraft work pod is not coupled to another spacecraft. a thruster assembly configured to alter the orbit of the spacecraft work pod ;
a body configured to be coupled to a target spacecraft by a carrier spacecraft at a location adjacent to the target spacecraft;
at least one spacecraft working component configured to perform at least one work operation on the target spacecraft when the body is coupled to the target spacecraft; One spacecraft working component includes the thruster assembly which, when the body is coupled to the target spacecraft, controls the orbit, velocity, or momentum of the target spacecraft. at least one spacecraft working component further configured to change at least one of;
a communication device configured to receive data relating to the at least one of trajectory, velocity, or momentum of the target spacecraft from a transmission location remote from the spacecraft workpod, the spacecraft while the spacecraft work pod is docked to the target spacecraft based on received data received by the communication device regarding at least one of trajectory, velocity, or momentum of the target spacecraft; a working pod adapted to control the thruster assembly to vary at least one of trajectory, velocity, or momentum of the target spacecraft;
Spacecraft working device. a computer wherein said communication device is configured to receive said data from said transmission location remote from said spacecraft workpod and programmed to operate said thrusters in response to said received data; 19. The spacecraft work pod of claim 18, further comprising. 19. The spacecraft work pod of claim 18, wherein the communication device is configured to receive the data over at least one of a wired communication channel or a wireless communication channel.