Search NASA⌕ Search

SEARCH · Search NASA

Results for “end-to-end reliability”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

Kepler Mission: A Search for Terrestrial Planets

The Kepler Mission is a search for terrestrial planets by monitoring a large ensemble of stars for the periodic transits of planets. The mission consists of a 95-cm aperture photometer with 105 square deg field of view that monitors 100,000 dwarf stars for four years. The mission is unique in its ability to detect Earth-size planets in the habitable zone of other stars in the extended solar neighborhood. An Earth-size transit of a solar-like star causes a change in brightness of about 100 ppm. Laboratory testing has demonstrated that a total system noise level of 20 ppm is readily achievable on the timescale of transits. Earth-like transits have been created and reliably measured in an end-to-end system test that has all known sources of noise including, spacecraft jitter. To detect Earth-size planets, the photometer must be spaceborne; this also eliminates the day-night and seasonal cycle interruptions of ground-based observing. The photometer will stare at a single field of stars for four years, with an option to continue for two more years. This allows for detection of four transits of planets in Mars-like orbits and detection of planets even smaller than Earth especially for short period orbits, since the signal to noise improves as the square root of the number of transits observed. In addition to detection of planets, Kepler data are also useful for understanding the activity cycles and rotation rates of the stars observed. For the 3,000 stars brighter than mv= 11.4 p-mode oscillations are measured. The mission has been selected as one of three candidates for NASA's next Discovery mission.

Koch, D.↗
NASA NTRS2002

MDP: Reliable File Transfer for Space Missions

This paper presents work being done at NASA/GSFC by the Operating Missions as Nodes on the Internet (OMNI) project to demonstrate the application of the Multicast Dissemination Protocol (MDP) to space missions to reliably transfer files. This work builds on previous work by the OMNI project to apply Internet communication technologies to space communication. The goal of this effort is to provide an inexpensive, reliable, standard, and interoperable mechanism for transferring files in the space communication environment. Limited bandwidth, noise, delay, intermittent connectivity, link asymmetry, and one-way links are all possible issues for space missions. Although these are link-layer issues, they can have a profound effect on the performance of transport and application level protocols. MDP, a UDP-based reliable file transfer protocol, was designed for multicast environments which have to address these same issues, and it has done so successfully. Developed by the Naval Research Lab in the mid 1990's, MDP is now in daily use by both the US Post Office and the DoD. This paper describes the use of MDP to provide automated end-to-end data flow for space missions. It examines the results of a parametric study of MDP in a simulated space link environment and discusses the results in terms of their implications for space missions. Lessons learned are addressed, which suggest minor enhancements to the MDP user interface to add specific features for space mission requirements, such as dynamic control of data rate, and a checkpoint/resume capability. These are features that are provided for in the protocol, but are not implemented in the sample MDP application that was provided. A brief look is also taken at the status of standardization. A version of MDP known as NORM (Neck Oriented Reliable Multicast) is in the process of becoming an IETF standard.

Rash, James↗
NASA NTRS2003

Reliable Transport over SpaceWire for James Webb Space Telescope (JWST) Focal Plane Electronics (FPE) Network

NASA's James Webb Space Telescope (JWST) faces difficult technical and budgetary challenges to overcome before it is scheduled launch in 2010. The Integrated Science Instrument Module (ISIM), shares these challenges. The major challenge addressed in this paper is the data network used to collect, process, compresses and store Infrared data. A total of 114 Mbps of raw information must be collected from 19 sources and delivered to the two redundant data processing units across a twenty meter deployed thermally restricted interface. Further data must be transferred to the solid-state recorder and the spacecraft. The JWST detectors are kept at cryogenic temperatures to obtain the sensitivity necessary to measure faint energy sources. The Focal Plane Electronics (FPE) that sample the detector, generate packets from the samples, and transmit these packets to the processing electronics must dissipate little power in order to help keep the detectors at these cold temperatures. Separating the low powered front-end electronics from the higher-powered processing electronics, and using a simple high-speed protocol to transmit the detector data minimize the power dissipation near the detectors. Low Voltage Differential Signaling (LVDS) drivers were considered an obvious choice for physical layer because of their high speed and low power. The mechanical restriction on the number cables across the thermal interface force the Image packets to be concentrated upon two high-speed links. These links connect the many image packet sources, Focal Plane Electronics (FPE), located near the cryogenic detectors to the processing electronics on the spacecraft structure. From 12 to 10,000 seconds of raw data are processed to make up an image, various algorithms integrate the pixel data Loss of commands to configure the detectors as well as the loss of science data itself may cause inefficiency in the use of the telescope that are unacceptable given the high cost of the observatory. This combination of requirements necessitates a redundant, fault tolerant, high- speed, low mass, low power network with a low Bit error Rate(1E-9- 1E-12). The ISIM systems team performed many studies of the various network architectures that meeting these requirements. The architecture selected uses the Spacewire protocol, with the addition of a new transport and network layer added to implement end-to-end reliable transport. The network and reliable transport mechanism must be implemented in hardware because of the high average information rate and the restriction on the ability of the detectors to buffer data due to power and size restrictions. This network and transport mechanism was designed to be compatible with existing Spacewire links and routers so that existing equipment and designs may be leveraged upon. The transport layer specification is being coordinated with European Space Agency (ESA), Spacewire Working Group and the Consultative Committee for Space Data System (CCSDS) PlK Standard Onboard Interface (SOIF) panel, with the intent of developing a standard for reliable transport for Spacewire. Changes to the protocol presented are likely since negotiations are ongoing with these groups. A block of RTL VHDL that implements a multi-port Spacewire router with an external user interface will be developed and integrated with an existing Spacewire Link design. The external user interface will be the local interface that sources and sinks packets onto and off of the network (Figure 3). The external user interface implements the network and transport layer and handles acknowledgements and re-tries of packets for reliable transport over the network. Because the design is written in RTL, it may be ported to any technology but will initially be targeted to the new Actel Accelerator series (AX) part. Each link will run at 160 Mbps and the power will be about 0.165 Watt per link worst case in the Actel AX.

Rakow, Glenn↗
NASA NTRS2003

Demonstrating a Realistic IP Mission Prototype

Flight software and hardware and realistic space communications environments were elements of recent demonstrations of the Internet Protocol (IP) mission concept in the lab. The Operating Missions as Nodes on the Internet (OMNI) Project and the Flight Software Branch at NASA/GSFC collaborated to build the prototype of a representative space mission that employed unmodified off-the-shelf Internet protocols and technologies for end-to-end communications between the spacecraft/instruments and the ground system/users. The realistic elements used in the prototype included an RF communications link simulator and components of the TRIANA mission flight software and ground support system. A web-enabled camera connected to the spacecraft computer via an Ethernet LAN represented an on-board instrument creating image data. In addition to the protocols at the link layer (HDLC), transport layer (UDP, TCP), and network (IP) layer, a reliable file delivery protocol (MDP) at the application layer enabled reliable data delivery both to and from the spacecraft. The standard Network Time Protocol (NTP) performed on-board clock synchronization with a ground time standard. The demonstrations of the prototype mission illustrated some of the advantages of using Internet standards and technologies for space missions, but also helped identify issues that must be addressed. These issues include applicability to embedded real-time systems on flight-qualified hardware, range of applicability of TCP, and liability for and maintenance of commercial off-the-shelf (COTS) products. The NASA Earth Science Technology Office (ESTO) funded the collaboration to build and demonstrate the prototype IP mission.

Rash, James↗
NASA NTRS2003

NASA/BAE SYSTEMS SpaceWire Effort

This paper discusses the state of the NASA and BAE SYSTEMS developments of SpaceWire. NASA has developed intellectual property that implements SpaceWire in Register Transfer Level (RTL) VHDL for a SpaceWire link and router. This design has been extensively verified using directed tests from the SpaceWire Standard and design specification, as well as being randomly tested to flush out hard to find bugs in the code. The high level features of the design will be discussed, including the support for multiple time code masters, which will be useful for the James Webb Space Telescope electrical architecture. This design is now ready to be targeted to FPGA's and ASICs. Target utilization and performance information will be presented for Spaceflight worthy FPGA's and a discussion of the ASIC implementations will be addressed. In particular, the BAE SYSTEMS ASIC will be highlighted which will be implemented on their .25micron rad-hard line. The chip will implement a 4-port router with the ability to tie chips together to make larger routers without external glue logic. This part will have integrated LVDS drivers/receivers, include a PLL and include skew control logic. It will be targeted to run at greater than 300 MHz and include the implementation for the proposed SpaceWire transport layer. The need to provide a reliable transport mechanism for SpaceWire has been identified by both NASA And ESA, who are attempting to define a transport layer standard that utilizes a low overhead, low latency connection oriented approach that works end-to-end. This layer needs to be implemented in hardware to prevent bottlenecks.

Rakow, Glenn Parker↗
NASA NTRS2004

Toward Synthesis, Analysis, and Certification of Security Protocols

Implemented security protocols are basically pieces of software which are used to (a) authenticate the other communication partners, (b) establish a secure communication channel between them (using insecure communication media), and (c) transfer data between the communication partners in such a way that these data only available to the desired receiver, but not to anyone else. Such an implementation usually consists of the following components: the protocol-engine, which controls in which sequence the messages of the protocol are sent over the network, and which controls the assembly/disassembly and processing (e.g., decryption) of the data. the cryptographic routines to actually encrypt or decrypt the data (using given keys), and t,he interface to the operating system and to the application. For a correct working of such a security protocol, all of these components must work flawlessly. Many formal-methods based techniques for the analysis of a security protocols have been developed. They range from using specific logics (e.g.: BAN-logic [4], or higher order logics [12] to model checking [2] approaches. In each approach, the analysis tries to prove that no (or at least not a modeled intruder) can get access to secret data. Otherwise, a scenario illustrating the &tack may be produced. Despite the seeming simplicity of security protocols ("only" a few messages are sent between the protocol partners in order to ensure a secure communication), many flaws have been detected. Unfortunately, even a perfect protocol engine does not guarantee flawless working of a security protocol, as incidents show. Many break-ins and security vulnerabilities are caused by exploiting errors in the implementation of the protocol engine or the underlying operating system. Attacks using buffer-overflows are a very common class of such attacks. Errors in the implementation of exception or error handling can open up additional vulnerabilities. For example, on a website with a log-in screen: multiple tries with invalid passwords caused the expected error message (too many retries). but let the user nevertheless pass. Finally, security can be compromised by silly implementation bugs or design decisions. In a commercial VPN software, all calls to the encryption routines were incidentally replaced by stubs, probably during factory testing. The product worked nicely. and the error (an open VPN) would have gone undetected, if a team member had not inspected the low-level traffic out of curiosity. Also, the use secret proprietary encryption routines can backfire, because such algorithms often exhibit weaknesses which can be exploited easily (see e.g., DVD encoding). Summarizing, there is large number of possibilities to make errors which can compromise the security of a protocol. In today s world with short time-to-market and the use of security protocols in open and hostile networks for safety-critical applications (e.g., power or air-traffic control), such slips could lead to catastrophic situations. Thus, formal methods and automatic reasoning techniques should not be used just for the formal proof of absence of an attack, but they ought to be used to provide an end-to-end tool-supported framework for security software. With such an approach all required artifacts (code, documentation, test cases) , formal analyses, and reliable certification will be generated automatically, given a single, high level specification. By a combination of program synthesis, formal protocol analysis, certification; and proof-carrying code, this goal is within practical reach, since all the important technologies for such an approach actually exist and only need to be assembled in the right way.

Schumann, Johann↗
NASA NTRS2005

Business Intelligence Modeling in Launch Operations

This technology project is to advance an integrated Planning and Management Simulation Model for evaluation of risks, costs, and reliability of launch systems from Earth to Orbit for Space Exploration. The approach builds on research done in the NASA ARC/KSC developed Virtual Test Bed (VTB) to integrate architectural, operations process, and mission simulations for the purpose of evaluating enterprise level strategies to reduce cost, improve systems operability, and reduce mission risks. The objectives are to understand the interdependency of architecture and process on recurring launch cost of operations, provide management a tool for assessing systems safety and dependability versus cost, and leverage lessons learned and empirical models from Shuttle and International Space Station to validate models applied to Exploration. The systems-of-systems concept is built to balance the conflicting objectives of safety, reliability, and process strategy in order to achieve long term sustainability. A planning and analysis test bed is needed for evaluation of enterprise level options and strategies for transit and launch systems as well as surface and orbital systems. This environment can also support agency simulation .based acquisition process objectives. The technology development approach is based on the collaborative effort set forth in the VTB's integrating operations. process models, systems and environment models, and cost models as a comprehensive disciplined enterprise analysis environment. Significant emphasis is being placed on adapting root cause from existing Shuttle operations to exploration. Technical challenges include cost model validation, integration of parametric models with discrete event process and systems simulations. and large-scale simulation integration. The enterprise architecture is required for coherent integration of systems models. It will also require a plan for evolution over the life of the program. The proposed technology will produce long-term benefits in support of the NASA objectives for simulation based acquisition, will improve the ability to assess architectural options verses safety/risk for future exploration systems, and will facilitate incorporation of operability as a systems design consideration, reducing overall life cycle cost for future systems. The future of business intelligence of space exploration will focus on the intelligent system-of-systems real-time enterprise. In present business intelligence, a number of technologies that are most relevant to space exploration are experiencing the greatest change. Emerging patterns of set of processes rather than organizational units leading to end-to-end automation is becoming a major objective of enterprise information technology. The cost element is a leading factor of future exploration systems.

Bardina, Jorge E.↗
NASA NTRS2007

Development of a Test Facility for Air Revitalization Technology Evaluation

Development of new air revitalization system (ARS) technology can initially be performed in a subscale laboratory environment, but in order to advance the maturity level, the technology must be tested in an end-to-end integrated environment. The Air Revitalization Technology Evaluation Facility (ARTEF) at the NASA Johnson Space Center serves as a ground test bed for evaluating emerging ARS technologies in an environment representative of spacecraft atmospheres. At the center of the ARTEF is a hypobaric chamber which serves as a sealed atmospheric chamber for closed loop testing. A Human Metabolic Simulator (HMS) was custom-built to simulate the consumption of oxygen, and production of carbon dioxide, moisture and heat of up to eight persons. A multitude of gas analyzers and dew point sensors are used to monitor the chamber atmosphere upstream and downstream of a test article. A robust vacuum system is needed to simulate the vacuum of space. A reliable data acquisition and control system is required to connect all the subsystems together. This paper presents the capabilities of the integrated test facility and some of the issues encountered during the integration.

Lu, Sao-Dung↗
NASA NTRS2007

Final Results for the GRC Supporting Technology Development Project for the 110-Watt Stirling Radioisotope Generator (SRG110)

From 1999-2006, the NASA Glenn Research Center (GRC) supported the development of a high-efficiency, nominal 110-We Stirling Radioisotope Generator (SRG110) for potential use on NASA missions, including deep space missions, Mars rovers, and lunar applications. Lockheed Martin (LM) was the system integrator for the SRG110, under contract to the Department of Energy (DOE). Infinia Corporation (formerly Stirling Technology Company) developed the Stirling convertor, first as a contractor to DOE and then under subcontract to LM. The SRG110 development has been redirected, and recent program changes have been made to significantly increase the specific power of the generator. System development of an Advanced Stirling Radioisotope Generator (ASRG) has now begun, using a lightweight, advanced convertor from Sunpower, Inc. This paper summarizes the results of the supporting technology effort that GRC completed for the SRG110. GRC tasks included convertor extended-duration testing in air and thermal vacuum environments, heater head life assessment, materials studies, permanent magnet aging characterization, linear alternator evaluations, structural dynamics testing, electromagnetic interference (EMI) and electromagnetic compatibility (EMC) characterization, organic materials evaluations, reliability studies, and development of an end-to-end system dynamic model. Related efforts are now continuing in many of these areas to support ASRG development.

Schreiber, Jeffrey G.↗
NASA NTRS2007

Final Results for the GRC Supporting Technology Development Project for the 110-Watt Stirling Radioisotope Generator (SRG110)

From 1999 to 2006, the NASA Glenn Research Center (GRC) supported the development of a high-efficiency, nominal 110-We Stirling Radioisotope Generator (SRG110) for potential use on NASA missions, including deep space missions, Mars rovers, and lunar applications. Lockheed Martin (LM) was the system integrator for the SRG110, under contract to the Department of Energy (DOE). Infinia Corporation (formerly Stirling Technology Company) developed the Stirling convertor, first as a contractor to DOE and then under subcontract to LM. The SRG110 development has been redirected, and recent program changes have been made to significantly increase the specific power of the generator. System development of an Advanced Stirling Radioisotope Generator (ASRG) has now begun, using a lightweight, advanced convertor from Sunpower, Inc. This paper summarizes the results of the supporting technology effort that GRC completed for the SRG110. GRC tasks included convertor extended-duration testing in air and thermal vacuum environments, heater head life assessment, materials studies, permanent magnet aging characterization, linear alternator evaluations, structural dynamics testing, electromagnetic interference (EMI) and electromagnetic compatibility (EMC) characterization, organic materials evaluations, reliability studies, and development of an end-to-end system dynamic model. Related efforts are now continuing in many of these areas to support ASRG development.

Schreiber, Jeffrey G.↗
NASA NTRS2007

"Fly-by-Wireless" : A Revolution in Aerospace Architectures for Instrumentation and Control

The conference presentation provides background information on Fly-by-Wireless technologies as well as reasons for implementation, CANEUS project goals, cost of change for instrumentation, reliability, focus areas, conceptual Hybrid SHMS architecture for future space habitats, real world problems that the technology can solve, evolution of Micro-WIS systems, and a WLEIDS system overview and end-to-end system design.

Studor, George F.↗
NASA NTRS2006

Simulation Modeling and Performance Evaluation of Space Networks

In space exploration missions, the coordinated use of spacecraft as communication relays increases the efficiency of the endeavors. To conduct trade-off studies of the performance and resource usage of different communication protocols and network designs, JPL designed a comprehensive extendable tool, the Multi-mission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE). The design and development of MACHETE began in 2000 and is constantly evolving. Currently, MACHETE contains Consultative Committee for Space Data Systems (CCSDS) protocol standards such as Proximity-1, Advanced Orbiting Systems (AOS), Packet Telemetry/Telecommand, Space Communications Protocol Specification (SCPS), and the CCSDS File Delivery Protocol (CFDP). MACHETE uses the Aerospace Corporation s Satellite Orbital Analysis Program (SOAP) to generate the orbital geometry information and contact opportunities. Matlab scripts provide the link characteristics. At the core of MACHETE is a discrete event simulator, QualNet. Delay Tolerant Networking (DTN) is an end-to-end architecture providing communication in and/or through highly stressed networking environments. Stressed networking environments include those with intermittent connectivity, large and/or variable delays, and high bit error rates. To provide its services, the DTN protocols reside at the application layer of the constituent internets, forming a store-and-forward overlay network. The key capabilities of the bundling protocols include custody-based reliability, ability to cope with intermittent connectivity, ability to take advantage of scheduled and opportunistic connectivity, and late binding of names to addresses. In this presentation, we report on the addition of MACHETE models needed to support DTN, namely: the Bundle Protocol (BP) model. To illustrate the use of MACHETE with the additional DTN model, we provide an example simulation to benchmark its performance. We demonstrate the use of the DTN protocol and discuss statistics gathered concerning the total time needed to simulate numerous bundle transmissions

network protocols↗
NASA NTRS2006

Implementation of a Coded Modulation for Deep Space Optical Communications

We present an efficient implementation of a coded modulation for the deep space optical channel. NASA designed this so called serially concatenated pulse position modulation (SCPPM) code to provide an optical link that can operate within one dB signal energy of the Shannon capacity during a nominal mission condition from Mars. Here, we describe some of the challenges in realizing the SCPPM decoder on a field-programmable gate array (FPGA). Through various architectural optimizations, we achieve a 6 Mbps decoder on a single FPGA. Moreover, we demonstrate that it is possible to communicate reliably on an efficient bits-per-photon count in an end-to-end SCPPM coded system.

turbo codes↗
NASA NTRS2008

Designing the Ares I Crew Launch Vehicle Upper Stage Element and Integrating the Stack at NASA's Marshall Space Flight Center

Fielding an integrated launch vehicle system entails many challenges, not the least of which is the fact that it has been over 30 years since the United States has developed a human-rated vehicle - the venerable Space Shuttle. Over time, whole generations of rocket scientists have passed through the aerospace community without the opportunity to perform such exacting, demanding, and rewarding work. However, with almost 50 years of experience leading the design, development, and end-to-end systems engineering and integration of complex launch vehicles, NASA's Marshall Space Flight Center offers the in-house talent - both junior- and senior-level personnel - to shape a new national asset to meet the requirements for safe, reliable, and affordable space exploration solutions.' These personnel are housed primarily in Marshall's Engineering Directorate and are matrixed into the programs and projects that reside at the rocket center. Fortunately, many Apollo era and Shuttle engineers, as well as those who gained valuable hands-on experience in the 1990s by conducting technology demonstrator projects such as the Delta-Clipper Experimental Advanced, X-33, X-34, and X-37, as well as the short-lived Orbital Space Plane, work closely with industry partners to advance the nation's strategic capability for human access to space. Currently, only three spacefaring nations have this distinction, including the United States, Russia, and, more recently, China. The U.S. National Space Policy of2006 directs that NASA provide the means to travel to space, and the NASA Appropriations Act of2005 provided the initial funding to begin in earnest to replace the Shuttle after the International Space Station construction is complete in 20 IO? These and other strategic goals and objectives are documented in NASA's 2006 Strategic Plan.3 In 2005, a team of NASA aerospace experts conducted the Exploration Systems Architecture Study, which recommended a two-vehicle approach to America's next space transportation system for missions to the International Space Station in the next decade and to explore the Moon and establish an outpost around the 2020 timeframe.4 Based on this extensive study, NASA selected the Ares I crew launch vehicle configuration and the heavy-lift Ares V cargo launch vehicle (fig 1). This paper will give an overview of NASA's approach to integrating the Ares I vehicle stack using capabilities and assets that are resident in Marshall's Engineering Directorate, working in partnership with other NASA Centers and the U.S. aerospace industry. It also will provide top-level details on the progress of the in-house design of the Ares I vehicle's upper stage element.

Lyles, Garry↗
NASA NTRS2006

A Holistic Approach for Risk Management During Design

In this paper, an approach for the identification, assessment, mitigation and continuous management of risks during the process of designing a space mission is presented. This approach has been developed by observing the risk patterns that occur at the Project Design Center of the Jet Propulsion Laboratory (TeamX) which develops conceptual, concurrent design of Space Missions. TeamX develops an end-to-end conceptual design of a Space Mission in a matter of one or two weeks. As the risk chair in TeamX, the author has had the opportunity to observe the risk patterns that occur during design over the course of many design sessions. This paper introduces an abstraction and generalization of those patterns. Risk is defined as anything that can go wrong, along with its approximate likelihood and consequence. The indicators, and causes, and effects of these risks are cross cutting across the multiple levels of people and processes involved in the design, and the actual design product itself.

reliability analysis↗
NASA NTRS2010

Total Water Content Measurements with an Isokinetic Sampling Probe

The NASA Glenn Research Center has developed a Total Water Content (TWC) Isokinetic Sampling Probe. Since it is not sensitive to cloud water particle phase nor size, it is particularly attractive to support super-cooled large droplet and high ice water content aircraft icing studies. The instrument is comprised of the Sampling Probe, Sample Flow Control, and Water Vapor Measurement subsystems. Analysis and testing have been conducted on the subsystems to ensure their proper function and accuracy. End-to-end bench testing has also been conducted to ensure the reliability of the entire instrument system. A Stokes Number based collection efficiency correction was developed to correct for probe thickness effects. The authors further discuss the need to ensure that no condensation occurs within the instrument plumbing. Instrument measurements compared to facility calibrations from testing in the NASA Glenn Icing Research Tunnel are presented and discussed. There appears to be liquid water content and droplet size effects in the differences between the two measurement techniques.

Reehorst, Andrew L.↗
NASA NTRS2011

Space Flight Middleware: Remote AMS over DTN for Delay-Tolerant Messaging

This paper describes a technique for implementing scalable, reliable, multi-source multipoint data distribution in space flight communications -- Delay-Tolerant Reliable Multicast (DTRM) -- that is fully supported by the "Remote AMS" (RAMS) protocol of the Asynchronous Message Service (AMS) proposed for standardization within the Consultative Committee for Space Data Systems (CCSDS). The DTRM architecture enables applications to easily "publish" messages that will be reliably and efficiently delivered to an arbitrary number of "subscribing" applications residing anywhere in the space network, whether in the same subnet or in a subnet on a remote planet or vehicle separated by many light minutes of interplanetary space. The architecture comprises multiple levels of protocol, each included for a specific purpose and allocated specific responsibilities: "application AMS" traffic performs end-system data introduction and delivery subject to access control; underlying "remote AMS" directs this application traffic to populations of recipients at remote locations in a multicast distribution tree, enabling the architecture to scale up to large networks; further underlying Delay-Tolerant Networking (DTN) Bundle Protocol (BP) advances RAMS protocol data units through the distribution tree using delay-tolerant storeand- forward methods; and further underlying reliable "convergence-layer" protocols ensure successful data transfer over each segment of the end-to-end route. The result is scalable, reliable, delay-tolerant multi-source multicast that is largely self-configuring.

Disruption Tolerant Networking (DTN)↗