Search NASA⌕ Search

SEARCH · Search NASA

Results for “space mission interoperability”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

Challenges of Space Mission Interoperability

This viewgraph presentation reviews some of the international challenges to space mission interoperability. Interoperability is the technical capability of two or more systems or components to exchange information and to use the information that has been exchanged. One of the challenges that is addressed is the problem of spectrum bandwidth, and interference. The key to interoperability is the standardization of space communications services and protocols. Various levels of international cross support are reviewed: harmony, cooperation cross support and confederation cross support. The various international bodies charged with implementing cross support are reviewed. The goal of the Interagency Operations Advisory Group (IOAG) is to achieve plug-and-play operations where all that is required is for each of the systems to use an agreed communications medium, after which the systems configure each other for the purpose of exchanging information and subsequently effect such exchange automatically.

interoperability↗
NASA NTRS1998

Interoperability for Space Mission Monitor and Control: Applying Technologies from Manufacturing Automation and Process Control Industries

Various issues associated with interoperability for space mission monitor and control are presented in viewgraph form. Specific topics include: 1) Space Project Mission Operations Control Architecture (SuperMOCA) goals and methods for achieving them; 2) Specifics on the architecture: open standards ad layering, enhancing interoperability, and promoting commercialization; 3) An advertisement; 4) Status of the task - government/industry cooperation and architecture and technology demonstrations; and 5) Key features of messaging services and virtual devices.

Jones, Michael K.↗
NASA NTRS2012

Mars Mission Scenario: Data Volume and PDT Notes

Objectives of this work are: (1) Investigate methods for quantifying the value of interoperability for deep space missions: A network of optical receive stations Each one potentially owned by a different space agency. Reduces overall cost to any individual agency Provides geographically diverse locations to mitigate weather problems (clouds, wind, rain, dust, etc.) (2) Metrics: a. Total data volume returned over mission duration b. Percent data transferred (PDT) or something similar.

deep space optical communications↗
NASA NTRS2009

CCSDS Spacecraft Monitor and Control Mission Operations Interoperability Prototype

We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the capabilities of existing legacy systems. Various custom applications and middleware solutions will be combined into one system providing the illusion of a set of homogenous services. This paper will document our journey as we implement the interoperability prototype. The team consists of software engineers with experience on the current command, telemetry and messaging systems that support the International Space Station (ISS) and Space Shuttle programs. Emphasis will be on the objectives, results and potential cost saving benefits.

Lucord, Steve↗
NASA NTRS2012

Effective Utilization of Resources and Infrastructure for a Spaceport Network Architecture

Providing routine, affordable access to a variety of orbital and deep space destinations requires an intricate network of ground, planetary surface, and space-based spaceports like those on Earth (land and sea), in various Earth orbits, and on other extraterrestrial surfaces. Advancements in technology and international collaboration are critical to establish a spaceport network that satisfies the requirements for private and government research, exploration, and commercial objectives. Technologies, interfaces, assembly techniques, and protocols must be adapted to enable mission critical capabilities and interoperability throughout the spaceport network. The conceptual space mission architecture must address the full range of required spaceport services, from managing propellants for a variety of spacecraft to governance structure. In order to accomplish affordability and sustainability goals, the network architecture must consider deriving propellants from in situ planetary resources to the maximum extent possible. Water on the Moon and Mars, Mars' atmospheric CO2, and O2 extracted from lunar regolith are examples of in situ resources that could be used to generate propellants for various spacecraft, orbital stages and trajectories, and the commodities to support habitation and human operations at these destinations. The ability to use in-space fuel depots containing in situ derived propellants would drastically reduce the mass required to launch long-duration or deep space missions from Earth's gravity well. Advances in transformative technologies and common capabilities, interfaces, umbilicals, commodities, protocols, and agreements will facilitate a cost-effective, safe, reliable infrastructure for a versatile network of Earth- and extraterrestrial spaceports. Defining a common infrastructure on Earth, planetary surfaces, and in space, as well as deriving propellants from in situ planetary resources to construct in-space propellant depots to serve the spaceport network, will reduce exploration costs due to standardization of infrastructure commonality and reduction in number and types of interfaces and commodities.

Gill, Tracy↗
NASA NTRS2008

OTF CCSDS SM and C Interoperability Prototype

A presentation is provided to demonstrate the interoperability between two space flight Mission Operation Centers (MOCs) and to emulate telemetry, actions, and alert flows between the two centers. One framework uses a COTS C31 system that uses CORBA to interface to the local OTF data network. The second framework relies on current Houston MCC frameworks and ad hoc clients. Messaging relies on SM and C MAL, Core and Common Service formats, while the transport layer uses AMS. A centralized SM and C Registry uses HTTP/XML for transport/encoding. The project's status and progress are reviewed.

Reynolds, Walter F.↗
NASA NTRS2017

Iris Deep-Space Transponder for SLS EM-1 CubeSat Missions

Several key design upgrades have been recently made to the Iris Deep-Space Transponder baselined to be used on secondary payload missions of the upcoming Space Launch System Exploration Mission One (SLS EM-1). The Iris Transponder is a reconfigurable software-defined radio (SDR) designed for missions requiring interoperability with NASA's Deep Space Network (DSN) on X-band frequencies (7.2 GHz uplink, 8.4 GHz downlink). The transponder provides radiometric tracking support with the DSN to provide navigational products for precise orbit determination while performing standard uplink and downlink communications in a CubeSat/SmallSat-applicable package size. The recent hardware changes include a volume reduction of 30% from previous models, with the main transponder unit weighing less than 1.0 kg, while maintaining total ionizing dose (TID) radiation tolerance of >23 krads (Si) for deep-space missions. Lab tests indicate maximum downlink rates of up to 6.25 Msps can be supported by the transponder in conventional BPSK modulation, but most SLS EM-1 CubeSat missions are link-performance limited to less than 256 kbps. A prototype unit of the flight production units has been assembled and various performance and characterization tests are underway. This talk discusses the key design aspects and specifications of the Iris Transponder and presents preliminary results from early testing of the assembled transponder.

Kobayashi, M. Michael↗
NASA NTRS2007

Strategic Adaptation of SCA for STRS

The Space Telecommunication Radio System (STRS) architecture is being developed to provide a standard framework for future NASA space radios with greater degrees of interoperability and flexibility to meet new mission requirements. The space environment imposes unique operational requirements with restrictive size, weight, and power constraints that are significantly smaller than terrestrial-based military communication systems. With the harsh radiation environment of space, the computing and processing resources are typically one or two generations behind current terrestrial technologies. Despite these differences, there are elements of the SCA that can be adapted to facilitate the design and implementation of the STRS architecture.

Quinn, Todd↗
NASA NTRSDate not supplied

Framework for NASA Space Relay Satellite Services over the Next Decade: Space Relay Partnership and Services Study

The United States National Space Policy provides guidance and directives for U.S. Government agencies to purchase commercial space services and capabilities to the maximum extent practical. In alignment with this guidance, the anticipated initial NASA near-Earth space relay operating capability over the next decade will be comprised of the existing NASA-owned Space Network infrastructure supplemented with commercially-owned and -provided relay satellites and their associated ground stations. NASA awarded contracts to eight study vendors in May 2019 to investigate the feasibility of applying commercial services concepts to the NASA user mission community. The studies, managed by NASA Glenn Research Center, detailed ten study topic areas. NASA completed the analysis and synthesis of these eight industry studies and other relevant information. The responses from the study vendors indicated a strong interest in providing commercial services to NASA missions, and included a wide range of proposed architectures and demonstration ideas. Overall, the responses indicated that a mature and healthy competitive environment exists across a broad spectrum of industry to deliver high-rate space relay services in the next three to five years. This paper will present an overview of the study, analysis and synthesis processes along with common themes and conclusions, and provide next steps and recommendations. The results of this study serve as a foundation for ongoing efforts to acquire interoperable space relay services for NASA missions from multiple commercial service providers.

Eric Knoblock↗
NASA NTRSDate not supplied

Framework for NASA Space Relay Satellite Services over the Next Decade: Space Relay Partnership and Services Study

The United States National Space Policy provides guidance and directives for U.S. Government agencies to purchase commercial space services and capabilities to the maximum extent practical. In alignment with this guidance, the anticipated initial NASA near-Earth space relay operating capability over the next decade will be comprised of the existing NASA-owned Space Network infrastructure supplemented with commercially-owned and -provided relay satellites and their associated ground stations. NASA awarded contracts to eight study vendors in May 2019 to investigate the feasibility of applying commercial services concepts to the NASA user mission community. The studies, managed by NASA Glenn Research Center, detailed ten study topic areas. NASA completed the analysis and synthesis of these eight industry studies and other relevant information. The responses from the study vendors indicated a strong interest in providing commercial services to NASA missions, and included a wide range of proposed architectures and demonstration ideas. Overall, the responses indicated that a mature and healthy competitive environment exists across a broad spectrum of industry to deliver high-rate space relay services in the next three to five years. This paper will present an overview of the study, analysis and synthesis processes along with common themes and conclusions, and provide next steps and recommendations. The results of this study serve as a foundation for ongoing efforts to acquire interoperable space relay services for NASA missions from multiple commercial service providers.

Eric Knoblock↗
NASA NTRS2009

Developing a Standard Method for Link-Layer Security of CCSDS Space Communications

Communications security for space systems has been a specialized field generally far removed from considerations of mission interoperability and cross-support in fact, these considerations often have been viewed as intrinsically opposed to security objectives. The space communications protocols defined by the Consultative Committee for Space Data Systems (CCSDS) have a twenty-five year history of successful use in over 400 missions. While the CCSDS Telemetry, Telecommand, and Advancing Orbiting Systems protocols for use at OSI Layer 2 are operationally mature, there has been no direct support within these protocols for communications security techniques. Link-layer communications security has been successfully implemented in the past using mission-unique methods, but never before with an objective of facilitating cross-support and interoperability. This paper discusses the design of a standard method for cryptographic authentication, encryption, and replay protection at the data link layer that can be integrated into existing CCSDS protocols without disruption to legacy communications services. Integrating cryptographic operations into existing data structures and processing sequences requires a careful assessment of the potential impediments within spacecraft, ground stations, and operations centers. The objective of this work is to provide a sound method for cryptographic encapsulation of frame data that also facilitates Layer 2 virtual channel switching, such that a mission may procure data transport services as needed without involving third parties in the cryptographic processing, or split independent data streams for separate cryptographic processing.

Biggerstaff, Craig↗
NASA NTRS2015

Software Defined Radio Architecture Contributions to Next Generation Space Communications

Space communications architecture concepts, comprising the elements of the system, the interactions among them, and the principles that govern their development, are essential factors in developing National Aeronautics and Space Administration (NASA) future exploration and science missions. Accordingly, vital architectural attributes encompass flexibility, the extensibility to insert future capabilities, and to enable evolution to provide interoperability with other current and future systems. Space communications architectures and technologies for this century must satisfy a growing set of requirements, including those for Earth sensing, collaborative observation missions, robotic scientific missions, human missions for exploration of the Moon and Mars where surface activities require supporting communications, and in-space observatories for observing the earth, as well as other star systems and the universe. An advanced, integrated, communications infrastructure will enable the reliable, multipoint, high-data-rate capabilities needed on demand to provide continuous, maximum coverage for areas of concentrated activity. Importantly, the cost/value proposition of the future architecture must be an integral part of its design; an affordable and sustainable architecture is indispensable within anticipated future budget environments. Effective architecture design informs decision makers with insight into the capabilities needed to efficiently satisfy the demanding space-communication requirements of future missions and formulate appropriate requirements. A driving requirement for the architecture is the extensibility to address new requirements and provide low-cost on-ramps for new capabilities insertion, ensuring graceful growth as new functionality and new technologies are infused into the network infrastructure. In addition to extensibility, another key architectural attribute of the space communication equipment's interoperability with other NASA communications systems, as well as those communications and navigation systems operated by international space agencies and civilian and government agencies. In this paper, we review the philosophies, technologies, architectural attributes, mission services, and communications capabilities that form the structure of candidate next-generation integrated communication architectures for space communications and navigation. A key area that this paper explores is from the development and operation of the software defined radio for the NASA Space Communications and Navigation (SCaN) Testbed currently on the International Space Station (ISS). Evaluating the lessons learned from development and operation feed back into the communications architecture. Leveraging the reconfigurability provides a change in the way that operations are done and must be considered. Quantifying the impact on the NASA Space Telecommunications Radio System (STRS) software defined radio architecture provides feedback to keep the standard useful and up to date. NASA is not the only customer of these radios. Software defined radios are developed for other applications, and taking advantage of these developments promotes an architecture that is cost effective and sustainable. Developments in the following areas such as an updated operating environment, higher data rates, networking and security can be leveraged. The ability to sustain an architecture that uses radios for multiple markets can lower costs and keep new technology infused.

Lessons Learned↗
NASA NTRS2013

CCSDS Overview

The primary goal of Consultative Committee for Space Data Systems (CCSDS) is interoperability between communications and data systems of space agencies' vehicles, facilities, missions and programs. Of all of the technologies used in spaceflight, standardization of communications and data systems brings the most benefit to multi-agency interoperability. CCSDS Started in 1982 developing standards at the lower layers of the protocol stack. The CCSDS scope has grown to cover standards throughout the entire ISO communications stack, plus other Data Systems areas (architecture, archive, security, XML exchange formats, etc.

Kearney, Mike↗
NASA NTRS2005

How to Extend the Capabilities of Space Systems for Long Duration Space Exploration Systems

For sustainable Exploration Missions the need exists to assemble systems-of-systems in space, on the Moon or on other planetary surfaces. To fulfill this need new and innovative system architectures must be developed to be modularized and launched with the present lift capability of existing rocket technology. To enable long duration missions with minimal redundancy and mass, system software and hardware must be reconfigurable. This will enable increased functionality and multiple use of launched assets while providing the capability to quickly overcome components failures. Additional required capability includes the ability to dynamically demate and reassemble individual system elements during a mission in order to recover from failed hardware or to adapt to changes in mission requirements. To meet the Space Exploration goals of Interoperability and Reconfigurability, many challenges must be addressed to transform the traditional static avionics architectures into architectures with dynamic capabilities. The objective of this paper is to introduce concepts associated with reconfigurable computer systems; to review the various needs and challenges associated with reconfigurable avionics space systems; to provide an operational example that illustrates the application to both the Crew Exploration Vehicle and a collection of 'Habot-like' mobile surface elements; to summarize the approaches that address key challenges to the acceptance of a Flexible, Intelligent, Modular, Affordable and Reconfigurable avionics space system.

space assembly↗
NASA NTRS2004

Internet-Protocol-Based Satellite Bus Architecture Designed

NASA is designing future complex satellite missions ranging from single satellites and constellations to space networks and sensor webs. These missions require more interoperability, autonomy, and coordination than previous missions; in addition, a desire exists to have scientists retrieve data directly from the satellite rather than a central distribution source. To meet these goals, NASA has been studying the possibility of extending the Transmission Control Protocol/Internet Protocol (TCP/IP) suite for spacebased applications.

Slywczak, Richard A.↗
NASA NTRS2023

Flight Mechanics Analysis Tools Interoperability and Component Sharing

Several NASA centers have developed independent flight mechanics tools to meet the science needs of missions. This NASA Engineering and Safety Center (NESC) assessment sought to explore the ways to increase the interoperability of three specific tools: Copernicus from Johnson Space Center (JSC), the General Mission Analysis Tool (GMAT) from Goddard Spaceflight Flight Center (GSFC), and the Mission-Analysis Operations Navigation Toolkit Environment (MONTE) from the Jet Propulsion Laboratory (JPL). Before this assessment, these tools were not integrated and could not easily share data, models, or components. This report contains the outcome of the NESC assessment.

General Mission Analysis Tool↗
NASA NTRSDate not supplied

Using Open Standards and NASA Open Source Simulation Tools to Model Artemis Base Camp Mission Timelines

The United States’ National Aeronautics and Space Administration (NASA) has announced that the Artemis Program will return humans to the Moon, establishing a persistent presence with the Artemis Base Camp (ABC), and extend human exploration to Mars. The NASA Exploration Systems Simulations (NExSyS) team at NASA’s Johnson Space Center is using internationally developed simulation interoperability standards and NASA open source simulation tools to support Artemis concept, analysis, designs, development, training, and ultimately operations. The NExSyS team has been tasked to support early ABC architecture and mission analysis using mission time lines developed by the crew operations mission planning team. The NExSyS team is developing a distributed simulation framework with initial Artemis element implementations to model the ABC mission timelines using the international simulation interoperability standard High Level Architecture (HLA), the Simulation Interoperability Standards Organization’s Space Reference Federation Object Model (SpaceFOM), the NASA open source Trick Simulation Environment, and another NASA open source interface package called TrickHLA. The ABC architecture is composed of a number of key surface elements and resources. Some examples of modeled elements (also known as entities) are landers, habitats, rovers, logistics carriers, and astronauts. Some examples of modeled transferable and consumable resources are power, water, oxygen, nitrogen, scientific samples, and food. These entities and resources are modeled in a collection of individual simulations called Federates. A coordinated collection of interoperable federates is called a Federation and when these federates are tied together in a coordinated simulation run, it is referred to as a Federation Execution. The federates communicate through HLA using data exchange formats defined by a collection of machine readable files called Federation Object Models (FOMs). These FOM files are based on extensions to the SpaceFOM. This enables the instantiation and sharing of objects and interactions between federates in the federation. These provide for entity and resource tracking, object transfer, and data collection. Federate interactions are used to trigger events and notify federates of entity or resource transfers. For the initial implementation, the constituent federates are Trick-based simulations that use TrickHLA to provide the required HLA-base interoperability. These Trick-based simulations provide the required modeling for the individual Artemis elements along with the associated element resources. These federates provide a means to explore traverses between surface elements and exploration sites as scheduled in a mission timeline and explore the affects traverse times have on the overall mission timeline. The mission time lines are modeled using a Trick input file event handling capabilities. Each timeline operation is handled as individual simulation events, and triggered based on previous event status, time of operation, and simulated task completions. In addition, the ABC Federation can be used to perform Monte Carlo analysis. The Monte Carlo tool can vary the inputs, timings, and malfunctions to show how various contingencies in the mission can affect the mission timeline.

Keaton Craig Dodd↗