interplanetary internet - its · pdf fileintranet internet space link protocols end-to-end ......

InterplanetaryInternet

Adrian J. HookeJet Propulsion Laboratory

California Institute of Technology

2000 Third Annual International Symposium on Advanced Radio Technologies

Boulder, CO, 08 September 2000

Member Agencies

ASI/ItalyBNSC/UKCNES/FranceCSA/CanadaDLR/Germany

NASDA/Japan

ESA/EuropeINPE/BrazilNASA/USA

RSA/Russia

Observer Agencies

ASA/AustriaCAST/ChinaCRC/CanadaCRL/JapanCSIR/South AfricaCSIRO/Australia

IKI/RussiaISAS/JapanISRO/IndiaKARI/KoreaKFKI/HungaryMOC/Israel

NOAA/USANSPO/TaipeiSSC/SwedenTsNIIMash/RussiaUSGS/USA

CTA/BrazilDSRI/DenmarkEUMETSAT/EuropeEUTELSAT/EuropeFSST&CA/BelgiumHNSC/Greece

Industry Associates ISO/TC20/SC13

Liaisons

PPAANNEELL 33

CROSSSUPPORT

OPERATIONS

PPAANNEELL 22

INFORMATIONINTERCHANGEPROCESSES

SPACECOMMUNICATIONS

PPAANNEELL 11

MANAGEMENTMANAGEMENTCOUNCILCOUNCIL

Consultative Committee for Space Data Systems (CCSDS)

Technical Steering GroupSecretariat

CCSDS Panel Work

Intranet Internet

Space LinkProtocols

End-to-EndProtocols

CCSDS Panel 1

Space LinkExtension Protocols

CCSDS Panel 3

Data Description& Archiving

CCSDS Panel 2

Radio Frequency and ModulationP1E

LinkARQ

TM Space DataLink Protocol

AOS Space DataLink Protocol

Proximity 1 SpaceData Link Protocol

TC Space DataLink Protocol

CommunicationsOperation

Procedure 1

Space DataLink SecurityMechanisms

P1A

P1F Internet IPSecSpace Security Protocol

Space PacketProtocol

Space NetworkProtocol

Internet Protocol(IPv4, IPv6)

P1B Reed-SolomonCoding

BCH CodingConvolutionalCoding

TurboCoding

TLM FrameSync.

CLTU andPLOPs

Synchronous Links Asynchronous Links

Current CCSDS Space/Ground Communications Protocol Stack

Physical

Link

Network

Transport

Application

CCSDSFile

DeliveryProtocol(CFDP)

Storeand

Forward

InternetTCP/UDP

SpaceTCP/UDP

Interactive

SpaceFTP

InternetFTP

Internet RFCDraft CCSDS RecommendationCCSDS Recommendation CCSDS Report

http://hope.gsfc.nasa.gov/ccsds/implementations/

151 Missions10 COTS Spacecraft16 COTS Space Products 2 COTS Ground Networks28 COTS Ground Products

1970 1980 1990 2000

International Space StationExtension ofStandards forMore ComplexSpace Missions

}Extension of the

Terrestrial Internetinto Space

Basic Space/GroundCommunicationsStandards forSpace Missions

} Consultative Committee for Space Data Systems (CCSDS)

NASA Telemetry Standardization

NASA/ESAWorking Group

“Packet” Spacecraft Telemetry and Telecommand

NASA/DOD SpaceCommunications Protocol Standards (SCPS) Project

Evolution of space standards

InterPlaNetaryInternet (IPN)

Evolution of the terrestrial Internet

Today’sInternet:

High rate fiber backboneNegligible delayNegligible errors

Symmetric data channelsContinuous connectivity

Loss = Congestion

Tomorrow’s“Earthnet”

U n t e t h e r e d e d g e- marke t

‘p lug- i n s ’ t o t h e f i b e r b a c k b o n e

[ s a t e l l i t e s , w i r e l e s s , m o b i l e

ad- h o c n e t w o r k s , e t c . ]

m a y i n t r o d u c e :Significant delay & errors

Power/bandwidth constraintsDisjoint connectivity

Corruption as source of lossAsymmetric channels

Surfaceto Orbit

Relay

SurfaceOperations

LongHaul toEarth

Mars

Moon

Satellite,Wireless

Internetbackbone

Mobile/Rovingapplications

Earth

A Candidate Sharing of Issues A Candidate Sharing of Issues and Technologiesand Technologies

• Generally high bandwidth-delay products• Possible data loss due to bit-errors and/or

transient link outages• Potentially asymmetric data rates

• Power constrained end systems• Episodic/disjoint connectivity• Networks may need to be self-organizing

• Ultra high bandwidth-delay product• typically >> transaction size

• ‘Ping-pong of bursts’ replaces streaming

• Channels often periodically unidirectional• Need for progressive/selectable reliability• Need for store-and-forward delivery

Similar Problems,Common Solutions

Fiber Satellites

Cable

Mobile/Wireless

WDM

Nomadic

Terabit communicationslow delay

Self-organizing

FTP/TCP/IP

Short-haul comm

unications

TerrestrialInternetStandards

IPN leverage

S-band X-bandKa-band

LEOConstellations

MarsNetwork

Deep-spaceOptical

Megabit communicationshigh delay

Long-haul c

omm

unicatio

ns

SpaceInternetStandards

File-basedOperations

Thirty years down the road…..

IPNSIGPublic

USC

UCLA

UDEL

UMD

Caltech

IPN ArchitectureCore Team

IPN Organizational Relationships

NASAProjects

DARPAProjects

IPNRG

Robert Rumeau - FranceEric Travis - USA

Open ArchitectureOpen SpecificationsOpen ImplementationsDemonstrations

The Basic IPN Concept:

Construct a “Network of Internets”

• Deploy standard internets in low latency remote environments (e.g., on other planets, on remote spacecraft)

• Connect these distributed internets via an interplanetary backbone that handles the high latency deep space environment.

• Create gateways and relays to interface between low and high latency environments

The Basic IPN Concept:construct a

“Network of Internets”

Deploy standard internets in low latency remote environments (e.g., on other planets)

Connect distributed internets via an interplanetary backbone

Provide dialog acrossa network of Internets

DeployedInternets

StableBackbone

Security

InterplanetaryGateways

Inter-InternetDialog and Nodes

IPN Technology Thrust Areas

Wired

Tetherlessi

I

e a r t h . s o l

IG

IG

IGIG

IG IG

Ii

iii

ii

ii

i ii

iI

i

ii

i I

iii I

m a r s . s o l l u n a . s o l

IPN Security

Security of user data flowing through the IPN

Security of the IPN backbone

DeployedInternets

StableBackbone

Security


Inter-Internet Dialogand Nodes

IG

IG

IGIG

IG IG

Ii

iii

ii

ii

i ii

iI

i

ii

i I

iii I

m a r s . s o l l u n a . s o l

e a r t h . s o l

Ø access control to the IPN will be required because space-based assets will have limited available resources.

Ø authentication will be required to perform access controls.

Ø data integrity will be required to assure that what wassent is received.

Ø data privacy will be required to assure that unauthorized users cannot obtain information.

DeployedInternets

StableBackbone

Security



Deployed In-Situ Internets

UntetheredMobile

Mass constrainedLocation-Location-Location

Power-Power-Power

What’s a Backbone?

Ø A set of high-capacity, high-availability links between network traffic hubs

– Terrestrial backbone links are between hubs like Houston and Chicago.

– Interplanetary backbone links are between hubs like Earth and Mars.

DeployedInternets

StableBackbone

Security



On the Interplanetary Backbone:

• Communications capacity is expensive

– Bits count

• Round Trips hurt

– Interactive protocols don’t work• Internet protocol suite doesn’t scale well with increasing latency• Negotiation is impractical• Reliable in-order delivery takes too long• Protocols need to be connectionless• Congestion control and flow control are difficult• Reliance on forward coding versus retransmission for error recovery

• Custodial store-and-forward data transfer is fundamental

– “Chatty Telephony” gives way to “Bundled Mail” as the model of operations

Resulting Backbone Differences

Transport

Network

Link

Physical

TerrestrialBackbone

TCP

IP

SONET

Optical fiber

InterplanetaryBackbone

“Bundling”

IP, NP, None?

CCSDS

R/F or laser

App

App

App App

App

App

NetworkIP

TransportTCP

NetworkIP

TransportTCP

NetworkIP

NetworkIP

Link. 1

Phys. 1 Phys. 2

Link. 2

Phys. 2

Link. 2

Phys. 3

Link. 3

Phys. 1

Link. 1

Phys. 1

Link. 1

Sub-network Sub-network Sub-network

IP: the “Thin Waist” of the Earth’s Internet

Internet: a Network of Connected Sub-Networks

Bundling supports end-to-end transfer across a “network of disconnected Internets”

having heterogeneous network protocol stacks

Bundle

Application Application

Transport Transport

Network Network

Transport

Network

Transport

Network

BundleBundle Bundle

Network of disconnected Internets spanning dissimilar environments

Bundles: A Store and Forward Overlay -the “Thin Waist” of the Interplanetary Internet

Bundling:Design Principles

• Names are the means of reference

– Names have two parts: a routing part (specifies the IPN region) and an administrative part (specifies the DNS name)

– Routing between IPN regions based upon routing part of the name

• Late-Binding

– Separate addressing domains for each internet; administrative names converted to local addresses in destination IPN region

• Indirection

– Inherent dependence on intermediate relay agents

• Custodial transfer

– “Bundles” are the common end-to-end transfer mechanism

DeployedInternets

StableBackbone

Security



Single Name Space,Late Name-to-Address Binding(s)

Internet InternetInterplanetaryBackbone

Name-to-AddressBinding Space A

Name-to-Address Binding Space B

Name-to-Address Binding Space C

Name Space - Common Across All Internets

IPN Region: .mars.solIPN Region: .earth.sol IPN Region: .ipn.sol

Name:{routing part: mars.sol,

admin part: http://www.rockshop.com}

Local Address: 137.79.10.232

Name:{routing part: earth.sol,

admin part: http://www.bughunter.org}

Local Address: 137.79.10.232

Basic IPN Architectural Definition

Development of Key Protocols

New Capability Demonstrations

Space Mission Infusion and Rollout

Protocol Test and Validation

Ba

sic

R&

DS

po

ns

ore

dR

oll

ou

t

Interplanetary Internet Deployment Plan

Earth Vicinity,2001

Lunar Vicinity,2002

Mars2003+

InterplanetaryInternet, “2020”

InterplanetaryBackbone


interplanetary internet - its · pdf fileintranet internet space link protocols end-to-end ......

Documents