Interplanetary Internet - Development

Development

Space communication technology has steadily evolved from expensive, one-of-a-kind point-to-point architectures, to the re-use of technology on successive missions, to the development of standard protocols agreed upon by space agencies of many countries. This last phase has gone on since 1982 through the efforts of the Consultative Committee for Space Data Systems (CCSDS), a body composed of the major space agencies of the world. It has 11 member agencies, 22 observer agencies, and over 100 industrial associates.

The evolution of space data system standards has gone on in parallel with the evolution of the Internet, with conceptual cross-pollination where fruitful, but largely as a separate evolution. Since the late 1990s, familiar Internet protocols and CCSDS space link protocols have integrated and converged in several ways, for example, the successful FTP file transfer to Earth-orbiting STRV-1b on January 2, 1996, which ran FTP over the CCSDS IPv4-like Space Communications Protocol Specifications (SCPS) protocols. Internet Protocol use without CCSDS has taken place on spacecraft, e.g., demonstrations on the UoSAT-12 satellite, and operationally on the Disaster Monitoring Constellation. Having reached the era where networking and IP on board spacecraft have been shown to be feasible and reliable, a forward-looking study of the bigger picture was the next phase.

The Interplanetary Internet study at NASA's Jet Propulsion Laboratory (JPL) was started by a team of scientists at JPL led by Vinton Cerf and Adrian Hooke. Cerf is one of the pioneers of the Internet on Earth, and currently holds the position of distinguished visiting scientist at JPL. Hooke is one of the directors of the CCSDS.

While IP-like SCPS protocols are feasible for short hops, such as ground station to orbiter, rover-to-lander, lander-to-orbiter, probe-to-flyby, and so on, delay-tolerant networking is needed to get information from one region of the solar system to another. It becomes apparent that the concept of a "region" is a natural architectural factoring of the InterPlanetary Internet.

A "region" is an area where the characteristics of communication are the same. Region characteristics include communications, security, the maintenance of resources, perhaps ownership, and other factors. The Interplanetary Internet is a "network of regional internets."

What is needed then, is a standard way to achieve end-to-end communication through multiple regions in a disconnected, variable-delay environment using a generalized suite of protocols. Examples of regions might include the terrestrial Internet as a region, a region on the surface of the moon or Mars, or a ground-to-orbit region.

The recognition of this requirement led to the concept of a "bundle" as a high-level way to address the generalized Store-and-Forward problem. Bundles are an area of new protocol development in the upper layers of the OSI model, above the Transport Layer with the goal of addressing the issue of bundling store-and-forward information so that it can reliably traverse radically dissimilar environments constituting a "network of regional internets."

Bundle Service Layering, implemented as the Bundling protocol suite for delay-tolerant networking, will provide general purpose delay-tolerant protocol services in support of a range of applications: custody transfer, segmentation and reassembly, end-to-end reliability, end-to-end security, and end-to-end routing among them. The Bundle Protocol was first tested in space on the UK-DMC satellite in 2008.

An example of one of these end-to-end applications flown on a space mission is CFDP, used on the comet mission, Deep Impact. CFDP is the CCSDS File Delivery Protocol an international standard for automatic, reliable file transfer in both directions. CFDP should not be confused with Coherent File Distribution Protocol, which unfortunately has the same acronym and is an IETF-documented experimental protocol for rapidly deploying files to multiple targets in a highly-networked environment.

In addition to reliably copying a file from one entity (such as a spacecraft or ground station) to another entity, the CCSDS CFDP has the capability to reliably transmit arbitrary small messages defined by the user, in the metadata accompanying the file, and to reliably transmit commands relating to file system management that are to be executed automatically on the remote end-point entity (such as a spacecraft) upon successful reception of a file.