Search NASA⌕ Search

SEARCH · Search NASA

Results for “Concept of Operations”

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 577 records · Page 32

Engineering and simulation of life sciences Spacelab experiments

The third in a series of Spacelab Mission Development tests was conducted at the Johnson (correction of Johnston) Space Center as a part of the development of Life Sciences experiments for the Space Shuttle era. The latest test was a joint effort of the Ames Research and Johnson Space Centers and utilized animals and men for study. The basic objective of this test was to evaluate the operational concepts planned for the Space Shuttle life science payloads program. A three-man crew (Mission Specialist and two Payload Specialists) conducted 26 experiments and 12 operational tests, which were selected for this 7-day mission simulation. The crew lived on board a simulated Orbiter/Spacelab mockup 24 hr a day. The Orbiter section contained the mid deck crew quarters area, complete with sleeping, galley and waste management provisions. The Spacelab was identical in geometry to the European Space Agency Spacelab design, complete with removable rack sections and stowage provisions. Communications between the crewmen and support personnel were configured and controlled as currently planned for operational shuttle flights. For this test a Science Operations Remote Center was manned at the Ames Research Center and was managed by simulated Mission Control and Payload Operation Control Centers at the Johnson Space Center. This paper presents the test objectives, description of the facilities and test program, and the results of this test.

Biological Sciences/instrumentation/methods↗

Trajectory-Based Takeoff Time Predictions Applied to Tactical Departure Scheduling: Concept Description, System Design, and Initial Observations

Current aircraft departure release times are based on manual estimates of aircraft takeoff times. Uncertainty in takeoff time estimates may result in missed opportunities to merge into constrained en route streams and lead to lost throughput. However, technology exists to improve takeoff time estimates by using the aircraft surface trajectory predictions that enable air traffic control tower (ATCT) decision support tools. NASA s Precision Departure Release Capability (PDRC) is designed to use automated surface trajectory-based takeoff time estimates to improve en route tactical departure scheduling. This is accomplished by integrating an ATCT decision support tool with an en route tactical departure scheduling decision support tool. The PDRC concept and prototype software have been developed, and an initial test was completed at air traffic control facilities in Dallas/Fort Worth. This paper describes the PDRC operational concept, system design, and initial observations.

Engelland, Shawn A.↗

Safety Case for Small Uncrewed Aircraft Systems (sUAS) Beyond Visual Line of Sight (BVLOS) Operations at NASA Langley Research Center

This Technical Memorandum (TM) is written to provide for dissemination of the methods and safety considerations for operations of small Uncrewed Aerial Systems (sUAS) Beyond Visual Line-of-Sight (BVLOS)at NASA Langley Research Center. It includes the Safety Case used to acquire a BVLOS Certificate of Authorization (COA) from the FAA and is being published to enable others to benefit from this work. The intended operations, subject to approval from the Federal Aviation Administration (FAA) and the National Aeronautics and Space Administration (NASA), will include a combination of Within Visual Line of Sight (WVLOS) and Beyond Visual Line of Sight (BVLOS) flights, comprising of at most five sUAS operating concurrently, with no more than three operating BVLOS. Flights will occur in a subset of the Langley Air Force Base (LAFB) Class D airspace (KLFI) at a maximum altitude of 400 ft AGL. Most operations within this subset will take place in the City Environment Range Testing for Autonomous Integrated Navigation (CERTAIN) Range. The CERTAIN Range includes airspace inside the borders of NASA Langley Research Center (LaRC). Additional airspace over the northern section of CERTAIN will be requested as part of the Certificate of Authorization (COA). NASA LaRC BVLOS operations on the CERTAIN Range can be broken down into five critical components needed to meet the 14 CFR § 91.113 see and avoid requirement: 1) procedural deconfliction with LAFB for UAS operations at or below 400 ft and manned aircraft at or above 900’ AGL; 2) ground equipment for detection of intruder aircraft and to support communications between crewmembers ; 3) sUAS vehicles with advanced onboard automation capable of autonomously maintaining safe separation; 4) BVLOS standardized operating procedures (SOPs); 5) and personnel to execute the flight operations in accordance with the SOPs and respond to airborne contingencies. The introduction of new ground equipment includes the use of the Remote Operations for Autonomous Missions (ROAM) UAS Operations Center, development and use of an Integrated Airspace Display (IAD), use of the L-STAR and GA-9120 radars, and the incorporation of standardized Vertiports. The ROAM Operations Center will be the central point for all BVLOS sUAS operations. All command and control (C2), voice communications and airspace awareness displays will reside inside ROAM. The IAD will provide raw data from ADS-B, FLARM, radar tracks and telemetered GPS vehicle positions for interpretation by an Airspace Monitor. The radars will search the class D airspace around the CERTAIN Range and serve as a backup to procedural deconfliction procedures coordinated with LAFB. In the event of a procedural deconfliction breakdown, radar detections of non-participating aircraft will be available so that the 91.113 see and avoid requirement can still be safely met. Finally, the incorporation of Vertiports will have video and network connectivity that enables large numbers of sUAS launches and recoveries from a single location. This is a continuation of the remote command and control of unpiloted aircraft component focused on evaluating unpiloted aircraft flight crew roles and responsibilities, control interfaces and the associated data links needed to operate a fleet of aircraft within a UAM Ecosystem. This work supports the development of future aviation operational concepts based on an Urban Air Mobility Maturity Level (UML) 4 environment (Patterson, 2020). It is assumed that future airspace will include hundreds of simultaneous aircraft operations within the airspace, therefore scalable operations are essential for enabling this future airspace to become a reality. Follow on work includes envisioned flights that expand operations beyond the CERTAIN range and lead to an effective Maritime Surveillance capability.

Matthew W Coldsnow↗

National Campaign Partner Demonstration Team Annual Review April 2023

- NASA developed the Advanced Air Mobility Project (AAM) and the National Campaign (NC) series to identify and address challenges ahead for advanced air mobility concepts. - NC seeks to challenge industry as follows; - Execute progressively more difficult ecosystem-wide system-level safety and integration scenarios - Demonstrate practical and scalable system concepts - Build a knowledge base for development of requirements and standards - There are currently three focus areas within the NASA AAM NC Portfolio - Vehicle Development and Operations: test and inform capabilities that are critical enablers for AAM such as electric aircraft propulsion and increasing levels of automation - Airspace Design and Operations: develop and validate an operational concept to integrate and manage AAM traffic safely and efficiently - Community Integration: understand and address critical barriers to community integration, such as public acceptance (noise, security, privacy, etc.), supporting infrastructure, and local regulation

Eric N Becker↗

Space station Simulation Computer System (SCS) study for NASA/MSFC. Volume 1: Overview and summary

NASA's Space Station Freedom Program (SSFP) planning efforts have identified a need for a payload training simulator system to serve as both a training facility and as a demonstrator to validate operational concepts. The envisioned Marshall Space Flight Center (MSFC) Payload Training Complex (PTC) required to meet this need will train the space station payload scientists, station scientists, and ground controllers to operate the wide variety of experiments that will be onboard the Space Station Freedom. The Simulation Computer System (SCS) is the computer hardware, software, and workstations that will support the Payload Training Complex at MSFC. The purpose of this SCS study is to investigate issues related to the SCS, alternative requirements, simulator approaches, and state-of-the-art technologies to develop candidate concepts and designs. This study was performed August 1988 to October 1989. Thus, the results are based on the SSFP August 1989 baseline, i.e., pre-Langley configuration/budget review (C/BR) baseline. Some terms, e.g., combined trainer, are being redefined. An overview of the study activities and a summary of study results are given here.

Source record↗

Application of automation and robotics to lunar surface human exploration operations

Major results of a study applying automation and robotics to lunar surface base buildup and operations concepts are reported. The study developed a reference base scenario with specific goals, equipment concepts, robot concepts, activity schedules and buildup manifests. It examined crew roles, contingency cases and system reliability, and proposed a set of technologies appropriate and necessary for effective lunar operations. This paper refers readers to four companion papers for quantitative details where appropriate.

Woodcock, Gordon R.↗

The Traverse Planning Process for the Drats 2010 Analog Field Simulations

Traverse planning concentrates on optimizing the science return within the overall objectives of planetary surface missions or their analog field simulations. Such simulations were conducted in the San Francisco Volcanic Field, northern Arizona, from Aug. 26 to Sept 17, 2010 and involved some 200 individuals in the field, with some 40 geoscientists composing the science team. The purpose of these Desert Research and Technology Studies (DRATS) is to exercise and evaluate developmental hardware, software and operational concepts in a mission-like, fully-integrated, setting under the direction of an onsite Mobile Mission Control Center(MMCC). DRATS 2010 focused on the simultaneous operation of 2 rovers, a historic first. Each vehicle was manned by an astronaut-commander and an experienced field geologist. Having 2 rovers and crews in the field mandated substantially more complex science and mission control operations compared to the single rover DRATS tests of 2008 and 2009, or the Apollo lunar missions. For instance, the science support function was distributed over 2 "back rooms", one for each rover, with both "tactical" teams operating independently and simultaneously during the actual traverses. Synthesis and integration of the daily findings and forward planning for the next day(s) was accomplished overnight by yet another "strategic" science team.

Horz, Friedrich↗

Achieving the Proper Balance Between Crew and Public Safety

A paramount objective of all human-rated launch and reentry vehicle developers is to ensure that the risks to both the crew onboard and the public are minimized within reasonable cost, schedule, and technical constraints. Past experience has shown that proper attention to range safety requirements necessary to ensure public safety must be given early in the design phase to avoid additional operational complexities or threats to the safety of people onboard, and the design engineers must give these requirements the same consideration as crew safety requirements. For human spaceflight, the primary purpose and operational concept for any flight safety system is to protect the public while maximizing the likelihood of crew survival. This paper will outline the policy considerations, technical issues, and operational impacts regarding launch and reentry vehicle failure scenarios where crew and public safety are intertwined and thus addressed optimally in an integrated manner. An overview of existing range and crew safety policy requirements will be presented. Application of these requirements and lessons learned from both the Space Shuttle and Constellation Programs will also be discussed. Using these past programs as examples, the paper will detail operational, design, and analysis approaches to mitigate and balance the risks to people onboard and in the public. Manned vehicle perspectives from the Federal Aviation Administration (FAA) and Air Force organizations that oversee public safety will be summarized as well. Finally, the paper will emphasize the need to factor policy, operational, and analysis considerations into the early design trades of new vehicles to help ensure that both crew and public safety are maximized to the greatest extent possible.

Gowan, John↗

Space shuttle avionics system

The Space Shuttle avionics system, which was conceived in the early 1970's and became operational in the 1980's represents a significant advancement of avionics system technology in the areas of systems and redundacy management, digital data base technology, flight software, flight control integration, digital fly-by-wire technology, crew display interface, and operational concepts. The origins and the evolution of the system are traced; the requirements, the constraints, and other factors which led to the final configuration are outlined; and the functional operation of the system is described. An overall system block diagram is included.

Hanaway, John F.↗

Real Time Metrics and Analysis of Integrated Arrival, Departure, and Surface Operations

A real time dashboard was developed in order to inform and present users notifications and integrated information regarding airport surface operations. The dashboard is a supplement to capabilities and tools that incorporate arrival, departure, and surface air-traffic operations concepts in a NextGen environment. As trajectory-based departure scheduling and collaborative decision making tools are introduced in order to reduce delays and uncertainties in taxi and climb operations across the National Airspace System, users across a number of roles benefit from a real time system that enables common situational awareness. In addition to shared situational awareness the dashboard offers the ability to compute real time metrics and analysis to inform users about capacity, predictability, and efficiency of the system as a whole. This paper describes the architecture of the real time dashboard as well as an initial set of metrics computed on operational data. The potential impact of the real time dashboard is studied at the site identified for initial deployment and demonstration in 2017; Charlotte-Douglas International Airport. Analysis and metrics computed in real time illustrate the opportunity to provide common situational awareness and inform users of metrics across delay, throughput, taxi time, and airport capacity. In addition, common awareness of delays and the impact of takeoff and departure restrictions stemming from traffic flow management initiatives are explored. The potential of the real time tool to inform the predictability and efficiency of using a trajectory-based departure scheduling system is also discussed.

integrated arrival departure surface operations↗

EVA Suit Studies: Human Forward Contamination Project

Background: NASA Strategic Knowledge Gap B5: Forward Contamination for Mars. Issue: we have knowledge gaps!: Whether / how microbes are released from crewed pressure systems. Why do we care?: Informs Mars operational concepts - How to protect the science; Informs architecture decisions - How “open” Environmental Control and Life Support (ECLS) systems are; Informs landing site selection decisions - How close we can land / operate to where life may be present. Project goal: get some data to fill in these gaps: Data will help determine whether we’re ready to go to Mars, or if we need to change our systems or operational designs.

Rucker, Michelle↗

Aeolus -A Mission to Study the Thermal and Wind Environment of Mars

Aeolus is a small satellite mission to observe surface and atmospheric forcing and general circulation of Mars, by measuring surface energy balance, atmospheric temperatures, aerosols and clouds, and winds. Critically, Aeolus will make these measurements at all local times of day, providing information on both seasonal and diurnal variability. To date, direct measurements of Martian wind speeds have only been possible at the surface, only during daylight hours, and over small areas limited by rover traverse capabilities. From orbit, thermal measurements (e.g., estimates from assumed geostrophic balance) as well as images of dust storms and dune migration have provided inputs to derive current data sets on Martian winds. However, Mars General Circulation models demonstrate that wind speeds derived from these indirect measurements may be in error by 50 to 100%. For this reason, direct wind velocity measurements have been deemed "High Priority" by MEPAG (Mars Exploration Program Analysis Group); measuring wind speeds and corresponding thermal data is vital to understanding the climate of Mars. Aeolus will carry four Spatial Heterodyne Spectrometers (SHS), coupled to two orthogonal viewing telescopes. These high-resolution near-infrared spectrometers will measure CO2 (daytime absorption) and O2 (day and night emission) lines in the Martian atmosphere. Doppler shifts in these lines can be measured during Martian day and night, resolving wind speeds down to ~5 m/s. Orthogonal views allow the spectrometers to capture wind vectors over all observation locations. Aeolus will also carry the atmospheric limb-viewing Thermal Limb Sounder (TLS) to measure atmospheric temperatures, water ice clouds, and dust abundances across all altitudes where winds are measured. Finally, the Surface Radiometric Sensor Package (SuRSeP), a nadir viewing radiometer, will measure the total reflected solar and emitted thermal radiance, surface temperature, and water cloud and dust total column abundances. The combined spectral and thermal measurements will provide a new understanding of the global energy balance, dust transport processes, and climate cycles in the Martian atmosphere. Aeolus will consist of a single satellite in a near-polar orbit, allowing it to pass over all local times, with the baseline mission observing all seasons of an entire Martian year (two Earth years). Aeolus was one of two Martian smallsat concepts selected for study through the Planetary Science Deep Space SmallSat Studies program. This talk will provide an overview of the mission, including science rationale, instruments, spacecraft, and mission operations concept.

and winds↗

Secure and Safe Assured Autonomy (S2A2)

Aviation’s future will likely see the integration of a wide variety of Advanced Air Mobility (AAM) systems including Unmanned Aerial Systems (UAS) for cargo/delivery, personal air vehicles, and commercial Urban Air Mobility (UAM)vehicles. However, substantial challenges exist that could delay (and possibly prevent) these developments and thus research is needed in a variety of areas to leverage technologies in autonomy, Air Traffic Management (ATM), multi-redundant flight systems architectures, and advanced wireless connectivity like 5G to meet these challenges. The goal of this ULI project is to develop new technologies and innovative operational concepts which will ensure safe, secure and robust integration of autonomous vehicles into Advanced Air Mobility-tailored transportation infrastructure. All this must be done while maintaining inter-operability with current civil air transportation systems and associated safety standards. The project is organized into four Technical Challenges (TCs) areas designed to provide unique UAM solutions and a transition roadmap for industry and government to utilize research product output.

Koushik Datta↗

Apollo experience report: Manned thermal-vacuum testing of spacecraft

Manned thermal-vacuum tests of the Apollo spacecraft presented many first-time problems in the areas of test philosophy, operational concepts, and program implementation. The rationale used to resolve these problems is explained and examined critically in view of actual experience. The series of 12 tests involving 1517 hours of chamber operating time resulted in the disclosure of numerous equipment and procedural deficiencies of significance to the flight mission. Test experience and results in view of subsequent flight experience confirmed that thermal-vacuum testing of integrated manned spacecraft provides a feasible, cost-effective, and safe technique with which to obtain maximum confidence in spacecraft flight worthiness early in the program.

Mclane, J. C., Jr.↗

Environmental Control and Life Support (ECLS) Hardware Commonality for Exploration Vehicles

In August 2011, the Environmental Control and Life Support Systems (ECLSS) technical community, along with associated stakeholders, held a workshop to review NASA s plans for Exploration missions and vehicles with two objectives: revisit the Exploration Atmospheres Working Group (EAWG) findings from 2006, and discuss preliminary ECLSS architecture concepts and technology choices for Exploration vehicles, identifying areas for potential common hardware or technologies to be utilized. Key considerations for selection of vehicle design total pressure and percent oxygen include operational concepts for extravehicular activity (EVA) and prebreathe protocols, materials flammability, and controllability within pressure and oxygen ranges. New data for these areas since the 2006 study were presented and discussed, and the community reached consensus on conclusions and recommendations for target design pressures for each Exploration vehicle concept. For the commonality study, the workshop identified many areas of potential commonality across the Exploration vehicles as well as with heritage International Space Station (ISS) and Shuttle hardware. Of the 36 ECLSS functions reviewed, 16 were considered to have strong potential for commonality, 13 were considered to have some potential commonality, and 7 were considered to have limited potential for commonality due to unique requirements or lack of sufficient heritage hardware. These findings, which will be utilized in architecture studies and budget exercises going forward, are presented in detail.

Carrasquillo, Robyn↗

Rapid Turnaround of Costing/Designing of Space Missions Operations

The Ground Segment Team (GST), at NASA's Jet Propulsion Laboratory in Pasadena, California, provides high-level mission operations concepts and cost estimates for projects that are in the formulation phase. GST has developed a tool to track costs, assumptions, and mission requirements, and to rapidly turnaround estimates for mission operations, ground data systems, and tracking for deep space and near Earth missions. Estimates that would often take several weeks to generate are now generated in minutes through the use of an integrated suite of cost models. The models were developed through interviews with domain experts in areas of Mission Operations, including but not limited to: systems engineering, payload operations, tracking resources, mission planning, navigation, telemetry and command, and ground network infrastructure. Data collected during interviews were converted into parametric cost models and integrated into one tool suite. The tool has been used on a wide range of missions from small Earth orbiters, to flagship missions like Cassini. The tool is an aid to project managers and mission planners as they consider different scenarios during the proposal and early development stages of their missions. The tool is also used for gathering cost related requirements and assumptions and for conducting integrated analysis of multiple missions.

Cost estimation↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗