Search NASA⌕ Search

SEARCH · Search NASA

Results for “Building Business Network”

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.

16 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

Business is Beaming

Terabeam has developed a Fiberless Optical(TM) Network that transmits broadband data from office buildings to the nation's wide-area networks (WANs), without digging up the streets. A key component of Terabeam's Fiberless Network is Large Aperture Holographic Optic technology, developed by Ralcon Development Lab, of Paradise, Utah. Ralcon developed the Holographic Optical Element (HOE) technology with assistance from a NASA Goddard Space Flight Center Small Business Innovation Research (SBIR) contract. Terabeam further developed the HOE technology and incorporated it into its Fiberless Optical Network-sending an immeasurable amount of information soaring overhead. Terabeam developed its Fiberless Optical Network using a proprietary HOE to transmit data. The unit is mounted near an office window and has the ability to beam safe, low-power, invisible data through the air at gigabits-per-second speeds to anywhere in the service area. Gigabits-per-second speeds are thousands of times faster than the speeds of current broadband transmissions. This allows businesses to connect to local-area networks (LANs) as well as WANs, in a quick and affordable manner.

Source record↗
NASA NTRS2022

Lunar Communications Services with Emphasis on Commercialization

In mid-2020 Lockheed Marin Space (LM) and NASA’s Jet Propulsion Laboratory (JPL) formed a working group to study and address the need for a lunar communications network to service a growing lunar economy, beginning with the initial crewed and robotic mission needs in 2024. Multiple commercial relay architectures were studied and evaluated for platform requirements, communications capabilities, and commercial business viability in a growing ecosystem. The evolution of communications needs around the Moon were mapped to infrastructure build out. Trade studies were performed to evaluate reliability and lifetime requirements, and the viability of various data protocols. Mission concepts and operations plans were developed for both initial mission support and future autonomous network support. This work has led to Lockheed Martin and JPL to evaluate a single dedicated relay satellite in a frozen lunar orbit, with simultaneous coverage of the far-side and south pole landing sites for over 10 hours per day as a first step towards a comprehensive solution to lunar connectivity. This first satellite is compatible with an ESPA Grande launch volume and would be capable of launching on a rideshare into a variety of orbits and trajectories. The satellite is equipped with both high- and low-rate communications relay payloads with software-defined radios and a delay/disruption tolerant networking protocol. The system is designed to service initial and future mission needs in a commercialized manner, enabling a new class of missions to the Moon. The relay satellite leverages prior spacecraft platform work with on-orbit heritage in a lunar environment expected by 2023.

Davarian, Faramaz↗
NASA NTRS1993

Data communication network at the ASRM facility

The main objective of the report is to present the overall communication network structure for the Advanced Solid Rocket Motor (ASRM) facility being built at Yellow Creek near Iuka, Mississippi. This report is compiled using information received from NASA/MSFC, LMSC, AAD, and RUST Inc. As per the information gathered, the overall network structure will have one logical FDDI ring acting as a backbone for the whole complex. The buildings will be grouped into two categories viz. manufacturing critical and manufacturing non-critical. The manufacturing critical buildings will be connected via FDDI to the Operational Information System (OIS) in the main computing center in B 1000. The manufacturing non-critical buildings will be connected by 10BASE-FL to the Business Information System (BIS) in the main computing center. The workcells will be connected to the Area Supervisory Computers (ASCs) through the nearest manufacturing critical hub and one of the OIS hubs. The network structure described in this report will be the basis for simulations to be carried out next year. The Comdisco's Block Oriented Network Simulator (BONeS) will be used for the network simulation. The main aim of the simulations will be to evaluate the loading of the OIS, the BIS, the ASCs, and the network links by the traffic generated by the workstations and workcells throughout the site.

Moorhead, Robert J., II↗
NASA NTRS1993

Data communication network at the ASRM facility

This report describes the simulation of the overall communication network structure for the Advanced Solid Rocket Motor (ASRM) facility being built at Yellow Creek near Iuka, Mississippi as of today. The report is compiled using information received from NASA/MSFC, LMSC, AAD, and RUST Inc. As per the information gathered, the overall network structure will have one logical FDDI ring acting as a backbone for the whole complex. The buildings will be grouped into two categories viz. manufacturing intensive and manufacturing non-intensive. The manufacturing intensive buildings will be connected via FDDI to the Operational Information System (OIS) in the main computing center in B_1000. The manufacturing non-intensive buildings will be connected by 10BASE-FL to the OIS through the Business Information System (BIS) hub in the main computing center. All the devices inside B_1000 will communicate with the BIS. The workcells will be connected to the Area Supervisory Computers (ASCs) through the nearest manufacturing intensive hub and one of the OIS hubs. Comdisco's Block Oriented Network Simulator (BONeS) has been used to simulate the performance of the network. BONeS models a network topology, traffic, data structures, and protocol functions using a graphical interface. The main aim of the simulations was to evaluate the loading of the OIS, the BIS, and the ASCs, and the network links by the traffic generated by the workstations and workcells throughout the site.

Moorhead, Robert J., II↗
NASA NTRS2001

Developing Distributed Collaboration Systems at NASA: A Report from the Field

Web-based collaborative systems have assumed a pivotal role in the information systems development arena. While business to customers (B-to-C) and business to business (B-to-B) electronic commerce systems, search engines, and chat sites are the focus of attention, web-based systems span the gamut of information systems that were traditionally confined to internal organizational client server networks. For example, the Domino Application Server allows Lotus Notes (trademarked) uses to build collaborative intranet applications and mySAP.com (trademarked) enables web portals and e-commerce applications for SAP users. This paper presents the experiences in the development of one such system: Postdoc, a government off-the-shelf web-based collaborative environment. Issues related to the design of web-based collaborative information systems, including lessons learned from the development and deployment of the system as well as measured performance, are presented in this paper. Finally, the limitations of the implementation approach as well as future plans are presented as well.

Becerra-Fernandez, Irma↗
NASA NTRS1997

The NASA Integrated Information Technology Architecture

This document defines an Information Technology Architecture for the National Aeronautics and Space Administration (NASA), where Information Technology (IT) refers to the hardware, software, standards, protocols and processes that enable the creation, manipulation, storage, organization and sharing of information. An architecture provides an itemization and definition of these IT structures, a view of the relationship of the structures to each other and, most importantly, an accessible view of the whole. It is a fundamental assumption of this document that a useful, interoperable and affordable IT environment is key to the execution of the core NASA scientific and project competencies and business practices. This Architecture represents the highest level system design and guideline for NASA IT related activities and has been created on the authority of the NASA Chief Information Officer (CIO) and will be maintained under the auspices of that office. It addresses all aspects of general purpose, research, administrative and scientific computing and networking throughout the NASA Agency and is applicable to all NASA administrative offices, projects, field centers and remote sites. Through the establishment of five Objectives and six Principles this Architecture provides a blueprint for all NASA IT service providers: civil service, contractor and outsourcer. The most significant of the Objectives and Principles are the commitment to customer-driven IT implementations and the commitment to a simpler, cost-efficient, standards-based, modular IT infrastructure. In order to ensure that the Architecture is presented and defined in the context of the mission, project and business goals of NASA, this Architecture consists of four layers in which each subsequent layer builds on the previous layer. They are: 1) the Business Architecture: the operational functions of the business, or Enterprise, 2) the Systems Architecture: the specific Enterprise activities within the context of IT systems, 3) the Technical Architecture: a common, vendor-independent framework for design, integration and implementation of IT systems and 4) the Product Architecture: vendor=specific IT solutions. The Systems Architecture is effectively a description of the end-user "requirements". Generalized end-user requirements are discussed and subsequently organized into specific mission and project functions. The Technical Architecture depicts the framework, and relationship, of the specific IT components that enable the end-user functionality as described in the Systems Architecture. The primary components as described in the Technical Architecture are: 1) Applications: Basic Client Component, Object Creation Applications, Collaborative Applications, Object Analysis Applications, 2) Services: Messaging, Information Broker, Collaboration, Distributed Processing, and 3) Infrastructure: Network, Security, Directory, Certificate Management, Enterprise Management and File System. This Architecture also provides specific Implementation Recommendations, the most significant of which is the recognition of IT as core to NASA activities and defines a plan, which is aligned with the NASA strategic planning processes, for keeping the Architecture alive and useful.

Baldridge, Tim↗
NASA NTRS2014

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗
NASA NTRSDate not supplied

Corridor Design and Analysis for UAM Operations

The Urban Air Mobility (UAM) concept is a part of Advanced Air Mobility (AAM), a joint initiative between the Federal Aviation Administration (FAA), NASA, and industry to develop an air transportation system that uses new electric (i.e., green) air vehicles in geographical areas previously underserved by traditional aviation. Market forecast studies predict that there will be demand for alternate modes of air transportation using electric Vertical Take-off and Landing aircraft. UAM expands transportation networks by introducing short flights to move people and goods around metropolitan areas​. UAM is expected to improve mobility for the public, decongest road traffic, reduce trip time, and decrease strain on existing public transportation networks. Various challenges exist to make the introduction of UAM operations successful in the U.S. National Airspace System (NAS). These include but are not limited to integration with existing airports and airspace, provision of air traffic services (e.g., separation), vehicle design and certification, and community acceptance. The focus of this paper is on integration of UAM operations into the NAS via introduction of new airspace structures. UAM will operate within a regulatory, operational, and technical environment that is incorporated into the NAS​. As per the UAM Concept of Operations (ConOps), the FAA retains regulatory authority and is responsible for establishing operational parameters and maintaining oversight. The FAA’s UAM ConOps describes flights at low altitudes (below 5,000 ft) with minimal disruption to established conventional aircraft traffic and limited voice interactions with the Air Traffic Control (ATC). Early stages of UAM may use existing procedures to safely integrate UAM with conventional flights. This would involve flying under Part 91 Visual Flight Rules (VFR) and using voice for communications. The initial UAM ecosystem will utilize the current infrastructure such as routes, helipads, and ATC services, where practicable. ​A NASA study explored the use of existing helicopter routes in Dallas Fort Worth (DFW) airspace for initial UAM operations with a Letter of Agreement (LOA) that included procedures to request a Class B (controlled airspace) clearance. The research showed that the chosen approach was feasible for near-term, low-demand UAM traffic, but was not scalable. The growth of operations in today’s aviation system has resulted in airspace reorganization and procedures to ensure safety and efficiency as traffic rates increase. One proposed operating innovation that can help with the scalability of UAM is establishing routes and corridors. This may look similar to the Area Navigation (RNAV) procedures used today to streamline operations into busy airports. However, instead of FAA automation systems and ATC managing the flow of traffic, some UAM concepts envision a third-party service provider performing this role as part of the Provider of Services for UAM (PSU) network. The FAA’s UAM ConOps posits that new airspace structures such as UAM corridors include the following design criteria: 1) Minimal impact on existing NAS operations, 2) no or minimal additional ATC services, 3) public interest considerations such as noise, safety, and security, and 4) customer needs. The airspace available in urban environments is limited by the height of buildings, the effect of weather including wind gusts, privacy needs, and a clearance envelope. The new airspace structure would need to be designed around large airports and urban areas where the initial market demand is likely to exist. NASA has started evaluating airspace in the Dallas Fort Worth area to design new airspace structures, keeping the first two design criteria in mind. It is assumed that there will be an on-board pilot-in-command, and the flights will operate under VFR in Visual Meteorological Conditions. Corridors will be required in controlled airspace, whereas UAM operations can fly in uncontrolled Class G and E airspace using current day rules. Keeler et. al identified factors and heuristics for development of routes for UAM operations for integration with airspace close to large airports such as Dallas Fort Worth and Dallas Love Field. This paper describes the heuristics applied to define the corridors, analyzes them with respect to legacy traffic and presents key results.

Urban Air Mobility↗
NASA NTRS2004

NASA GSFC's Role in the US Space Program

The paper discussss the GSFC research interests and how GSFC contributes to solve some of most basic questions Humans having been asking for thousands of years. How big is universe? How old is the universe? Will Humans and industrialization of the Earth change the climate significantly? Can Humans live in space? How does the Sun affect life on Earth? Goddard s role in Earth Science is very unique. We buy and build instruments that collect data about weather around the world. By flying those instruments on spacecraft, we have a unique vantage point to observe the weather patterns on a global scale. The best example is a satellite network called GOES (Geostationary Operational Environmental Satellite) which produces the weather pictures and videos you see on the nightly news and weather channel. Earth Science is another area of great interest to Goddard scientists and spacecraft designers. This photo of an oil fire in Iraq taken on March 2Ist of this year shows the down range effect pollution will have on entire region. Space Weather has become extremely important in the Space business. Satellites not only can become inoperable due to the occasional high level of radiation but astronauts can be exposed to dangerous levels of radiation. Space Weather is actually an issue when planning Extra Vehicular Activities (EVA). At Goddard, our operation of the Hubble Space Telescope has meant we have worked closely with several Shuttle crews over the years.

Simpson, James E.↗
NASA NTRS1993

ACE: A distributed system to manage large data archives

Competitive pressures in the oil and gas industry are requiring a much tighter integration of technical data into E and P business processes. The development of new systems to accommodate this business need must comprehend the significant numbers of large, complex data objects which the industry generates. The life cycle of the data objects is a four phase progression from data acquisition, to data processing, through data interpretation, and ending finally with data archival. In order to implement a cost effect system which provides an efficient conversion from data to information and allows effective use of this information, an organization must consider the technical data management requirements in all four phases. A set of technical issues which may differ in each phase must be addressed to insure an overall successful development strategy. The technical issues include standardized data formats and media for data acquisition, data management during processing, plus networks, applications software, and GUI's for interpretation of the processed data. Mass storage hardware and software is required to provide cost effective storage and retrieval during the latter three stages as well as long term archival. Mobil Oil Corporation's Exploration and Producing Technical Center (MEPTEC) has addressed the technical and cost issues of designing, building, and implementing an Advanced Computing Environment (ACE) to support the petroleum E and P function, which is critical to the corporation's continued success. Mobile views ACE as a cost effective solution which can give Mobile a competitive edge as well as a viable technical solution.

Daily, Mike I.↗
NASA NTRS2003

The Logical Extension

The same software controlling autonomous and crew-assisted operations for the International Space Station (ISS) is enabling commercial enterprises to integrate and automate manual operations, also known as decision logic, in real time across complex and disparate networked applications, databases, servers, and other devices, all with quantifiable business benefits. Auspice Corporation, of Framingham, Massachusetts, developed the Auspice TLX (The Logical Extension) software platform to effectively mimic the human decision-making process. Auspice TLX automates operations across extended enterprise systems, where any given infrastructure can include thousands of computers, servers, switches, and modems that are connected, and therefore, dependent upon each other. The concept behind the Auspice software spawned from a computer program originally developed in 1981 by Cambridge, Massachusetts-based Draper Laboratory for simulating tasks performed by astronauts aboard the Space Shuttle. At the time, the Space Shuttle Program was dependent upon paper-based procedures for its manned space missions, which typically averaged 2 weeks in duration. As the Shuttle Program progressed, NASA began increasing the length of manned missions in preparation for a more permanent space habitat. Acknowledging the need to relinquish paper-based procedures in favor of an electronic processing format to properly monitor and manage the complexities of these longer missions, NASA realized that Draper's task simulation software could be applied to its vision of year-round space occupancy. In 1992, Draper was awarded a NASA contract to build User Interface Language software to enable autonomous operations of a multitude of functions on Space Station Freedom (the station was redesigned in 1993 and converted into the international venture known today as the ISS)

Source record↗
NASA NTRS2018

Next-Generation NASA Earth-Orbiting Relay Satellites: Fusing Optical and Microwave Communications

NASA is currently considering architectures and concepts for the generation of relay satellites that will replace the Tracking and Data Relay Satellite (TDRS) constellation, which has been flying since 1983. TDRS-M, the last of the second TDRS generation, launched in August 2017, extending the life of the TDRS constellation beyond 2030. However, opportunities exist to re-engineer the concepts of geosynchronous Earth relay satellites. The needs of the relay satellite customers have changed dramatically over the last 34 years since the first TDRS launch. There is a demand for greater bandwidth as the availability of the traditional RF spectrum for space communications diminishes and the demand for ground station access grows. The next generation of NASA relay satellites will provide for operations that have factored in these new constraints. In this paper, we describe a heterogeneous constellation of geosynchronous relay satellites employing optical and RF communications. The new constellation will enable new optical communications services formed by user-to-space relay, space relay-to-space relay and space relay-to-ground links. It will build upon the experience from the Lunar Laser Communications Demonstration from 2013 and the Laser Communications Relay Demonstration to be launched in 2019.Simultaneous to establishment of the optical communications space segment, spacecraft in the TDRS constellation will be replaced with RF relay satellites with targeted subsets of the TDRS capabilities. This disaggregation of the TDRS service model will allow for flexibility in replenishing the needs of legacy users as well as addition of new capabilities for future users. It will also permit the U.S. government access to launch capabilities such as rideshare and to hosted payloads that were not previously available.In this paper, we also explore how the next generation of Earth relay satellites provides a significant boost in the opportunities for commercial providers to the communications space segment. For optical communications, the backbone of this effort is adoption of commercial technologies from the terrestrial high-bandwidth telecommunications industry into optical payloads. For RF communications, the explosion of software-defined radio, high-speed digital signal processing technologies and networking from areas such as 5G multicarrier will be important. Future commercial providers will not be limited to a small set of large aerospace companies. Ultimately, entirely government-owned and -operated satellite communications will phase out and make way for commercial business models that satisfy NASA's satellite communications requirements. The competition being provided by new entrants in the space communications business may result in a future in which all NASA communications needs can be satisfied commercially.

Space Communications↗
NASA NTRS2018

Next-Generation NASA Earth-Orbiting Relay Satellites: Fusing Microwave and Optical Communications

NASA is currently considering architectures and concepts for the generation of relay satellites that will replace the Tracking and Data Relay Satellite (TDRS) constellation, which has been flying since 1983. TDRS-M, the last of the second TDRS generation, launched in August 2017, extending the life of the TDRS constellation beyond 2030. However, opportunities exist to re-engineer the concepts of geosynchronous Earth relay satellites. The needs of the relay satellite customers have changed dramatically over the last 34 years since the first TDRS launch. There is a demand for greater bandwidth as the availability of the traditional RF spectrum for space communications diminishes and the demand for ground station access grows. The next generation of NASA relay satellites will provide for operations that have factored in these new constraints. In this paper, we describe a heterogeneous constellation of geosynchronous relay satellites employing optical and RF communications. The new constellation will enable new optical communications services formed by user-to-space relay, space relay-to-space relay and space relay-to-ground links. It will build upon the experience from the Lunar Laser Communications Demonstration from 2013 and the Laser Communications Relay Demonstration to be launched in 2019.Simultaneous to establishment of the optical communications space segment, spacecraft in the TDRS constellation will be replaced with RF relay satellites with targeted subsets of the TDRS capabilities. This disaggregation of the TDRS service model will allow for flexibility in replenishing the needs of legacy users as well as addition of new capabilities for future users. It will also permit the U.S. government access to launch capabilities such as rideshare and to hosted payloads that were not previously available. In this paper, we also explore how the next generation of Earth relay satellites provides a significant boost in the opportunities for commercial providers to the communications space segment. For optical communications, the backbone of this effort is adoption of commercial technologies from the terrestrial high-bandwidth telecommunications industry into optical payloads. For RF communications, the explosion of software-defined radio, high-speed digital signal processing technologies and networking from areas such as 5G multicarrier will be important. Future commercial providers will not be limited to a small set of large aerospace companies. Ultimately, entirely government-owned and -operated satellite communications will phase out and make way for commercial business models that satisfy NASAs satellite communications requirements. The competition being provided by new entrants in the space communications business may result in a future in which all NASA communications needs can be satisfied commercially.

Space Communications↗
NASA NTRSDate not supplied

Deep Learning-Based Negotiation Strategy Selection for Cooperative Conflict Resolution in Urban Air Mobility

This paper presents a collaborative conflict resolution technique using deep neural network-based intelligent search of the solution space. This approach offers a rapid convergence to a mutually acceptable solution for real-time conflict resolution, suitable for urban air mobility operations. Furthermore, the presented technique allows operational flexibility to the urban air mobility agents where these agents can collaboratively devise the solution via integrative negotiation, based on their local utility functions, as long as such a solution does not violate the global safety thresholds. The presented machine-to-machine negotiation method is built on our prior work on holistic assessment of the airspace and potential conflict detection implemented at-the-edge, onboard the unmanned aircraft systems. This paper extends the prior work to augment decision-making at-the-edge, thereby, promising a true distributed control architecture for urban air mobility. In this approach, each agent (a) builds a potential in-flight conflict map, (b) identifies the conflicting agents, (c) dynamically prepares a list of alternatives based on its current utility functions, (d) negotiates with the conflicting agents to pick one of these alternatives, and (e) implements the negotiated alternative to mutually resolve the conflict. Note that such an approach does not require a contingency plan to be made pre-flight, as the conflict resolution strategies are decided and negotiated in real time based on the present state of the agent. The contingency plan, if available, can serve as an input to the real-time conflict resolution strategy formulation, and also can be used as a fallback plan in case the negotiation fails and the impacted agents need to switch to a rule-based/supervisory resolution mode from the discussed distributed resolution mode. The presented collaborative negotiation-based conflict resolution technique incorporates a time-dependent reward function to catalyze collaborative resolution by incentivizing the agents with local and global rewards beneficial to their business operations.

Advanced Air Mobility↗
NASA NTRSDate not supplied

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 NTRSDate not supplied

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↗