Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission management ground data systems”

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 73 records · Page 4

Marshall Space Flight Center Ground Systems Development and Integration

Ground Systems Development and Integration performs a variety of tasks in support of the Mission Operations Laboratory (MOL) and other Center and Agency projects. These tasks include various systems engineering processes such as performing system requirements development, system architecture design, integration, verification and validation, software development, and sustaining engineering of mission operations systems that has evolved the Huntsville Operations Support Center (HOSC) into a leader in remote operations for current and future NASA space projects. The group is also responsible for developing and managing telemetry and command configuration and calibration databases. Personnel are responsible for maintaining and enhancing their disciplinary skills in the areas of project management, software engineering, software development, software process improvement, telecommunications, networking, and systems management. Domain expertise in the ground systems area is also maintained and includes detailed proficiency in the areas of real-time telemetry systems, command systems, voice, video, data networks, and mission planning systems.

Wade, Gina↗

Progress Towards a 2012 Landsat Launch

The Landsat Data Continuity Mission (LDCM) is on schedule for a December 2012 launch date. The mission is being managed by an interagency partnership between NASA and the U.S. Geological Survey (USGS). NASA leads the development and launch of the satellite observatory while leads ground system development. USGS will assume responsibility for operating the satellite and for collecting, archiving, and distributing the LDCM data following launch. When launched the satellite will carry two sensors into orbit. The Operational Land Imager (OLI) will collect data for nine shortwave spectral bands with a spatial resolution of 30 m (with a 15 m panchromatic band). The Thermal Infrared Sensor (TIRS) will coincidently collect data for two thermal infrared bands with a spatial resolution of 100 m. The OLI is fully assembled and tested and has been shipped by it?s manufacturer, Ball Aerospace and Technology Corporation, to the Orbital Sciences Corporation (Orbital) facility where it is being integrated onto the LDCM spacecraft. Pre-launch testing indicates that OLI will meet all performance specification with margin. TIRS is in development at the NASA Goddard Space Flight Center (GSFC) and is in final testing before shipping to the Orbital facility in January, 2012. The ground data processing system is in development at the USGS Earth Resources Observation and Science (EROS) Center. The presentation will describe the LDCM satellite system, provide the status of system development, and present prelaunch performance data for OLI and TIRS. The USGS has committed to renaming the satellite as Landsat 8 following launch.

Irons, Jim↗

From Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn GDS Team met the SC Sim integration challenge in eight months. The GDS System Engineering approach in response to the SC Simintegration challenge, focused on a set of key practices: decomposition of project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; risk management thru management of expectations; and aggregation of intermediate products into a final product. By maintaining a a system-level focus, the overall systems engineering process unified team GDS Team members with a common goal: the success of the ground system as a whole and not just the success of their individual expert contributions. Incorporation of Agile-type development efforts were aligned with a risk strategy based on team-oriented principles and expectations management, thus achieving a more stable baseline solution without compromising the integrity of the GDS design.

Dawn Mission↗

Data Distribution System (DDS) and Solar Dynamic Observatory Ground Station (SDOGS) Integration Manager

The DDS SDOGS Integration Manager (DSIM) provides translation between native control and status formats for systems within DDS and SDOGS, and the ASIST (Advanced Spacecraft Integration and System Test) control environment in the SDO MOC (Solar Dynamics Observatory Mission Operations Center). This system was created in response for a need to centralize remote monitor and control of SDO Ground Station equipments using ASIST control environment in SDO MOC, and to have configurable table definition for equipment. It provides translation of status and monitoring information from the native systems into ASIST-readable format to display on pages in the MOC. The manager is lightweight, user friendly, and efficient. It allows data trending, correlation, and storing. It allows using ASIST as common interface for remote monitor and control of heterogeneous equipments. It also provides failover capability to back up machines.

Pham, Kim↗

Automation of Hubble Space Telescope Mission Operations

On June 13, 2011, after more than 21 years, 115 thousand orbits, and nearly 1 million exposures taken, the operation of the Hubble Space Telescope successfully transitioned from 24x7x365 staffing to 815 staffing. This required the automation of routine mission operations including telemetry and forward link acquisition, data dumping and solid-state recorder management, stored command loading, and health and safety monitoring of both the observatory and the HST Ground System. These changes were driven by budget reductions, and required ground system and onboard spacecraft enhancements across the entire operations spectrum, from planning and scheduling systems to payload flight software. Changes in personnel and staffing were required in order to adapt to the new roles and responsibilities required in the new automated operations era. This paper will provide a high level overview of the obstacles to automating nominal HST mission operations, both technical and cultural, and how those obstacles were overcome.

Burley, Richard↗

Radiation protection and instrumentation

Radiation was found not to be an operational problem during the Apollo program. Doses received by the crewmen of Apollo missions 7 through 17 were small because no major solar-particle events occurred during those missions. One small event was detected by a radiation sensor outside the Apollo 12 spacecraft, but no increase in radiation dose to the crewmen inside the spacecraft was detected. Radiation protection for the Apollo program was focused on both the peculiarities of the natural space radiation environment and the increased prevalence of manmade radiation sources on the ground and onboard the spacecraft. Radiation-exposure risks to crewmen were assessed and balanced against mission gain to determine mission constraints. Operational radiation evaluation required specially designed radiation detection systems onboard the spacecraft in addition to the use of satellite data, solar observatory support, and other liaison. Control and management of radioactive sources and radiation-generating equipment was important in minimizing radiation exposure of ground-support personnel, researchers, and the Apollo flight and backup crewmen.

J. Vernon Bailey↗

ASF Design Considerations for Radarsat/ERS-2

This paper examines the requirements and the design considerations of the Synthetic Aperture Radar (SAR) ground data system for the Alaska SAR Facility (ASF) at the University of Alaska in Fairbanks (UAF) for the new era of Radarsat/ERS-2 missions. These include a new data acquisition planning capability to manage more satellites with global planning and to manage more than one instrument mode; a new archive strategy that is cheaper, faster, and better; a product generation system to produce data on demand and to produce data for the varied instruments and modes; and a product verification ability for the new and old products. In response to these new functional requirements, JPL is using a design approach that emphasizes an open systems, client/server architecture based on industry standards and commercial off-the-shelf technology.

Radarsat/ERS-2 ground data system upgrade↗

Creative Analytics of Mission Ops Event Messages

Historically, tremendous effort has been put into processing and displaying mission health and safety telemetry data; and relatively little attention has been paid to extracting information from missions time-tagged event log messages. Todays missions may log tens of thousands of messages per day and the numbers are expected to dramatically increase as satellite fleets and constellations are launched, as security monitoring continues to evolve, and as the overall complexity of ground system operations increases. The logs may contain information about orbital events, scheduled and actual observations, device status and anomalies, when operators were logged on, when commands were resent, when there were data drop outs or system failures, and much much more. When dealing with distributed space missions or operational fleets, it becomes even more important to systematically analyze this data. Several advanced information systems technologies make it appropriate to now develop analytic capabilities which can increase mission situational awareness, reduce mission risk, enable better event-driven automation and cross-mission collaborations, and lead to improved operations strategies: Industry Standard for Log Messages. The Object Management Group (OMG) Space Domain Task Force (SDTF) standards organization is in the process of creating a formal standard for industry for event log messages. The format is based on work at NASA GSFC. Open System Architectures. The DoD, NASA, and others are moving towards common open system architectures for mission ground data systems based on work at NASA GSFC with the full support of the commercial product industry and major integration contractors. Text Analytics. A specific area of data analytics which applies statistical, linguistic, and structural techniques to extract and classify information from textual sources. This presentation describes work now underway at NASA to increase situational awareness through the collection of non-telemetry mission operations information into a common log format and then providing display and analytics tools to provide in-depth assessment of the log contents. The work includes: Common interface formats for acquiring time-tagged text messages Conversion of common files for schedules, orbital events, and stored commands to the common log format Innovative displays to depict thousands of messages on a single display Structured English text queries against the log message data store, extensible to a more mature natural language query capability Goal of speech-to-text and text-to-speech additions to create a personal mission operations assistant to aid on-console operations. A wide variety of planned uses identified by the mission operations teams will be discussed.

events↗

Enabling Future Science and Human Exploration with NASA's Next Generation near Earth and Deep Space Communications and Navigation Architecture

The National Aeronautics and Space Administration (NASA) is studying alternatives for the United States space communications architecture through the 2040 timeframe. This architecture provides communication and navigation services to both human exploration and science missions throughout the solar system. Several of NASA's key space assets are approaching their end of design life and major systems are in need of replacement. The changes envisioned in the relay satellite architecture and capabilities around both Earth and Mars are significant undertakings and occur only once or twice each generation, and therefore is referred to as NASA's next generation space communications architecture. NASA's next generation architecture will benefit from technology and services developed over recent years. These innovations will provide missions with new operations concepts, increased performance, and new business and operating models. Advancements in optical communications will enable high-speed data channels and the use of new and more complex science instruments. Modern multiple beam/multiple access technologies such as those employed on commercial high throughput satellites will enable enhanced capabilities for on-demand service, and with new protocols will help provide Internet-like connectivity for cooperative spacecraft to improve data return and coordinate joint mission objectives. On-board processing with autonomous and cognitive networking will play larger roles to help manage system complexity. Spacecraft and ground systems will coordinate among themselves to establish communications, negotiate link connectivity, and learn to share spectrum to optimize resource allocation. Spacecraft will autonomously navigate, plan trajectories, and handle off-nominal events. NASA intends to leverage the ever-expanding capabilities of the satellite communications industry and foster its continued growth. NASA's technology development will complement and extend commercial capabilities to meet unique space environment requirements and to provide capabilities that are beyond the commercial marketplace. The progress of the communications industry, including the emerging global space internet segment and its planned constellations of 100's of satellites offer additional opportunities for new capability and mission concepts. The opportunities and challenges of a future space architecture require an optimal solution encompassing a global perspective. The concepts and technologies intentionally define an architecture that applies not only to NASA, but to other U.S. government agencies, international space and government agencies, and domestic and international industries to advance the openness, interoperability, and affordability of space communications. Cooperation among the worlds space agencies, their capabilities, standards, operations, and interoperability are key to advancing humankind's understand of the universe and extending human presence into the solar system.

Communications↗

Enabling Future Science and Human Exploration with NASA's Next Generation Near Earth and Deep Space Communications and Navigation Architecture

The National Aeronautics and Space Administration (NASA) is studying alternatives for the United States space communications architecture through the 2040 timeframe. This architecture provides communication and navigation services to both human exploration and science missions throughout the solar system. Several of NASA's key space assets are approaching their end of design life and major systems are in need of replacement. The changes envisioned in the relay satellite architecture and capabilities around both Earth and Mars are significant undertakings and occur only once or twice each generation, and therefore is referred to as NASA's next generation space communications architecture. NASA's next generation architecture will benefit from technology and services developed over recent years. These innovations will provide missions with new operations concepts, increased performance, and new business and operating models. Advancements in optical communications will enable high-speed data channels and the use of new and more complex science instruments. Modern multiple beam/multiple access technologies such as those employed on commercial high throughput satellites will enable enhanced capabilities for on-demand service, and with new protocols will help provide Internet-like connectivity for cooperative spacecraft to improve data return and coordinate joint mission objectives. On-board processing with autonomous and cognitive networking will play larger roles to help manage system complexity. Spacecraft and ground systems will coordinate among themselves to establish communications, negotiate link connectivity, and learn to share spectrum to optimize resource allocation. Spacecraft will autonomously navigate, plan trajectories, and handle off-nominal events. NASA intends to leverage the ever-expanding capabilities of the satellite communications industry and foster its continued growth. NASA's technology development will complement and extend commercial capabilities to meet unique space environment requirements and to provide capabilities that are beyond the commercial marketplace. The progress of the communications industry, including the emerging global space internet segment and its planned constellations of 100's of satellites offer additional opportunities for new capability and mission concepts. The opportunities and challenges of a future space architecture require an optimal solution encompassing a global perspective. The concepts and technologies intentionally define an architecture that applies not only to NASA, but to other U.S. government agencies, international space and government agencies, and domestic and international industries to advance the openness, interoperability, and affordability of space communications. Cooperation among the worlds space agencies, their capabilities, standards, operations, and interoperability are key to advancing humankinds understand of the universe and extending human presence into the solar system.

deep space↗

The SAX Italian scientific satellite. The on-board implemented automation as a support to the ground control capability

This paper presents the capabilities implemented in the SAX system for an efficient operations management during its in-flight mission. SAX is an Italian scientific satellite for x-ray astronomy whose major mission objectives impose quite tight constraints on the implementation of both the space and ground segment. The most relevant mission characteristics require an operative lifetime of two years, performing scientific observations both in contact and in noncontact periods, with a low equatorial orbit supported by one ground station, so that only a few minutes of communications are available each orbit. This operational scenario determines the need to have a satellite capable of performing the scheduled mission automatically and reacting autonomously to contingency situations. The implementation approach of the on-board operations management, through which the necessary automation and autonomy are achieved, follows a hierarchical structure. This has been achieved adopting a distributed avionic architecture. Nine different on-board computers, in fact, constitute the on-board data management system. Each of them performs the local control and monitors its own functions while the system level control is performed at a higher level by the data handling applications software. The SAX on-board architecture provides the ground operators with different options of intervention by three classes of telecommands. The management of the scientific operations will be scheduled by the operation control center via dedicated operating plans. The SAX satellite flight mode is presently being integrated at Alenia Spazio premises in Turin for a launch scheduled for the end of 1995. Once in orbit, the SAX satellite will be subject to intensive check-out activities in order to verify the required mission performances. An overview of the envisaged procedure and of the necessary on-ground activities is therefore depicted as well.

Martelli, Andrea↗

STEREO Superior Solar Conjunction Mission Phase

With its long duration and high gain antenna (HGA) feed thermal constraint; the NASA Solar-TErestrial RElations Observatory (STEREO) solar conjunction mission phase is quite unique to deep space operations. Originally designed for a two year heliocentric orbit mission to primarily study coronal mass ejection propagation, after 8 years of continuous science data collection, the twin STEREO observatories entered the solar conjunction mission phase, for which they were not designed. Nine months before entering conjunction, an unforeseen thermal constraint threatened to stop daily communications and science data collection for 15months. With a 3.5 month long communication blackout from the superior solar conjunction, without ground commands, each observatory will reset every 3 days, resulting in 35 system resets at an Earth range of 2 AU. As the observatories will be conjoined for the first time in 8 years, a unique opportunity for calibrating the same instruments on identical spacecraft will occur. As each observatory has lost redundancy, and with only a limited fidelity hardware simulator, how can the new observatory configuration be adequately and safely tested on each spacecraft? Without ground commands, how would a 3-axis stabilized spacecraft safely manage the ever accumulating system momentum without using propellant for thrusters? Could science data still be collected for the duration of the solar conjunction mission phase? Would the observatories survive? In its second extended mission, operational resources were limited at best. This paper discusses the solutions to the STEREO superior solar conjunction operational challenges, science data impact, testing, mission operations, results, and lessons learned while implementing.

STEREO↗

MOS 2.0: The Next Generation in Mission Operations Systems

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits that this top-down, architectural approach holds for creating a more flexible and capable MOS for Missions while holding the line on cost.

ground systems↗

Mars Observer Orbit Insertion Briefing

Steve Wall is the host of this video entitled, "Return to the Red Planet". Live animation of the Mars Observer orbiting Mars is presented. Steve Wall explains the spacecraft insertion maneuver and also explains the purpose for the Mars Observer launch. Live coverage of the Cape Canaveral launch of the Mars Observer is also presented. Suzanne Dodd, Chief of the Mission Planning team describes the burn start and how the spacecraft will be captured by Mars' gravity. Glenn Cunningham, Mars Observer Project Manager, gives background information on the Mars Observer and describes the organizations behind the Mars Observer Spacecraft, such as the Deep Space Network, the Mission Operation Support Office, Science Investigators, the Flight Engineering Office, Operations Office, and the Ground Data System Office. Dr. William Piotrowski, Acting Director, Solar System Exploration Division, NASA, talks about the purpose of the Mars Pathfinder which is to develop the technology and systems for landing small science packages on Mars. Mr. Roger Gibbs, Former Mars Observer Spacecraft Systems Engineer, tells us how the Mars Observer was built and describes the structural elements on the Mars Observer. The 11-month cruise period for the spacecraft is given by Joseph Beerer, Manager of the Engineering office. The thrust for the Mars Orbit Insertion is described by Ronald Klemetson, Technical Manager, Propulsion Subsystem Jet Propulsion Laboratory (JPL). George Chen, Lead Engineer Attitude and Articulation Subsystem Spacecraft Team, explains the importance of the attitude control engines on the Spacecraft. Marvin Traxler, Manager of Tracking and Data Acquisition, describes how searching for a signal from the Mars Observer works. See NONP-NASA-VT-2000081555 for a continuation of this discussion with Marvin Traxler.

Source record↗

Earth Observatory Satellite system definition study. Report no. 5: System design and specifications. Part 2: Ground system element specifications

The Ground System requirements for the Land Resources Management (LRM) type-A and type-B missions of the Earth Observatory Satellite (EOS) program are presented. Specifications for the Thematic Mapper data processing are provided (LRM A mission). The specifications also cover the R and D instruments (Thematic Mapper and High Resolution Pointable Imager) data processing for the LRM type-B mission.

Source record↗

General Purpose Data-Driven Monitoring for Space Operations

As modern space propulsion and exploration systems improve in capability and efficiency, their designs are becoming increasingly sophisticated and complex. Determining the health state of these systems, using traditional parameter limit checking, model-based, or rule-based methods, is becoming more difficult as the number of sensors and component interactions grow. Data-driven monitoring techniques have been developed to address these issues by analyzing system operations data to automatically characterize normal system behavior. System health can be monitored by comparing real-time operating data with these nominal characterizations, providing detection of anomalous data signatures indicative of system faults or failures. The Inductive Monitoring System (IMS) is a data-driven system health monitoring software tool that has been successfully applied to several aerospace applications. IMS uses a data mining technique called clustering to analyze archived system data and characterize normal interactions between parameters. The scope of IMS based data-driven monitoring applications continues to expand with current development activities. Successful IMS deployment in the International Space Station (ISS) flight control room to monitor ISS attitude control systems has led to applications in other ISS flight control disciplines, such as thermal control. It has also generated interest in data-driven monitoring capability for Constellation, NASA's program to replace the Space Shuttle with new launch vehicles and spacecraft capable of returning astronauts to the moon, and then on to Mars. Several projects are currently underway to evaluate and mature the IMS technology and complementary tools for use in the Constellation program. These include an experiment on board the Air Force TacSat-3 satellite, and ground systems monitoring for NASA's Ares I-X and Ares I launch vehicles. The TacSat-3 Vehicle System Management (TVSM) project is a software experiment to integrate fault and anomaly detection algorithms and diagnosis tools with executive and adaptive planning functions contained in the flight software on-board the Air Force Research Laboratory TacSat-3 satellite. The TVSM software package will be uploaded after launch to monitor spacecraft subsystems such as power and guidance, navigation, and control (GN&C). It will analyze data in real-time to demonstrate detection of faults and unusual conditions, diagnose problems, and react to threats to spacecraft health and mission goals. The experiment will demonstrate the feasibility and effectiveness of integrated system health management (ISHM) technologies with both ground and on-board experiments.

Iverson, David L.↗

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↗