nasa-1 space communications and navigation office nasa’s concept: “international space...

nasa-1

Space Communications and Navigation Office

NASA’s Concept:NASA’s Concept:““International Space Communications International Space Communications

and Navigation Networkand Navigation NetworkService Architecture”Service Architecture”

Drawn from Rush / Hooke Presentation to IOAG-11June 19, 2007, Cebreros, Spain

Presented to CCSDS Cross Support Service Architecture BoFPeter Shames, 13 March 2008

NASA Consolidated Network Services TeamSpace Communications and Navigation Office

NASA Headquarters

13 March 2008 nasa-2

Earth Local Network

Martian Local Network

Lunar Local Network

Martian Trunk

LunarTrunk

L1/L2

IndividualSpacecraftConnections

Top LevelSpace Communications & Navigation Architecture


Cross Support Interfaces

Source: NASA IOAG Internetworking Proposal


BackgroundBackground

• 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/

nasa-5

SN

GN

DSN Goldstone

Complex Canberra

Complex

MadridComplex

NISN

NetworkOperations

ControlCenter(NOCC)

WallopsOrbital

TrackingInformation

System (WOTIS)

NetworkControlCenter(NCC)

White Sands Ground Terminal

Second TDRSS Ground Terminal

Guam Remote Ground Terminal

Mission Operations

Center

Mission Operations

Center

Mission Operations

Center

Mission Operations

Center

Mission Operations

Center

• Network-specific service interfaces

• Network-specific service management interfaces

• Network-specific service interfaces

Description of Description of The Present Service ArchitectureThe Present Service Architecture

nasa-6

SN

GN

DSN Goldstone

Complex Canberra

Complex

MadridComplex

NISN

NetworkOperations

ControlCenter(NOCC)

WallopsOrbitingTracking

InformationSystem(WOTIS)

NetworkControlCenter(NCC)

White Sands Ground Terminal

Second TDRSS Ground Terminal

Guam Remote Ground Terminal

Mission Operations

Center

Mission Operations

Center

Mission Operations

Center

Mission Operations

Center

• Standard service interfaces

• Standard service management interfaces

• Standard service interfaces

Enterprise Service

ManagementFunction

Description of Description of The Future Service ArchitectureThe Future Service Architecture


ControlCenters

Earth Ground Stations

Relays EndUsers

(Remote)

EndUsers(Earth)

NASA SPACE COMMUNICATIONS NETWORK

Data Flow

Information Flow

Conceptual scope of NASA’s NetworksConceptual scope of NASA’s Networks

Source: Dave Israel

13 March 2008 nasa-8Space Communications Path

Layer (n) Layer (n)

Layer (n+1) Layer (n+1)

Layer (n-1) Layer (n-1)

UserApplication

Service Access Service Access

UserApplication

EndUser

EndUser

NASA’s Layered Protocol ConceptNASA’s Layered Protocol Concept

“on-ramps” for accessing protocol

services


UserEndSystem

UserEndSystem

EndUser

(Remote)

EndUser

(Earth)

ApplicationService

NetworkService

LinkService

PhysicalService

TransportService

ApplicationService

NetworkService

LinkService

PhysicalService

TransportService

UserApplication

UserApplication

NASA’s view: Single Hop CommunicationsNASA’s view: Single Hop Communications

“on-ramps” for accessing protocol

services

Space Communications Path


UserEndSystem

UserEndSystem

EndUser

(Remote)

EndUser

(Earth)

ApplicationService

NetworkService

PhysicalService

TransportService

ApplicationService

NetworkService

PhysicalService

TransportService

PhysicalService

PhysicalService

UserApplication

UserApplication

RelaySystem

LinkService

LinkService

LinkService

LinkService

“Bent-pipe”

NetworkService

Relaying Application:Real Time or Store-and-Forward

NASA’s view: Multi Hop CommunicationsNASA’s view: Multi Hop Communications

Space Communications Path

“on-ramps” foraccessing protocol

services


NASA Space Communications Architecture:NASA Space Communications Architecture:where next?where next?

What concept unites all of these views into a cohesive,consolidated “network of networks”?


MissionUser

MissionUser

Space CommunicationSpace Communicationand and

Navigation ServicesNavigation Services

NASA’s Concept:NASA’s Concept:provide “any-to-any” services …provide “any-to-any” services …


MissionUser

MissionUser

International SpaceInternational SpaceCommunicationsCommunicationsand Navigationand Navigation

Service InfrastructureService Infrastructure

… … via an via an InternationalInternational Service Infrastructure … Service Infrastructure …

13 March 2008 nasa-14April 21, 2023

International Space Communications and Navigation

Service Infrastructure

SpaceMission

UserSpaceMission

User SpaceMission

User

SpaceMission

User

… … offering standard service interfacesoffering standard service interfaces

Source: Mario Merri/Mike Kearney

StandardServices

StandardServices

StandardServices

StandardServices

StandardServices


There are multiple phases involvedThere are multiple phases involvedwith providing space communications and navigation serviceswith providing space communications and navigation services

MissionUser

DiscoverDiscoverCapabilitiesCapabilities

NegotiateNegotiateSupportSupport

ProvideProvideServicesServices

MissionFormulation

Phase

MissionDesignPhase

MissionOperations

Phase


Options

Provide

Select

ServiceServiceProviderProvider

MissionUser

User/provider negotiations involveUser/provider negotiations involvethe selection and refinement of the selection and refinement of service optionsservice options


MissionUser




MissionFormulation

MissionDesign

MissionOperations

ServiceCatalog

Provide

Select

ServiceCapabilityProvider

MissionUser

ServiceAgreements

Provide

Select

ServicePackageProvider

MissionUser

ConfigurationProfiles

Provide

Select

ServiceProvider

MissionUser

Activities across all PhasesActivities across all Phasesshould follow a principle of should follow a principle of successive successive refinementrefinement


Mission UserService Provider

Mission Formulation Phase:Mission Formulation Phase:ddiscover available services; certify and register authorized usersiscover available services; certify and register authorized users

SMI/F

ServiceManagement

Interface

Service Discovery Functions Service Discovery Activities

Mission Formulation

Manager

SMI/FService

Catalog

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 “M” user requests authority to enter exploratory support discussions.Users x, y and z are validated and authorized to negotiate during formulation phase

example:

(Backgroundadministrativenegotiation)



Service Negotiation Activities

ConfigProfile

DB

Service Negotiation Functions

ConfigProfile

DB

ServiceAgreement

DB

ServiceAgreement

DB

Mission Formulation

Manager

Network Engineering

NetworkIntegrationManager

Mission Design Phase:Mission Design Phase:negotiate service agreement; create configuration profilesnegotiate service agreement; create configuration profiles

SMI/F

SMI/F

ServiceCatalog

ServiceManagement

Interface

(Backgroundadministrativenegotiation)

“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”

example:

“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:



Service Providing Resources

Service Users

Provider Scheduling andExecution Functions

Networkscheduling

SMI/F

SMI/F

Missionscheduling

Mission planningEquipment configuration,

control, monitoring

ConfigProfile

DB

ServiceAgreement

DBConfigProfile

DB

ServiceAgreement

DB

Service UtilizationInterface

Mission Planning, Scheduling and Execution Functions

Mission Operations Phase:Mission Operations Phase:Provide ServicesProvide 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”

1. Raw Radiometric service 2. Forward CLTU telecommand service3. Return All Frames telemetry service

FDF1

2

3

example:

example:

ServiceManagement

Interface

MissionPlanningManager

MissionUser

StationS67


NASA’s Proposed ApproachNASA’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


NASA’s NASA’s InitialInitial Scope Scope

PrimaryInitialScope

• 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


Current state of the art forCurrent state of the art forstandard capabilitiesstandard capabilities




MissionFormulation

Phase

MissionDesignPhase

MissionOperations

Phase

MissionUser

• Full specification of basic “SLE” data transfer servicesFull specification of basic “SLE” data transfer services• Growing deployment communityGrowing deployment community

• Service Management nearing initial StandardService Management nearing initial Standard• Prototypes under testPrototypes under test

• Generalization and expansion intoGeneralization and expansion into “Cross Support “Cross Support Transfer Services”, including Radiometric and MonitoringTransfer Services”, including Radiometric and Monitoring

• Service Management defines Configuration Profiles Service Management defines Configuration Profiles to specify fixed or alternative mission parameters to specify fixed or alternative mission parameters

• Service Management defines some content of Service Management defines some content of Service AgreementsService Agreements• But no process for negotiating that contentBut no process for negotiating that content

• No uniform way to:No uniform way to:• obtain knowledge of network capabilitiesobtain knowledge of network capabilities• describe network services.describe network services.• negotiate or document mission supportnegotiate or document mission support

Key: ExistsExistsEmergingEmergingDoes not existDoes not exist





MissionFormulation

Phase

MissionDesignPhase

MissionOperations

Phase

MissionUser

• Cross Support Transfer Services (CSTS) and Cross Cross Support Transfer Services (CSTS) and Cross Support Service Management (CSSM) standards complete –Support Service Management (CSSM) standards complete –

• Ready for widespread deployment and operational use across Ready for widespread deployment and operational use across international networksinternational networks

• Expansion to Lunar and Mars Relays and Expansion to Lunar and Mars Relays and internetworked operationsinternetworked operations

• Fully standardized process defined for negotiating Fully standardized process defined for negotiating network support via Service Agreementsnetwork support via Service Agreements

• XML-based Service Agreements and Configuration XML-based Service Agreements and Configuration Profiles defined and ready for operational useProfiles defined and ready for operational use

• Expansion to Lunar and Mars Relays and Expansion to Lunar and Mars Relays and internetworked operationsinternetworked operations

• Fully standardized process defined for initial negotiation of Fully standardized process defined for initial negotiation of network supportnetwork support

• Internationally agreed Cross support Service Catalog defined Internationally agreed Cross support Service Catalog defined and ready for operational use, providing access to uniformly-and ready for operational use, providing access to uniformly-described service offerings of Agency networksdescribed service offerings of Agency networks

• Expansion to Lunar and Mars Relays and internetworked Expansion to Lunar and Mars Relays and internetworked operationsoperations

Goal forGoal forstandard capabilitiesstandard capabilities

Key: ExistsExistsEmergingEmergingDoes not existDoes not exist


Service Provider

Service P

rovis

ion

Mission User

Service Users

First Step - Mission Operations Phase:First Step - Mission Operations Phase:initial Earth-Based “initial Earth-Based “Service SetService Set””

MissionUserService

UtilizationInterface

SUI/F

SUI/F

SMI/F

SMI/FService

ManagementInterface

Service Production

Positioning& TimingServices

RadiometricServices

ReturnData Delivery

Services

ForwardData Delivery

Services


Initial Service Set:Initial Service Set:Earth-Based Return and ForwardEarth-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• Internetworking• 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)


Physical

Sp

ace

Pac

ket

Link

Network

CL

TU

Application

File

Inte

rnet

wo

rkin

g P

acke

t

Transport

FORWARD

Sp

ace

Pac

ket

All

Fra

mes

Ch

ann

el F

ram

es

Link

Inte

rnet

wo

rkin

g P

acke

t

Network

Transport

File

Application

Un

fram

ed T

elem

etry

RETURN

Raw

Rad

iom

etri

c

Bit

-str

eam

Bit

-str

eam

Del

ta-D

OR

Physical

Val

idat

edR

adio

met

ric

Po

sit

ion

Tim

e

Pos&

Time

Service Provision

Service Production

Radiometric

Initial Service Set - service data unit view:Initial Service Set - service data unit view:Earth-Based Return and ForwardEarth-Based Return and Forward


Current capabilityPlanned UpgradeProposed additionNo planned serviceDeprecatedLocal standard

Current Standard Service Set mapping to NASA Networks:Current Standard Service Set mapping to NASA Networks:Earth-Based Return and ForwardEarth-Based Return and Forward

• 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• Internetworking• Return All Frames; Return Channel Frames• Return Unframed Telemetry• Return Bitstream*


• Positioning &Timing services:• Position Determination• Time Determination (Clock Correlation, Time distribution)

Source: Mike Kearney

* Deprecated DSN services; provided only to legacy missions** “GN” has been renamed “NEN”

L

L L

L LL

L

L LL

L

L

L

L LL

L LL

**


Communication ViewCommunication View Example – RAF ServiceExample – RAF Service

NASA Space Communications Infrastructure

Mission Ground Element

Ground RAF Utilization

SLE RAF TS

TCPIP

SLE IPTS

NISN Link

NISN Physical

NISN

NISN Link

NISN Phys

NISN Link

NISN Phys

IP Routing

Mission Space Element

Space RAF Utilization

Mission Ground Application

RF & Modulation

Mission Space Application

RAF Provision

RF & Modulation

SLE RAF TS

TCPIP

SLE IPTS

NISN Link

NISN Physical

NASA Space Communications Network

Ground Station/Relay Satellite

AF ReceptionAF Generation

IP IP

R-S or Turbo encode

Attach ASM

conv encoding

P-R Seq Gen

R-S or Turbo decode

Frame Synchconv decoding

P-R Seq Rem


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

Proposed Next StepsProposed Next Steps


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

nasa-32

SupplementarySupplementaryMaterialMaterial

Space Communications and Navigation Office


Overall Architecture

Earth-basedAntenna Element

LunarRelay

SatelliteElement

Earth-basedRelay

SatelliteElement

MarsRelay

SatelliteElement

Spectrum Framework

Security Architecture

Networking Architecture

Navigation Architecture

ELEMENT ARCHITECTURES

CR

OS

SC

UT

TIN

G A

RC

HIT

EC

TU

RE


State of Interoperable Framework Development

Spectrum •Resolves issues of RFI•Allows re-use of Front End RF Hardware

Coding and Modulation •Allows for bitstream services

Network

Link •Link layer switching (ie, “virtual channels”) •Frame level data accounting

•Network protocols for data forwarding at the packet level•Use of common higher level protocols/applications over heterogeneous links.

Network Layer Security •Provides secure communications, while still allowing networking functionality

Transport •Provides transfer of data between end points

Application Layer Security •Provides secure communications transparently to the lower layers

Middleware •Provides common application interfaces over heterogeneous lower layers

Application •Provides services such as file delivery or time service

Complete /International Dialog Underway

Study

TBD

Study

TBD

TBD

TBD

TBD

TBD

Status Layer* Notes

* International Standards prime consideration


Initial Service Set - service data unit view:Initial Service Set - service data unit view:Earth-Based Return and ForwardEarth-Based Return and Forward

Physical

Sp

ace

Pac

ket

Link

Network

CL

TU

Application

File

Inte

rnet

wo

rkin

g P

acke

t

Transport

FORWARD

Sp

ace

Pac

ket

All

Fra

mes

Ch

ann

el F

ram

es

Link

Inte

rnet

wo

rkin

g P

acke

t

Network

Transport

File

Application

Un

fram

ed T

elem

etry

RETURN

Raw

Rad

iom

etri

c

Bit

-str

eam

Bit

-str

eam

Del

ta-D

OR

Physical

Val

idat

edR

adio

met

ric

Service Provision

Service Production

Radiometric


Anticipated Service Set mapping to NASA Networks:Anticipated Service Set mapping to NASA Networks:Earth-Based Return and ForwardEarth-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• Internetworking• Return All Frames; Return Channel Frames• Return Unframed Telemetry• Return Bitstream*


• Positioning &Timing services:• Position Determination• Time Determination (Clock Correlation, Time distribution)

Source: Mike Kearney

L

L

LL

L L

Current capabilityPlanned UpgradeProposed additionNo planned serviceDeprecatedLocal standard L

**

* Deprecated DSN services; provided only to legacy missions** “GN” has been renamed “NEN”


Lifecycle ViewLifecycle View

Source: Erik Barkley


User View of Mission Formulation PhaseUser View of Mission Formulation Phase

• 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

• 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



User View of Mission Design PhaseUser View of Mission Design Phase

• Provider Network: • Assess feasibility of meeting mission

requirements and schedule • Agree to terms of Service Agreement

• 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



User View of Mission Operations PhaseUser View of Mission Operations Phase

• Provider Network: • Assess service requests • Support or deny request• Commit resources to support service

package• Provide mutually-agreed services

• 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



Ground-Based Earth Element

2006 2030~2017

Deep space missions

Earth Polar, LEO, GEO missions, and ELV

RLEP missions

Earth LEO-GEO & Near Earth Missions

Mars human exploration

Lunar exploration - sorties, outpost

Dedicated stations support Polar missions, Launch Head, and other LEO-GEO & Near Earth Missions

Gradual decommission oflarge aperture DSN antennas

Build-up of downlink antenna arrays supporting missions above GEO distance

Downlink arrays in steady state for missions support

nasa-42

Near Earth Relay Element

F11BOL 2015

F13BOL 2017

F12BOL2016

F14BOL 2018

F32010 EOL

Current Constellation Future ConstellationTransition 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

Single Access- 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

Global Coverage & Some Extended Coverage Beyond LEO

Bent-pipe Design Bent-pipe Design

2 Ground Terminals (WSC & Guam) 2 Ground Terminal locations

Web-based Scheduling

IP/SLE Connectivity

NASA wide Service Mgmt Protocol

20152006

Ground Obsolescence & Upgrades

F5 *

F6 EOL 2015

F8 EOL 2019

F9 EOL 2017

F7 EOL 2019 F4

EOL 2007

F10 EOL 2019WSC

Terrestrial Network

GT 2

GT 1

Terrestrial Network

Guam GT

GT #2

Satellite Attrition Satellite Replenishment


Robotic Exploration Human ExplorationGlobal Sortie Access South Pole Outpost

RLEP2

RLEP3

Sortie-2Sortie-1 Sortie-3 Sortie-N South PoleOutpostVisit 1

Lunar CEVFly-by

+

+

+

South PoleOutpostVisit 2

+

Relays are deployed incrementally: # of relays, Coverage and Capability is responsive to mission evolution

RLEP4

Orbit SMA 9250 km SMA ; Period 22 hrOrbit SMA 9250 km SMA ; Period 22 hr

RLEP relays used to mature technology and components for relay satellite capability at beginning of Human Sortie Phase

Orbit SMA 6541 km; Period 13.2 hrOrbit SMA 6541 km; Period 13.2 hr

Global Capability Option: Possible with 6-relay constellation that provides continuous global lunar coverage

Focused South PoleOutpost: Can be supported by an elliptical orbit constellation of two relays providing continuous coverage

+

Scalability:Numerous intermediate solutions available to meet mission needs

Lunar Relay Element


Robotic Exploration Human Exploration

MGSODY MRO

First Human Landing

MSTO

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

Scout AFL NetworkLanders

Sample Return

MER PHX MSL Scout

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

...

Mars Areostationary Relay Satellites

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

...

Detailed Phase 2 orbit design will be responsive to human mission design and detailed comm/nav requirements; areostationary option shown for reference

Mars Relay Element(Evolves with Missions)


1-way Doppler to GT

1-way Doppler to Relay

2-way coherent originated by GT

2-way coherent ranging originated by Relay2

1

1

2

2

2-way coherent originated by GT

2-way coherent ranging originated by User1

1

2

21

1-way to User

1-way Doppler to User4

Baseline distance known

VLBI, Very Long Baseline Interferometry5

Triangulate on QuasarTriangulate on User

Navigation Architecture

Earth orbiters can use GNSS up to GEO

Users achieve precise Orbit with GNSS & Autonomous operations

6

3


GROUND NETWORK

END USER END-TO-END SECURITY

TT&C SUBSYSTEM

ON-BOARD PAYLOAD

NETWORK LAYER (IPSec)

APP LAYER (SSL)

Security Architecture

Source Encrypt – Destination De-Crypt


Spectrum Framework

Mission Data (Ka)

Earth Network

Martian Network

LunarNetwork (applies to

Lagrange Points)

Deep Space

Ground-based Earth

Element

Array

Near Earth Relay

Mars Relay

LunarRelay

GPS

TT&C (S)LV

Mission Data (Ka)

TT&C (S)

Mission Data (Ka)

TT&C (S)

Mission Data (Ka)

TT&C (X)

Time & Position (L)

TT&C & Mission

Data (Ka)

Emergency TT&C (S)

TT&C & Mission

Data (Ku)EmergTT&C

(S)

TT&C (S)

Mission Data (Ka)

Mission Data (Ka)

TT&C (S)

TT&C & Mission

Data (Ka)

TT&C (UHF)

Mission Data (near X)

Mission Data (Ka)

TT&C (X)

LunarOrbit User

MarsOrbit User

MarsSurface

User

EarthOrbit User

LunarSurface

User


Spectrum Framework

Link TT&C/Mission Band Uplink/Forward Downlink/Return

Earth

Vicin

ity

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 Ka22.55-23.55 GHz* 25.5-27 GHz

Earth Relay Orbiter Trunk Line TT&C S 2025-2110 MHz 2200-2290 MHz

Mission Ku14.6-15.225 GHz 13.4-14.05 GHz

Earth Relay to Earth Orbital User TT&C S 2025-2110 MHz 2200-2290 MHz

Mission Ka22.55-23.55 GHz 25.5-27 GHz

Lu

nar V

icinity

To/From Earth (Direct-to-User)*Requires a new ITU allocation (in process).

TT&C S 2025-2110 MHz 2200-2290 MHz

Mission Ka22.55-23.55 GHz* 25.5-27 GHz

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.

TT&C S 2025-2110 MHz 2200-2290 MHz

Mission Ka40-40.5 GHz 37-38 GHz**

Lunar Relay to Lunar Surface or Orbital Usert Relay Emergency Only

TT&C t S 2025-2110 MHz 2200-2290 MHz

Mission Ka22.55-23.55 GHz 25.5-27 GHz

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. Mission Ka 37-38 GHz*** 40-40.5 GHz

Ma

rs Vicin

ity

To/From Earth (Direct–to-User) TT&C X 7145-7190 MHz 8400-8450 MHz

Mission Ka34.2-34.7 GHz 31.8-32.3 GHz

Mars Relay Orbiter Trunk Line TT&C X 7145-7190 MHz 8400-8450 MHz

Mission Ka34.2-34.7 GHz 31.8-32.3 GHz

Mission Ka40-40.5 GHz 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

TT&C UHF 435-450 MHz 390-405 MHz

Mission X Near* 7145-7190 MHz Near* 8400-8450 MHz

Mission KaNear* 34.2-34.7 GHz Near* 31.8-32.3 GHz

Separate TT&C and mission data spectrum bands identified for any user throughout the solar system.

nasa-1 space communications and navigation office nasa’s concept: “international space...

Documents