OUTLINE OUTLINE • Where we’ve come from: CCSDS space links • Where we are now: – Delay Intolerant Networking (the IP suite) – The first Delay Tolerant Application (CFDP) • Where we are going: – Delay Tolerant Networking (Bundles) • MTO possibilities
1970 1980 1990 2000 NASA Telemetry Standardization “Packet” Spacecraft Telemetry and Telecommand 02 January, 1996 NASA/ESA Space Missions } STRV-1b Working Group IP address: Baselined by Space Basic Space/Ground 192.48.114.156 Station and Ground Network Communications Standards for Consultative Committee for Space Data Systems (CCSDS) CCSDS Recommendation for Advanced Orbiting Systems Extension of The Space Missions } File Transfer: FTAM Dark International Space Station Standards for Transport: TP4 Age More Complex Of Network: ISO 8473 GOSIP Extension of the Terrestrial Internet Evolution of space standards into Space NASA/DOD/CCSDS File Transfer: FTP Space Communications Transport: TCP Protocol Standards (CCSDS-SCPS) Project Network: IP 2002: InterPlaNetary 605 Internet (IPN) million users Evolution of the terrestrial Internet
InterPlaNetary Internet (IPN): a long term architecture for a connected Solar System http://www.dtnrg.org dtn-interest@mailman.dtnrg.org
The Internet is a connected, chatty ‘network of networks’ based on a wired backbone with negligible delay and errors (with untethered “edges” emerging) The InterPlaNetary Internet is a often disconnected, store-and forward ‘network of Internets’ based on a wireless backbone with huge delays and error prone links
Deep Space Backbone Region Terrestrial Region Mars Orbit Region Space missions are increasingly moving from point-to-point to networked Mars Region 2 architectures -- internal to each spacecraft -- on and around other planets Just like the terrestrial Internet, standardized space networking allows us to build low-cost, reusable infrastructure that can be shared by many diverse space missions Mars Region 1 Untethered, disconnected Extreme mass/power constraints Mobile, ad-hoc, self organizing
The Interplanetary Internet: An overlay network for interconnection of regional internets • A region is an area where the relevant characteristics of communication are homogeneous R E • Regions are defined based upon: R D – Communications capability – Quality of Service Peerings – Security (levels of trust) R C – Degree of resource management – Etc. R A • Traversal of two or more regions R B will affect the nature of communications
Interplanetary Region Internet: Region a “network of regional Region Region internets” Deep Space Region Backbone Region Region g o l a i D d n E - o t - d n E “The Internet” Region We need a general, standard way to Region communicate end-to-end through multiple regions in a disconnected, Region 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 2 Link 1 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 Store and Forward Application Overlay The “Thin Waist” of the Interplanetary Internet App App Possible disconnection App App App App Internet a Internet b Bundle Bundle Bundle New protocol development Transport b Transport a Transport b Transport a Network b Network a Network a Network b Network a Link 2 Link 1 Link 1 Link 2 Link 3 Link 3 Phys 1 Phys 1 Phys 2 Phys 3 Phys 2 Phys 3 A “network of internets” spanning dissimilar environments
Bundle Service Layering e2e Applications (e.g., Bundle FTP, CFDP, Bundle NTP) Bundle API Bundle Segmentation & Reassembly end-end Reliability Custody Transfer Authentication TBD Services Encryption Bundle Bundle Bundle Bundle Bundle “Bundling” Bundle Routing Convergence Layer (specific adapters that map Bundles to underlying transmission services) TCP UDP LTP IP CCSDS CCSDS Proximity Link SONET Ethernet Long-haul Link
“Interplanetary Networking ”: 2007+ Constellation Deep Space Backbone Earth Surface Orbiter Free Flyer CCSDS Space Applications Protocols (CFDP, Messaging, Streaming, etc.) CCSDS Bundling CCSDS Bundling � Developing the CCSDS Bundling protocol suite will provide general purpose delay tolerant protocol services in support of many diverse applications in highly networked configurations: – Custody transfer – Segmentation and reassembly – End-to-end reliability – End-to-end security – End-to-end routing – Long-haul link reliability • Bundling can replace most of DPM & SFO and will therefore allow CFDP to stabilize
IPN Bundle Transfer (Internet Draft 1) March 2003 DTN DTN IPN Bundle Protocol Architecture Architecture Architecture Specification, Draft1 (Internet Draft 3) (Internet Draft 2) (Internet Draft 1) September 2002 March 2003 August 2002 May 2001 Bundle Protocol Specification (Internet Draft 1) March 2003 Bundle Specification Bundle Specification Specifications Code base Bundle Prototyping Bundle Prototyping 1 st .Rough Code 4 th Proto.Code 5 th Proto. Code 2 nd .Proto.Code 3 rd .Proto.Code August 2000 Sept. 2002 Nov. 2002 May 2002 July 2002 Open Source Release1 Code March 2003 Code available at http://www.dtnrg.org
• “Non-chatty” Interplanetary Internet message-oriented communications • Store-and-forward Sensor Sensor between nodes • Routing algorithms Webs Webs cognizant of scheduled connectivity • Use transport and network technologies appropriate to the environment • Integral infrastructure protection Delay Tolerant Delay Tolerant Networking Networking Remote outposts Stressed tactical communications Stressed tactical communications IPN evolution: Broader applicability Nearer term utility Larger research community
Delay Tolerant Networking: a broad community effort Open Architecture Open Specifications Open Implementations Fielded DTN Deployments Other DTN communities Public IRTF DTN IPNSIG Research Group http://www.ipnsig.org http://www.dtnrg.org http://www.ccsds.org Interplanetary Internet
Purpose, goals and research issues . The purpose of the project is to contribute to the design and implementation of the general Delay Tolerant Network (DTN) architecture, with special focus on wireless sensor and sensor/actuator networks (SN). The aim of the general DTN architecture is to achieve interoperability between and among challenged networks. Of particular interest for this research proposal is using DTN to achieve interoperability between wireless SNs and the Internet. In practical terms, this means being able to access, operate and control wireless sensor networks through the Internet.
DARPA Advanced Technology Office Fielded deployments of DTN technology 2003 2005 2002 2004 DTN Research Group: Focal point for DTN • DTN Architecture DTN Core Engineering • DTN Design Documents Delay Tolerant Delay Tolerant • Reference Software DTN Open Source Networking Networking • Configuration Control DTN Standardization • International Standards ajh16 04 June, 2003
Internet DTN TEST AND DEMONSTRATION NSF Future DTN regions Antarctic INCUBATOR region CONCEPT DTN Satellite EarthSat Sea World Satellite terminal G/W region Earth JPL Arroyo: Orbit North Mars analog Relay Dryden Sensor region DC8 region Field Sensor Field Rover JPL Mesa: Deep Space Rover Sensor Backbone Mars Orbit Field Analog region region DSN Terminal MarSat Rover Lander CCSDS (DTF-21) Long-haul Arctic Rover Sensor Mars analog region Field Rover JPL Control Center JPL Mars (AMMOS/SMOCC) Sensor JPL Core System Field Yard: South Mars analog region
CFDP Bundling and • Store and forward mode • Store and forward mode • Transfers files • Transfers all forms of data • Currently point-point: • Inherently networked: – Static Routing – Dynamic Routing – Implicit notion of Custody – Full DTN Custody protocol • Monolithic • Will be internally layered • Fairly complex; adding • Quite complex, but routing + custody transfer layering will make will make it more so complexity manageable • Only of current interest to • Of wide potential interest the ‘space’ community to other communities Proposed Strategy • Get CFDP into widespread use as a waypoint to Bundling • Avoid increasing the complexity of the protocol beyond Core+Extended • Mobilize other DTN users to develop Bundling as a community effort • Broader base of users and applications = faster development and more robustness • Infuse Bundling to handle needed complexity and simply move a stable CFDP to become an application running over Bundling
e2e Applications APPLICATIONS APPLICATIONS (e.g., Bundle FTP, CFDP, Bundle NTP) CFDP File operations Bundle API [CFDP point-to-point reliability] Bundle Segmentation & Reassembly end-end Reliability Custody Transfer Authentication TBD Services Encryption Bundle Bundle Bundle Bundle Bundle BUNDLE Custody transfer; e2e security, reliability, routing Bundle Routing Convergence Layer (specific adapters that map Bundles to underlying transmission services) TCP UDP LTP IP CCSDS CCSDS CCSDS Reliable Space Link Proximity Link SONET Ethernet Long-haul Link
Recommend
More recommend
