Space traffic management system architecture

1. A Space Traffic Management (STM) system comprising:

a Space Traffic Management System Service Supplier (S3) interface configured for sending a space conjunction request to a Conjunction Assessment Supplier (CAS) interface;

a Space Situational Awareness Supplier (SSA) interface configured for receiving and fulfilling space object data requests, wherein the SSA interface further includes generating a meta-catalog by multiparty computation (MPC) that securely shares inputs from a plurality of SSA interfaces for performing computations on position and trajectory information of resident space objects while shielding the inputs from one or more other interfaces;

the Conjunction Assessment Supplier (CAS) interface configured for:

receiving the space conjunction request from the S3 interface,

requesting and receiving the space object data from the SSA interface; and

generating and sending a conjunction data message to the S3 interface;

wherein the system provides an automated service that uses the conjunction data message for spacecraft owner operators to anticipate and avoid a space traffic conjunction.

2. The system of claim 1 , further comprising:

Supplemental Data Supplier (SDS) Interface to receive space environment data requests, responses, and notifications.

3. The system of claim 2 , wherein two or more of the SSA interface, S3 interface, CAS interface, and the SDS interface are combined into a single interface.

4. The system of claim 1 , further comprising:

an STM gateway for relaying and recording messages between the S3, the CAS, and the SDS.

5. The system of claim 1 , further comprising:

where one or more objects in a space conjunction are not controlled by an O/O participating in the STM system.

6. The system of claim 1 , further comprising:

the S3 further configured to enable negotiations between two spacecraft owner operators.

7. The system of claim 1 , further comprising:

Supplemental Data Supplier (SDS) Interface to receive space weather data identifying space weather events.

8. The system of claim 1 , wherein two or more of the S3, the SSA, and the CAS functions are performed by a single entity.

9. A Space Traffic Management (STM) system comprising:

a Space Situational Awareness Supplier (SSA) interface configured for receiving and fulfilling space object data requests, wherein the SSA interface further includes generating a meta-catalog by multiparty computation (MPC) that securely shares inputs from a plurality of SSA interfaces for performing computations on position and trajectory information of resident space objects while shielding the inputs from one or more other interfaces;

a Space Traffic Management System Service Supplier (S 3 ) interface configured for sending a conjunction avoidance maneuver request to the Conjunction Assessment Supplier (CAS) interface;

the Conjunction Assessment Supplier (CAS)interface configured for:

receiving the conjunction avoidance maneuver request from the S 3 interface,

requesting and receiving the space object data from the SSA interface, and

sending the conjunction avoidance maneuver to the S 3 interface;

wherein the system provides an automated service that uses the conjunction avoidance maneuver for spacecraft owner operators to validate and negotiate conjunction avoidance.

10. The system of claim 9 , further comprising:

Supplemental Data Supplier (SDS) Interface to receive space environment data requests, responses, and notifications.

11. The system of claim 10 , wherein two or more of the SSA interface, S3 interface, CAS interface, and the SDS interface are combined into a single interface.

12. The system of claim 10 , further comprising:

an STM gateway for relaying and recording messages between the S3, the CAS, and the SDS.

13. The system of claim 9 , further comprising:

where one or more objects in a space conjunction are not controlled by an O/O participating in the STM system.

14. The system of claim 9 , further comprising:

the S3 further configured to enable negotiations between two of the spacecraft owner operators.

15. The system of claim 9 , wherein two or more of the S3, the SSA, and the CAS functions are performed by a single entity.

16. A method of providing a Space Traffic Management (STM) framework comprising:

receiving a registration of an owner operator (O/O) by a System Service Supplier (S3) to participate in the STM system;

sending, by the S3, data about the O/O's spacecraft to a Space Situational Awareness Supplier (SSA);

updating, by the SSA, a catalog of resident space objects (RSO), wherein the SSA further performs the step of generating a meta-catalog by multiparty computation (MPC) that securely shares inputs from a plurality of SSAs for performing computations on position and trajectory, information of resident space objects while shielding the inputs from one or more other interfaces;

sending, by the S3, a request for an encounter screening to a Conjunction Assessment Supplier (CAS), the conjunction assessment supplier to use data from the SSA to return conjunction data message indicating potential conjunctions;

wherein the messages are sent through the STM framework, and an STM gateway routes and stores the messages sent by the S3; SSA, and CAS.

17. The method of claim 16 , wherein providing the conjunction data message comprises:

receiving the space conjunction request from the S3 interface,

requesting and receiving the RSO data from the SSA interface; and

generating and sending a conjunction data message to the S3 interface.

18. The method of claim 16 , further comprising:

the CAS receiving space environment data from a Supplemental Data Supplier (SDS), the CAS using the space environmental data in the encounter screening.

19. The method of claim 16 , wherein the potential conjunctions include:

(1) conjunctions between an RSO of the O/O and another O/O that participates in the STM framework;

(2) conjunctions between the RSO of the O/O and different O/O that does not participate in the STM framework;

(3) conjunctions between the RSO of the O/O and objects that are not controlled.

20. The method of claim 19 , further comprising:

generating, by the CAS, a proposed maneuver in response to determining that one of the potential conjunctions requires a maneuver;

receiving, via the S3, the proposed maneuver by the O/o; and

when the proposed maneuver is accepted by the O/O, publishing by the S3 the accepted maneuver to the catalog of the SSA.