Overview of the InterPlanetary

BroadSkyBroadSky WorkshopWorkshop 10th Ka and Broadband Communications Conference

Vicenza, Italy 01 October 2004

Adrian J. Hooke Interplanetary Network Directorate Jet Propulsion Laboratory, California Institute of 818.354.3063 [email protected] Roadmap of International Space Data Systems Standardization

1980 1990 2000 2010

Basic Space/Ground “Packet” Spacecraft Telemetry and Telecommand communications 02 January, 1996 STRV-1b standards for } Baselined by International IP address: all space missions Space Station and GN 192.48.114.156

Consultative Committee for Space Data Systems (CCSDS)

CCSDS Advanced Orbiting Systems

The : FTAM Dark File Transfer: FTP Transport: TP4 Age Transport: TCP Space Internetworking Of CCSDS in richly connected, Network: ISO 8473 GOSIP Network: IP. Mobile IP Proximity-1 short delay, stressed space environments NASA/DOD/CCSDS } Space Communications Next Generation Protocol Standards Space Internet (CCSDS-SCPS) Project (NGSI) Project Space Internetworking in sparsely connected, CCSDS File Delay Tolerant long delay, stressed Delivery Protocol Networking space environments }

Standardized Space CCSDS Space Link Extension CCSDS Spacecraft Mission Operations and Service Management Monitor & Control Services } Technical Areas of International Space Standardization

Space Internetworking Spacecraft Services Onboard Interface Services Mission Operations and Information Management Services Space Link Services

Cross Support Systems Services Engineering Constellation Free Flyer Orbiting Relay Space Link

Access Services

Internet Short-Haul Terrestrial Long-Haul Surface Proximity Internet Space Backbone Operations Operations

End-to-end Space Internetworking

Internet-based Long delay Short delay in-situ ground mission near- and proximity surface operations systems deep space links links links SPACE COMMUNICATIONS PROTOCOLS End-to-End Space Applications

Space Middleware

Space Application Services

Space Transport Services

Space Networking Services

Space Link Services

Space Long-Haul Data Link Space Proximity Data Link Space Surface Data Link

Space Long-Haul Coding Space Proximity Coding Space Surface Coding

Space Long-Haul Channel Space Proximity Channel Space Surface Channel SPACE COMMUNICATIONS PROTOCOL MODEL

Space Long Haul Space Proximity Space Surface 1980s - now: standard “Packet Telemetry/Telecommand” space links

Free Flyer

Orbiter Ground Long-Haul Proximity Surface Operations Space Backbone Operations Operations CCSDS Packet

CCSDS Long-haul Link CCSDS Space Link Extension (SLE)

TCP, UDP

IPSEC

IP

CCSDS Long-Haul Link and Coding Local Terrestrial Link CCSDS Proximity Link and Coding

Local CCSDS UHF; CCSDS CCSDS Terrestrial local wired/ S, X, Ka Band UHF Wired wireless 300 Missions now using CCSDS Space Link Protocols http://www.ccsds.org/CCSDS/missions.jsp Mid-1990s: a focus on space internetworking Free Flyer

Orbiter Ground Long-Haul Proximity Surface Operations Space Backbone Operations Operations CCSDS Packet

CCSDS Long-haul Link CCSDS Space Link Extension (SLE) TCP, UDP Upper Layer IPSEC Network - based Services?

IP

CCSDS Long-Haul Link and Coding Local Terrestrial Link CCSDS Proximity Link and Coding

Local CCSDS UHF; CCSDS CCSDS Terrestrial local wired/ S, X, Ka Band UHF Wired wireless Conventional Internetworking

• Richly connected • Continuous availability • Error free • Negligible delay • Symmetric channels • High data rates Typical Space Internetworking

• Intermittently connected (frequent service disruption) • Error prone • Significant-to-huge delay • Asymmetric or unidirectional channels • Constrained data rates CCSDS approach to extending the terrestrial Internet into space Proxy-Based Operation

ES ES ES ES ES GW Internet ES Internet GW ES ES “Proxy ES Space” ES ES ES

ES • Dual-gateway (proxy) configuration Internet • End System transport connections do not cross ES the satellite/wireless link so End Systems do ES ES not have to be satellite/wireless aware (e.g., can be unmodified COTS, simplifying

ES = End System deployment) GW = Transport Layer Gateway (Proxy) • Security above transport or via trusted gateways Current CCSDS Space Options

Space extensions Record read & record update; File & record Integrity; FP to FTP FP - - FTPFTP Other Apps Automatic restart; FeaturesFeatures FTP User suspend/resume; SCPS Space extensions SCPS Suppress ASCII reply codes. to the Socket Congestion control appropriate for Interface mixed-loss environments (congestion, corruption, outage); SCPS-TP Selective negative acknowledgment; TCPTCP Robust header compression; “TCP TCP UDP OptionsOptions TCP UDP Partial Reliability service (BETS); Tranquility” Delimitation of record boundaries; options RFC 1323: Window scaling, time stamps, sequence number extension

Space-optimized Authentication: guarantee of the identity of a source; IPSec variant IPSec Access Control: prevention of unauthorized access; SCPS-SP IPSec Integrity: protection against modification; Common Network- Confidentiality: protection from disclosure. Layer Interface Provides both connectionless and managed- connection ; Space-optimized Supports precedence (priority) based handling; IP variant SCPS-NP IP Offer multiple routing options; Signals errors to the layer above; Supports packet lifetime control; Scalable - tailor capability to need, e.g., high communications efficiency in constrained bandwidth conditions. Space Link Subnet: CCSDS Data Link

The CCSDS protocol suite supports either “native” or “space enhanced” Internet services, at the discretion of the Project organization SCPS RI Distribution by Date 200 180 160 140 120 100 Copies 80 60 40 20 0 199719981999200020012002200320042005 Calendar Year

Joint NASA-DOD SCPS Project 1991-1999

SCPS RI Distribution, by Sector

Gov 18%

Industry Academia 68% 14% “Space Internet” CCSDS Protocol Scenario Constellation Free Flyer Orbiter

Ground Long-Haul Proximity Surface Operations Space Backbone Operations Operations CCSDS Packet

CCSDS Long-haul Link

CCSDS Space Link FTP+ Extension (SLE) Reliable File Transfer in disconnected, TCP, UDP + stressed, long-delay TCP , UDP environments ? IPSEC IPSec,CCSDS SP

IP IP, CCSDS NP

CCSDS Long-Haul Link and Coding Local Terrestrial Link CCSDS Link + CCSDS Proximity Link Physical Security and Coding

Local CCSDS UHF; CCSDS CCSDS Terrestrial local wired/ S, X, Ka Band UHF Wired wireless CCSDS File Delivery Protocol (CFDP)

Build 1 CFDP Build 2 CFDP

Currently in deployment (AlSat1, DI, JWST, MRO, etc) 1. point-to-point, 2. point-to-point, unacknowledged acknowledged 3. multi-hop, in series

X Rover CFDP Service Packet Service Frame Service X Orbiter

CFDP Service Packet Service Frame Service

X Lander Orbiter ice erv CFDP S e X rvic Packet Se ice Build 3 CFDP rv Frame Se CFDP Service Packet Service Frame Service

Ground Station

Frame/CLTUService X Network Control Center CFDP Service Packet Service Ground Station Frame/CLTUService 4. multi-hop, in parallel - without cross-links “CFDP-Era” (2005+) CCSDS Protocol Scenario Constellation Free Flyer Orbiter

Long-Haul Surface Ground Operations Space Backbone Proximity Operations Operations CCSDS File Delivery Protocol (CFDP) CCSDS File Delivery Protocol (CFDP) CCSDS Packet

CCSDS Long-haul Link CCSDS Space Link Extension (SLE) Is that all TCP, UDP TCP+, UDP there is? IPSEC IPSec,CCSDS SP

IP CCSDS NP IP, CCSDS NP

CCSDS Long-Haul Link and Coding Local Terrestrial Link CCSDS Link + CCSDS Proximity Link Physical Security and Coding

Local CCSDS UHF; CCSDS CCSDS Terrestrial local wired/ S, X, Ka Band UHF Wired wireless Do we expect 2010 – 2025 to be like this? Or like this? Will space operations of 2010 – 2025 look like this? Or like this? Do we have an underlying data communications architecture that can

scale u i.e., do we have an Interplanetary Network architecture that can scale to handle disruptive developments?

250000

200000 Internet Hosts (000s) 1989- 2001 150000

100000

50000 High Low 0 Jul-89 Jul-90 Jul-91 Jul-92 Jul-93 Jul-94 Jul-95 Jul-96 Jul-97 Jul-98 Jul-99 Jul-00 Jul-01 Interplanetary Region Internet: Region a “network of regional Region ” Region

Space Backbone Region Region

Region

log Dia End -to- End “The Internet” Region Region We need a general, standard way to communicate end-to-end through Region multiple regions in a disconnected, variable-delay environment The Internet: a Network of Connected Sub-Networks

App App

App App App App

Transport Transport TCP TCP Network Network Network Network IP IP IP IP

Link 1 Link 1 Link 2 Link 2 Link 3 Link 3

Phys 1 Phys 1 Phys 2 Phys 2 Phys 3 Phys 3

Subnet 1 Subnet 2 Subnet 3 Bundles: A Application Overlay The “Thin Waist” of the Interplanetary Internet

App App Possible disconnection App App App App

Internet a Internet b

Bundle New protocol development Bundle Bundle

Transport a Transport a Transport b Transport b

Network a Network a Network a Network b Network b

Link 1 Link 1 Link 2 Link 2 Link 3 Link 3

Phys 1 Phys 1 Phys 2 Phys 2 Phys 3 Phys 3

A “network of internets” spanning dissimilar environments 2007-2012 “Bundling-era” Protocol Scenario

Constellation

Orbiter Free Flyer Long-Haul Surface Ground Operations Space Backbone Proximity Operations Operations CCSDS Middleware and Space Applications Services (CFDP, ftp, Messaging, Streaming, etc.) CCSDS Disruption Tolerant Networking (“Bundling”) CCSDS Long-haul Link CCSDS Space Link Extension (SLE) TCP, UDP (TCP,TCP+, UDP)UDP

IPSEC IPSec,CCSDS SP

IP CCSDS NP IP, CCSDS NP

Long-haul CCSDS Long-Haul Link and Coding Local Link ARQ Terrestrial Link CCSDS Link + CCSDS Proximity Link Physical Security and Coding

Local CCSDS CCSDS local wired/ Terrestrial S, X, Ka Band; UHF wireless Wired Optical • “Non-chatty” Interplanetary Internet message-oriented communications • Store-and-forward Sensor between nodes • Routing algorithms Webs cognizant of scheduled connectivity • Use transport and network appropriate to the environment • Integral infrastructure protection

Disruption/Delay Tolerant Networking Remote outposts

Stressed tactical communications

Disruption Tolerant Networking: A new DARPA initiative

BAA04-13 Proposer Information Pamphlet (PIP)

for

Defense Advanced Research Projects Agency (DARPA) Advanced Technology Office (ATO)

Disruption Tolerant Networking (DTN)

Technical POC: Preston Marshall, DARPA/ATO

************************************************************* 2. OVERVIEW OF DISRUPTION TOLERANT NETWORKING 2.1. PROGRAM OVERVIEW Phase 1 (September The DTN program will develop and demonstrate technology that will provide network services when no end-to-end path exists through the network, and additional network 2004 - November 2005) behavior and functionality are required as DoD transitions from conventional networks to proposal selection more dynamic, self-forming, peer to peer architectures, such as Mobile Ad-Hoc Networks (MANETs). This program builds on protocol development and work performed by began by DARPA in late DTNRG program. The DTNRG program’s goal is to provide delay tolerance by July……. organizing information flow into bundles. These bundles are to be routed through an "intelligent" network that can manage the delivery of the bundles to the maximal extent permitted by the available topology. This method will allow messages to pass through the network with successive nodes (or regions) assuming delivery responsibilities. This ……. DTN is on its way. approach is in contrast to current layer 3 approaches which are based on an end-to-end model in which the sending and receiving nodes mutually assume all responsibility for delivery. In the DTN program, features appropriate to military application of the underlying delay tolerant mechanism will be researched. These technology needs are http://www.dtnrg.org further described in the research areas outlined in paragraph 2.1.1. DTN should be designed to be as Layer 3 Protocol independent as possible, and should address terrestrial, airborne and space environments.