AWS Ground Station Antenna ASTERIA AWS
Total Page:16
File Type:pdf, Size:1020Kb
N E T 3 0 8 - R Enabling automated astrophysics with AWS Ground Station Tom Soderstrom Shayn Hawthorne CTIO, JPL Office of the CIO Senior Manager, AWS Ground Station Amazon Web Services © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Agenda Intro to AWS Ground Station AWS Ground Station overview – customer view Demo ASTERIA AWS Ground Station experiment AWS Ground Station • Managed ground stations • No long-term commitments required • Simple, pay-as-you-go pricing – pay by the minute • Close proximity to AWS Regions • Self-service scheduling • First-come, first- served Traditional ground station challenges • Build, lease, or rent • Large up-front capital to build • Expensive and complex to maintain • Inelastic scaling • Opaque pricing • Scheduling conflicts and contention High-level architecture Customer VPC Downlink Antenna Tracking Mission data control processing EC2 Uplink Antenna Software radio / System data recovery Digitizer / Scheduling Tracking radio Telemetry and Control Self-service and automation through AWS Console and AWS APIs/SDK AWS Security and Identity Key events • Customers configure what they want to do (Mission Profile + Configs) • Customers reserve/schedule a Contact (Mission Profile + Configs + Satellite + Ground Station + Timing) • System executes the Contact Configuration • Customers create a Mission Profile consisting of multiple Configs to configure the antenna system for a contact • Configs and Mission Profiles are created via an API Mission Profile Dataflow Dataflow Edge Tracking Config Edge (Data and where it ... (Use autotrack?) (Data and comes from) where it goes) Antenna Dataflow Antenna Dataflow Endpoint Downlink Config Endpoint Group Uplink Config Group (Frequencies, (Where to send (Frequencies, (Where data polarity) data) polarity) comes from) Downlink and DataflowEndpoint { { "antennaDownlinkConfig": { "endpointDetails": [ { "spectrumConfig": { "endpoint": { "bandwidth": { "address": { "units": "MHz", "name": "192.168.1.100", "port": 55888 "value": 25 }, }, "name": "DataflowEndpoint1", "centerFrequency”: { }, "units": "MHz", "securityDetails": { "roleArn": "value": 8212.5 "arn:aws:iam:…:/GSEniControl", }, "securityGroupIds": [ "polarization": "RIGHT_HAND" "sg-deadbeef" ], } "subnetIds": [ }, "subnet-abcdef12" "name": "MyAntennaDownlinkConfig" ] } } } ] } Reserving a contact • Customers reserve a Contact, specifying Satellite, Ground Station, Mission Profile, and timing • Contacts are reserved via API or Console Contact Ground Mission Start Satellite End Time Station Profile time Tracking Dataflow Dataflow ... Config Edge Edge Antenna Dataflow Antenna Dataflow Downlink Endpoint Uplink Endpoint Config Group Config Group © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Demo – what we’re going to see Mission Profile Contact Tracking Dataflow Dataflow Config Edge Edge Ground Mission Start Satellite End Time Station Profile time Antenna Dataflow Antenna Downlink Dataflow Downlink Endpoint Demod Decode Endpoint Config Group Config Group Customer VPC Downlink RF over IP Downlink Demodulated EC2 & Decoded Data Antenna Data recording System Data saved to S3 Overview of the antenna provider model • AWS Ground Station is actually 3 services • Control Plane • Antenna Provider • Data Delivery Service • The Control Plane has two APIs • Customer-facing API • Antenna Provider-facing API • Our antennas use the antenna provider-facing API High-level architecture Antenna Provider Customer VPC Downlink Downlink … Uplink Uplink Antenna System Code Cloud- based code Key events • Customers configure what they want to do (Mission Profile + Configs) • Customer -> Control Plane • Customers reserve/schedule a Contact (mission profile/antenna matching, Customer/Antenna selection, Times) • Customer -> Control Plane • System executes the Contact • Antenna, Control Plane, Data Delivery At reservation time • Control Plane finds an antenna that can execute the contact • Capability/Config match – all Configs in the Mission Profile • Available during that time • Ground Station has satellite visibility • Control Plane creates the reservation in its internal system • Stores the details of antenna/Config matches • Marks the antenna as “not available” for the duration of the contact Contacts are padded with pre-pass and post-pass durations • Control Plane notifies the Customer that the contact is scheduled At contact execution time Antenna Provider Customer VPC Downlink Downlink … Uplink Uplink Antenna System Code Cloud- based code © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. How do we protect Mother Earth? How do we divert an asteroid? Are we alone Can we find Earth 2.0? How did the universe form, and where is it going? Is/was there life on Mars? JPL is part of NASA and Caltech ▪ Federally Funded (NASA-owned) Research and ▪ 167 Acres (includes 12 acres leased for parking) Development Center (FFRDC) ▪ 139 Buildings; 36 Trailers ▪ University Operated (Caltech) ▪ 673,000 Net Square Feet of Office Space ▪ $2.6B Business Base ▪ 906,000 Net Square Feet of Non-Office Space ▪ 5,800 Employees (e.g., Labs) 19 spacecraft and 7 instruments across the Solar System and beyond that we must protect… Two Voyagers Mars Odyssey Spitzer (2003) Mars CloudSat Jason 2 NEOWISE (2009) Juno (2011) Curiosity (2011) (1977) (2001) Reconnaissance (2006) (2008) Orbiter (2005) NUSTAR (2012) OCO-2 (2014) SMAP (2015) Jason 3 (2016) InSight (2018) MarCO (2018) RainCube (2018) GRACE Follow-On (2018) Instruments Earth Science • MISR (1999) • ASTER (1999) • AIRS (2002) • MLS (2004) • ECOSTRESS (2018) • CAL (2018) • OCO-3 (2019) …and we must be visionary to enable and protect recent and upcoming launches InSIGHT MarCo Cold Atom Lab TEMPEST RainCube May 2018 May 2018 May 2018 May 2018 May 2018 GRACE-FO ECOSTRESS OCO-3 COSMIC-2 Mars 2020 Mars Helicopter May 2018 June 2018 Feb 2019 June 2019 2020 NISAR 2021 SWOT 2021 PSYCHE 2022 Europa Clipper 2023 SPHEREx 2023 Using the ASTERIA* CubeSat to demonstrate In- Space Autonomy *Arcsecond Space Telescope Enabling Research In Astrophysics 6U CubeSat built, tested, operated by JPL, in collaboration with MIT First CubeSat to detect an exoplanet! Deployed from International Space Station Development Delivery Launch Deployment Operations lifetime Dec 2014 through Jun 2017 1 Jun 2017 14 Aug 2017 20 Nov 2017 Exp. through Apr 2020 Completed prime mission Feb. 2018; now used for technology validation, including resilient onboard execution, autonomous navigation, and new business models. Resilient On-Board Multi-mission EXECutive (MEXEC) Shift the paradigm to operate spacecraft from timed sequences to closed-loop task execution – provides resilience to faults and anomalies 26 Resilient On-Board Autonomous Navigation Geostationary spacecraft observed with ASTERIA’s camera are used by Autonav software – provides resilience in GPS-denied environments Image of Comet Wirtanen taken 12/18 “Christmas Comet” Comet Wirtanen Pleiades ASTERIA AWS Ground Station experiment Objectives: Demonstrate and evaluate utility of Ground Station as a Service: 1. Utility and cost-effectiveness for CubeSats 2. Applicability to NOS: e.g., downlink on demand, coordination among assets 3. Document AWS-compatible GDS design, including heritage points, performance characteristics, recommendations and lessons learned for other CubeSats ASTERIA Spacecraft in Low Earth Orbit Approach: The ASTERIA cube-sat completed its primary PI: Lorraine Fesq, JPL objectives, and is in an extended mission that includes demos 1. Demonstrate telecom compatibility and downlink between Milestones and Schedule ASTERIA and AWS Ground Station Kickoff May 2019 2. Acquire frequency approval for uplink licensing Downlink Experiment June 2019 3. Demonstrate telecom compatibility and uplink between Uplink and Downlink Experiment Aug 2019 AWS Ground Station and ASTERIA on licensed frequencies. Cloud-based Operations Sep 2019 4. Conduct Ground Data System Demonstration in AWS Virtual Report Oct 2019 Private Cloud – Virtual Mission Operations 5. Document AWS-compatible GDS design How do ideas start? How fast can we iterate? AWS Ground Station experiment Downlink 1. Signal lock to AWS Ground Station 2. Frame sync with AWS Ground Station 3. Telemetry processing and verification of downlink 4. Configure RTLogic modem in Amazon VPC (qFEP & qRadio) for downlink capability 5. Downlink to backup MOC (AWS GS) in parallel with MSU • Required cloud-based version of ASTERIA GDS Uplink 1.Complete Licensing with NTIA for uplink via AWS Ground Station 2.Transition from AWS Ground Station preview into uplink & downlink operations 3.Document the AWS Ground Station GDS design and identify steps that need to be completed for other NASA project adaptations (ongoing, in progress) 4.Transition to AWS GovCloud implementation of AWS Ground Station (TBD) Experiment confirms that AWS Ground Station can provide uplink/downlink services for future CubeSats and provides ASTERIA with ground stations ASTERIA GDS Configuration NOTE: AWS does not hold or store any customer data EC2 Instance 1 ASTERIA RF/IP RF/IP AWS VPC DataDefender DataDefender Digitizer (Lossless UDP) (Lossless UDP) EC2 Instance 2 Raw RTLogic Frames AIT Server qRadio & qFEP (hosted) qFEP & qRadio Telemetry Configuration AWS Ground Station Antenna Ground Station OpenMCT Scheduling & Server S3 During the contact window, EC2 instances communicate with AWS Ground Station’s Configuration (hosted) antenna gateway over an elastic network interface (ENI) connection in the Amazon VPC