IP Library Granted Patent US 12,244,575
Granted Patent B2
US 12,244,575 · App. 18/169,527 · Granted Mar 4, 2025

Method and system for satellite tasking

Inventors: Reuben Sorensen (Ann Arbor, MI); Ryan Farris (Arlington, VA); Doug Muhlbauer (Sterling, VA)
Assignee: R2 SPACE, LLC
H04L63/0428G06F9/4843G06F9/54H04L9/14H04L63/0272
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,244,575
App. No.
18/169,527
Granted
Mar 4, 2025
Kind
B2
Abstract

Various embodiments of the present technology relate to satellite tasking systems and methods. More specifically, embodiments include an operations center configured to receive a tasking order from a client and to generate satellite instructions for the satellite based on the tasking order. In some examples, a security tag is generated and associated with the tasking order. The security tag is correlated with the client on a remote server.

Claims (36)

1. A satellite tasking method comprising:

receiving, at an operations center, a satellite tasking order from a client;

generating, in the operations center, a security tag associated with the tasking order;

generating, in the operations center, instructions for a satellite based on the tasking order, wherein the instructions include the security tag, and wherein the security tag comprises a string of characters that tie the tasking order to the client;

transmitting the instructions to the satellite;

receiving, at a remote cloud server, captured data from the satellite, wherein the captured data is responsive to the satellite tasking order;

receiving, at the remote cloud server, a request from the client to access the captured data; and

determining that the client may access the captured data based on the security tag, wherein the determining that the client has access to the captured data comprises using a resolving function to attribute the characters of the security tag to the client.

2. The method of claim 1 , wherein the characters of the security tag are randomly generated.

3. The method of claim 1 , further comprising the step of providing a virtual private network (VPN), wherein the tasking order is transmitted from the client to the operations center via the VPN.

4. The method of claim 1 , further comprising the step of providing a VPN, wherein the captured data is transmitted from the remote cloud server to the client via the VPN.

5. The method of claim 1 , further comprising the step of providing an application programming interface (API) in the operations center, wherein the API is configured to receive the tasking order in a format recognizable by an operations center processor.

6. The method of claim 1 , wherein the step of transmitting the instructions to the satellite comprises using a transmitter in the operations center to transmit the instructions.

7. The method of claim 1 , further comprising the step of storing a client ID associated with the client in an operations center server, the operations center server being inaccessible to the client.

8. The method of claim 1 , further comprising the step of encrypting the tasking order with a public encryption key.

9. The method of claim 8 , wherein the public encryption key comprises an AES 256 encryption key.

10. The method of claim 1 , wherein the captured data is satellite imagery.

11. A satellite tasking network system comprising:

a client system configured to transmit a satellite tasking order from a client;

an operations center configured to:

receive the tasking order,

generate a security tag associated with the tasking order, wherein the security tag comprises a string of characters that tie the tasking order to the client,

generate instructions for a satellite based on the tasking order, and

transmit the instructions to the satellite, wherein the instructions include the security tag; and

a remote cloud server configured to:

receive captured data from the satellite, wherein the captured data is responsive to the satellite tasking order, wherein the remote cloud server is further configured to receive a request from the client to access the captured data, and

determine that the client has access to the captured data based on the security tag, wherein the determining that the client has access to the captured data comprises using a resolving function to attribute the characters of the security tag to the client.

12. The system of claim 11 , wherein the characters of the security tag are randomly generated.

13. The system of claim 11 , further comprising a virtual private network (VPN), wherein VPN is configured to route the tasking order from the client system to the operations center.

14. The system of claim 11 , further comprising a VPN, wherein the VPN is configured to route the captured data from the remote cloud server to the client system.

15. The system of claim 11 , wherein the operations center further comprises a processor and an application programming interface (API), the API being configured to receive the tasking order in a format recognizable by the processor.

16. The system of claim 11 , wherein the operations center further comprises a transmitter, the transmitter being configured to transmit the instructions to the satellite.

17. The system of claim 11 , wherein the operations center further comprises an operations center server, the operations center server being inaccessible to the client and configured to store a client ID.

18. The system of claim 11 , wherein the client system is configured to encrypt the tasking order with a public encryption key.

19. The system of claim 18 , wherein the public encryption key comprises an AES 256 encryption key.

20. The system of claim 11 , wherein the captured data is satellite imagery.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 15, 2023
From: SORENSEN, REUBEN; FARRIS, RYAN; MUHLBAUER, DOUG
To: R2 SPACE, INC.
Reel/Frame 062709/0443 →
CHANGE OF NAME Recorded Feb 15, 2023
From: R2 SPACE, INC.
To: R2 SPACE, LLC
Reel/Frame 062761/0869 →
Continuity (3)
Continuation 16835141 · Mar 30, 2020
Provisional Application 62825718 · Mar 28, 2019
Related Publication 20230198963A1 · Jun 22, 2023
References Cited (1)
US 20180205715A1 · Ingale · 2018 [cited by examiner]