“International Space Communications and Navigation Network Space Communications and Navigation Office NASA’s Concept: “International Space Communications and Navigation Network Service Architecture” NASA Consolidated Network Services Team Space Communications and Navigation Office NASA Headquarters Drawn from Rush / Hooke Presentation to IOAG-11 June 19, 2007, Cebreros, Spain Presented to CCSDS Cross Support Service Architecture BoF Peter Shames, 13 March 2008

Top Level Space Communications & Navigation Architecture Martian Local Network Lunar Local Network Martian Trunk Lunar Trunk L1/L2 Individual Spacecraft Connections Earth Local Network 13 March 2008

Cross Support Interfaces Source: NASA IOAG Internetworking Proposal 13 March 2008

Background 2005-2006: NASA’s Space Communications Architecture Working Group (SCAWG) Fresh look at NASA’s overall space communications and navigation infrastructure Created the “NASA Space Communications and Navigation Architecture - Recommendations for 2005-2030”: https://www.spacecomm.nasa.gov/spacecomm/ 13 March 2008

Description of The Present Service Architecture Network-specific service interfaces Network-specific service management interfaces Network-specific service interfaces SN White Sands Ground Terminal Second TDRSS Ground Terminal Guam Remote Ground Terminal Network Control Center (NCC) Mission Operations Center Mission Operations Center GN Wallops Orbital Tracking Information System (WOTIS) Mission Operations Center Mission Operations Center DSN Goldstone Complex Network Operations Control Center (NOCC) Mission Operations Center Canberra Complex Madrid Complex NISN

Description of The Future Service Architecture Standard service interfaces Standard service management interfaces Standard service interfaces SN White Sands Ground Terminal Second TDRSS Ground Terminal Guam Remote Ground Terminal Network Control Center (NCC) Mission Operations Center Mission Operations Center GN Wallops Orbiting Tracking Information System (WOTIS) Enterprise Service Management Function Mission OperationsCenter DSN Goldstone Complex Network Operations Control Center (NOCC) Mission Operations Center Canberra Complex Madrid Complex NISN

Conceptual scope of NASA’s Networks NASA SPACE COMMUNICATIONS NETWORK End Users (Earth) End Users (Remote) Control Centers Earth Ground Stations Relays NASA SPACE COMMUNICATIONS NETWORK Data Flow Information Flow Source: Dave Israel 13 March 2008

NASA’s Layered Protocol Concept “on-ramps” for accessing protocol End User End User User Application User Application Service Access Service Access “on-ramps” for accessing protocol services Layer (n+1) Layer (n+1) Layer (n) Layer (n) Layer (n-1) Layer (n-1) Space Communications Path 13 March 2008

NASA’s view: Single Hop Communications User End System User End System End User (Earth) End User (Remote) User Application User Application Application Service Application Service “on-ramps” for accessing protocol services Transport Service Transport Service Network Service Network Service Link Service Link Service Physical Service Physical Service Space Communications Path 13 March 2008

NASA’s view: Multi Hop Communications User End System User End System End User (Earth) End User (Remote) Relay System User Application User Application Relaying Application: Real Time or Store-and-Forward Application Service Application Service “on-ramps” for accessing protocol services Transport Service Transport Service Network Service Network Service Network Service Link Service Link Service Link Service Link Service “Bent- pipe” Physical Service Physical Service Physical Service Physical Service Space Communications Path 13 March 2008

NASA Space Communications Architecture: where next? What concept unites all of these views into a cohesive, consolidated “network of networks”? 13 March 2008

NASA’s Concept: provide “any-to-any” services … Space Communication and Navigation Services Mission User 13 March 2008

… via an International Service Infrastructure … Mission User Mission User International Space Communications and Navigation Service Infrastructure 13 March 2008

… offering standard service interfaces Space Mission User Space Mission User Space Mission User Space Mission User Standard Services Standard Services Standard Services Standard Services Standard Services International Space Communications and Navigation Service Infrastructure Source: Mario Merri/Mike Kearney 13 March 2008 21 April 2017

Discover Capabilities Mission User Negotiate Support Provide Services There are multiple phases involved with providing space communications and navigation services Discover Capabilities Mission User Mission Formulation Phase Negotiate Support Mission Design Phase Provide Services Mission Operations Phase 13 March 2008

Service Provider Options Mission User User/provider negotiations involve the selection and refinement of service options Options Select Mission User Service Provider Provide 13 March 2008

Discover Capabilities Mission User Negotiate Support Provide Services Activities across all Phases should follow a principle of successive refinement Service Catalog Provide Select Capability Provider Mission User Discover Capabilities Mission User Mission Formulation Service Agreements Provide Select Package Provider Mission User Negotiate Support Mission Design Configuration Profiles Provide Select Service Provider Mission User Provide Services Mission Operations 13 March 2008

Mission Formulation Phase: discover available services; certify and register authorized users Mission “M” user browses the service catalog to determine which available network providers may potentially be available to support. User decides to explore potential support arrangements example: Mission User Service Provider Service Discovery Functions Service Discovery Activities (Background administrative negotiation) Service Catalog SM I/F SM I/F Service Management Interface Mission Formulation Manager example: Mission “M” user requests authority to enter exploratory support discussions. Users x, y and z are validated and authorized to negotiate during formulation phase 13 March 2008

Mission Design Phase: negotiate service agreement; create configuration profiles example: “Service Agreement: per Service Package M23, SN will support Mission “M” with one S-band forward link at 8kbps or 16 kbps; one S-band return link with data rate in the 10 kbps – 2 Mbps range; and one-way or two-way Doppler tracking” Mission User Service Provider Service Negotiation Functions (Background administrative negotiation) Service Negotiation Activities Network Integration Manager Service Agreement DB Mission Formulation Manager SM I/F SM I/F Config Profile DB Service Management Interface Service Agreement DB Service Catalog Config Profile DB Network Engineering “Service Package M23, Configuration Profile C23.761: provide Mission “M” with S-band forward link at 8kbps, S-band return link with data rate = 1 Mbps, and one-way Doppler tracking service” example: 13 March 2008

Mission Operations Phase: Provide Services “Provide a contiguous Telemetry, Telecommand and Raw Radiometric data acquisition pass for Mission “M”, per Service Package M23 and using configuration profile C23.761 with Station “S67”, between 15:00 and 15:45 Z on 2007-06-19” example: Service Provider Mission User Provider Scheduling and Execution Functions Mission Planning, Scheduling and Execution Functions Service Agreement DB Service Agreement DB Config Profile DB Config Profile DB Network scheduling Mission scheduling Mission Planning Manager SM I/F SM I/F Service Management Interface Equipment configuration, control, monitoring Mission planning Service Utilization Interface 1 FDF 2 Service Users Mission User 3 Station S67 Service Providing Resources 1. Raw Radiometric service 2. Forward CLTU telecommand service 3. Return All Frames telemetry service example: 13 March 2008

NASA’s Proposed Approach Consolidate NASA’s three current mission support networks around the organizing principle of a service-based architecture, that builds upon significant current international investment in “SLE” Coordinate the development of that service-based architecture with other IOAG agencies to ensure future interoperability - NASA proposes that its networks should be a component of an international space communications and navigation service infrastructure Evolve this international infrastructure by progressively exposing increasingly richer suites of services for cross support - Participating Agencies will agree to implement a common, evolving catalog of agreed Cross Support Transfer Services Supported by common, evolving Cross Support Service Management systems Expand the scope of the international infrastructure to embrace new capabilities as needs emerge - Support of the Mission Design and Mission Formulation phases Provision of new network capabilities, e.g., Lunar and Mars relays Space internetworking 13 March 2008

NASA’s Initial Scope Initially focus on expanding NASA’s service infrastructure based on what we have today – Earth-based networks Basic communications and tracking services Consolidation of services in the Mission Operations Phase Primary Initial Scope 13 March 2008

Current state of the art for standard capabilities Discover Capabilities Negotiate Support Provide Services Mission Formulation Phase Design Operations User Full specification of basic “SLE” data transfer services Growing deployment community Service Management nearing initial Standard Prototypes under test Generalization and expansion into “Cross Support Transfer Services”, including Radiometric and Monitoring Service Management defines Configuration Profiles to specify fixed or alternative mission parameters Service Management defines some content of Service Agreements But no process for negotiating that content No uniform way to: obtain knowledge of network capabilities describe network services. negotiate or document mission support Key: Exists Emerging Does not exist 13 March 2008

Goal for standard capabilities Discover Capabilities Negotiate Support Provide Services Mission Formulation Phase Design Operations User Fully standardized process defined for initial negotiation of network support Internationally agreed Cross support Service Catalog defined and ready for operational use, providing access to uniformly-described service offerings of Agency networks Expansion to Lunar and Mars Relays and internetworked operations Fully standardized process defined for negotiating network support via Service Agreements XML-based Service Agreements and Configuration Profiles defined and ready for operational use Expansion to Lunar and Mars Relays and internetworked operations Cross Support Transfer Services (CSTS) and Cross Support Service Management (CSSM) standards complete – Ready for widespread deployment and operational use across international networks Expansion to Lunar and Mars Relays and internetworked operations Key: Exists Emerging Does not exist 13 March 2008

First Step - Mission Operations Phase: initial Earth-Based “Service Set” Service Provider Mission User SM I/F SM I/F Service Management Interface Forward Data Delivery Services Return Data Delivery Services Mission User Service Utilization Interface SU I/F Service Provision Radiometric Services Positioning & Timing Services Service Users Service Production 13 March 2008

Initial Service Set: Earth-Based Return and Forward Forward data delivery services: Forward File (CFDP) Forward Space Packet Internetworking Forward CLTU (TC Frame, AOS Frame,octet-stream) Forward Bitstream Return data delivery services: Return File (CFDP) Return Space Packet Return All Frames; Return Channel Frames Return Unframed Telemetry Return Bitstream Radiometric services: Raw radio metric data Validated radio metric Delta-DOR Position &Timing services: Position Determination Time Determination (Clock Correlation, Time distribution) 13 March 2008 26

Initial Service Set - service data unit view: Earth-Based Return and Forward Service Provision Space Packet File Radiometric Validated Application Position Delta-DOR Application Time Space Packet File Pos & Time Radiometric Transport Transport Internetworking Packet Internetworking Packet Network Network CLTU All Frames Channel Frames Bit-stream Link Unframed Telemetry Link Bit-stream Physical Raw Radiometric Physical FORWARD RETURN Service Production 13 March 2008

Forward data delivery services: Current Standard Service Set mapping to NASA Networks: Earth-Based Return and Forward ** DSN SN GN Forward data delivery services: Forward File (CFDP) Forward Space Packet Internetworking Forward CLTU (TC Frame, octet stream) Forward Bitstream* Return data delivery services: Return File (CFDP) Return Space Packet Return All Frames; Return Channel Frames Return Unframed Telemetry Return Bitstream* Radiometric services: Raw radio metric data Validated radio metric Delta-DOR Positioning &Timing services: Position Determination Time Determination (Clock Correlation, Time distribution) L L L L L L L L L L L L * Deprecated DSN services; provided only to legacy missions ** “GN” has been renamed “NEN” Current capability Planned Upgrade Proposed addition No planned service Deprecated Local standard Source: Mike Kearney L 13 March 2008 28

Communication View Example – RAF Service 13 March 2008

Proposed Next Steps NASA recommends that: IOAG/CCSDS should jointly focus on accelerated development of the Cross Support Service Architecture, with a view towards creating three new CCSDS Recommendations: CCSDS Recommended Practice: Cross Support Service Architecture CCSDS Recommended Standard: Cross Support Service Catalogs CCSDS Recommended Standard: Cross Support Service Agreements IOAG/CCSDS should continue to push towards rapid completion of the current SLE Service Management Blue Book, and towards accelerated development of the generic Cross Support Transfer Services and Cross Support Service Management standards CCSDS should be asked to issue a communiqué to IOAG, detailing progress made on the Cross Support Service Architecture, and related standards, at the completion of the CCSDS Fall 2007 technical meeting IOAG should consider forming a working committee to: Explore how to create and maintain the international IOAG Cross Support Service Catalog: Provide a guide to services exposed for inter-agency use within CCSDS-compliant agencies Indicate to CCSDS-compliant agencies where infrastructure development is needed Coordinate the international prototyping and interoperability testing of specific services and their associated service management capabilities 13 March 2008

Current Status, March 08 Developed a NASA Service Conceptual Architecture Description (CAD) Has been reviewed by the three NASA networks RIDs are being finalized Intended to form core of SCaN Services ADD, elaborated during the next stage ADD promotes: Adoption of existing CCSDS standards where they exist Support for development of new CCSDS standards where needed Use of NASA or network specific standards only where essential Services ADD uses the four viewpoints (Physical, Enterprise, Service(functional), and Communications) from the IOAG Cross Support Service Architecture Agreement reached with NASA Constellation program (CxP) that supports this general approach for service delivery 13 March 2008

Supplementary Material Space Communications and Navigation Office Supplementary Material

Overall Architecture Networking Architecture CROSSCUTTING ARCHITECTURE Spectrum Framework CROSSCUTTING ARCHITECTURE Security Architecture Navigation Architecture Earth-based Antenna Element Earth-based Relay Satellite Element Lunar Relay Satellite Element Mars Relay Satellite Element ELEMENT ARCHITECTURES 13 March 2008

State of Interoperable Framework Development Status Layer* Notes TBD Application Provides services such as file delivery or time service Middleware Provides common application interfaces over heterogeneous lower layers TBD Application Layer Security Provides secure communications transparently to the lower layers TBD TBD Transport Provides transfer of data between end points Network Layer Security Provides secure communications, while still allowing networking functionality TBD Network protocols for data forwarding at the packet level Use of common higher level protocols/applications over heterogeneous links. TBD Network Study Link Link layer switching (ie, “virtual channels”) Frame level data accounting Coding and Modulation Allows for bitstream services Study Complete / International Dialog Underway Spectrum Resolves issues of RFI Allows re-use of Front End RF Hardware 13 March 2008 * International Standards prime consideration

Initial Service Set - service data unit view: Earth-Based Return and Forward Service Provision Space Packet File Radiometric Validated Application Delta-DOR Space Packet Application File Radiometric Transport Transport Internetworking Packet Internetworking Packet Network Network CLTU All Frames Channel Frames Bit-stream Link Unframed Telemetry Link Bit-stream Physical Raw Radiometric Physical FORWARD RETURN Service Production 13 March 2008

Forward data delivery services: Anticipated Service Set mapping to NASA Networks: Earth-Based Return and Forward ** DSN SN GN Forward data delivery services: Forward File (CFDP) Forward Space Packet Internetworking Forward CLTU (TC Frame, AOS Frame, octet-stream) Forward Bitstream* Return data delivery services: Return File (CFDP) Return Space Packet Return All Frames; Return Channel Frames Return Unframed Telemetry Return Bitstream* Radiometric services: Raw radio metric data Validated radio metric Delta-DOR Positioning &Timing services: Position Determination Time Determination (Clock Correlation, Time distribution) L L L L L L * Deprecated DSN services; provided only to legacy missions ** “GN” has been renamed “NEN” Current capability Planned Upgrade Proposed addition No planned service Deprecated Local standard Source: Mike Kearney L 13 March 2008 36

Lifecycle View Source: Erik Barkley 13 March 2008

User View of Mission Formulation Phase Mission User: Establish “legitimacy” of mission to negotiate with Provider Network (via registration, inter-agency agreement …) Discover (identify, find, browse for, already know about …) services that are available from a Provider Network to meet mission objectives Provider Network: Establish and maintain catalog of services Provide access to the Service Catalog through a standard interface Analyze user objectives Confirm intention to negotiate support Source: Erik Barkley 13 March 2008

User View of Mission Design Phase Mission User: Define requirements and configuration profiles (what, when, how much … ) Negotiate for support via Service Agreement Possibly revise requirements to meet available services Possibly arrange for new or modified services from Provider Provider Network: Assess feasibility of meeting mission requirements and schedule Agree to terms of Service Agreement Source: Erik Barkley 13 March 2008

User View of Mission Operations Phase Mission User: Request specific instances of support (Service Packages) Times, data rates, link parameters, flexibility React to Provider Network responses Possibly revise requests to meet available times, etc. Accept or cancel proposed support Provider Network: Assess service requests Support or deny request Commit resources to support service package Provide mutually-agreed services Source: Erik Barkley 13 March 2008

Ground-Based Earth Element 2006 ~2017 2030 RLEP missions Lunar exploration - sorties, outpost Mars human exploration Earth Polar, LEO, GEO missions, and ELV Earth LEO-GEO & Near Earth Missions Deep space missions Build-up of downlink antenna arrays supporting missions above GEO distance Downlink arrays in steady state for missions support Gradual decommission of large aperture DSN antennas Dedicated stations support Polar missions, Launch Head, and other LEO-GEO & Near Earth Missions 13 March 2008

MIXED FLEET AND CAPABILITIES Near Earth Relay Element F11 BOL 2015 F13 BOL 2017 F12 BOL2016 F14 BOL 2018 F3 2010 EOL Current Constellation Future Constellation Transition Overlap MIXED FLEET AND CAPABILITIES 2030+ S-Band Demand Access (300 KBS) S-Band Demand Access Enhanced Single Access - S-band (6 MBS) - Ku-Band (300 MBS) - Ka-band (300 MBS) 3 sats - S-band (6 MBS) - Ka-band (.6 – 1.2 Gbps) Possible signal performance (6 dB+ forward/3dB+ return) Global Coverage & Some Extended Coverage Beyond LEO Bent-pipe Design 2 Ground Terminals (WSC & Guam) 2 Ground Terminal locations Web-based Scheduling IP/SLE Connectivity NASA wide Service Mgmt Protocol 2015 2006 Ground Obsolescence & Upgrades F5 * F6 EOL 2015 F8 EOL 2019 F9 EOL 2017 F7 EOL 2019 F4 EOL 2007 F10 EOL 2019 WSC Terrestrial Network GT 2 GT 1 Guam GT GT #2 Satellite Attrition Satellite Replenishment

Human Exploration Global Sortie Access South Pole Outpost Lunar Relay Element Robotic Exploration Human Exploration Global Sortie Access South Pole Outpost RLEP2 RLEP3 Sortie-2 Sortie-1 Sortie-3 Sortie-N South Pole Outpost Visit 1 Lunar CEV Fly-by + South Pole Outpost Visit 2 Relays are deployed incrementally: # of relays, Coverage and Capability is responsive to mission evolution RLEP4 RLEP relays used to mature technology and components for relay satellite capability at beginning of Human Sortie Phase Global Capability Option: Possible with 6-relay constellation that provides continuous global lunar coverage Focused South Pole Outpost: Can be supported by an elliptical orbit constellation of two relays providing continuous coverage Scalability: Numerous intermediate solutions available to meet mission needs 13 March 2008

Mars Relay Element ... ... (Evolves with Missions) Robotic Exploration Human Exploration MER PHX MSL Scout AFL Scout Network Landers Sample Return First Human Landing ... ... MGS ODY MRO MSTO Mars Areostationary Relay Satellites Phase 1 Mars Relay Architecture: Science/Telecom Hybrid Relay Orbiters Standardized relay payload flown on each planned science orbiter Cost-effective strategy to grow Mars Relay infrastructure Increased data return and imrpoved energy-efficiency relative to direct-to-Earth communications Orbit characteristics constrained by primary science mission goals Spacecraft design and consumables for long extended relay ops Phase 2 Mars Relay Architecture: Dedicated Telesats Redundant, continuous coverage of human landing site Higher-performance access link and trunk line capabilites to meet human era comm/nav rqmts Detailed Phase 2 orbit design will be responsive to human mission design and detailed comm/nav requirements; areostationary option shown for reference Software defined relay radio represents key architectural building block Supports evolution of comm protocols over orbiter lifetime Enables infusion of new capabilities in response to emerging technologies (e.g., improved coding) Allows flexible response to unanticipated mission needs 13 March 2008

Baseline distance known Navigation Architecture 1 2-way coherent ranging originated by User 2 2-way coherent ranging originated by Relay 1 2 2 1 1 2 2 1 2-way coherent originated by GT 2-way coherent originated by GT 3 1-way Doppler to Relay 4 1-way Doppler to User 1-way Doppler to GT 1-way to User 5 VLBI, Very Long Baseline Interferometry 6 Earth orbiters can use GNSS up to GEO Triangulate on User Triangulate on Quasar Baseline distance known Users achieve precise Orbit with GNSS & Autonomous operations 13 March 2008

Security Architecture Source Encrypt – Destination De-Crypt 13 March 2008

Spectrum Framework 13 March 2008

Spectrum Framework Separate TT&C and mission data spectrum bands identified for any user throughout the solar system. Link TT&C/Mission Band Uplink/Forward Downlink/Return Earth Vicinity To/From Earth (Direct-to-User) *Requires a new allocation in the ITU (in process). TT&C S 2025-2110 MHz 2200-2290 MHz Mission Ka 22.55-23.55 GHz* 25.5-27 GHz Earth Relay Orbiter Trunk Line Ku 14.6-15.225 GHz 13.4-14.05 GHz Earth Relay to Earth Orbital User 22.55-23.55 GHz Lunar Vicinity *Requires a new ITU allocation (in process). Lunar Relay Orbiter Trunk Line **This use is subject to SFCG Rec. 14-2R5 which assigns priority to deep space in the 37-37.5 GHz portion of the band. 40-40.5 GHz 37-38 GHz** Lunar Relay to Lunar Surface or Orbital User t Relay Emergency Only TT&C t Lunar Relay to Lunar Relay Xlink *** Allocated for Space to Earth and Earth to Space. Must operate on a non-interference basis with other services allocated to the band. Non-interference is feasible since operational mitigation is practical. 37-38 GHz*** Mars Vicinity To/From Earth (Direct–to-User) X 7145-7190 MHz 8400-8450 MHz 34.2-34.7 GHz 31.8-32.3 GHz Mars Relay Orbiter Trunk Line 37-38 GHz Mars Relay to Mars Surface or Orbital User * User link spectral bands are located “near” trunk line bands but far enough away in frequency to not cause interference on the relay satellite UHF 435-450 MHz 390-405 MHz Near* 7145-7190 MHz Near* 8400-8450 MHz Near* 34.2-34.7 GHz Near* 31.8-32.3 GHz 13 March 2008