SEARCH · Search NASA

Results for “File Transfer Service”

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.

SourceResearch connectionFrom yearThrough year

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

At least 37 records · Page 2

All sources NASA NTRS DOE OSTI

NASA NTRS2001

Registered File Support for Critical Operations Files at (Space Infrared Telescope Facility) SIRTF

The SIRTF Science Center's (SSC) Science Operations System (SOS) has to contend with nearly one hundred critical operations files via comprehensive file management services. The management is accomplished via the registered file system (otherwise known as TFS) which manages these files in a registered file repository composed of a virtual file system accessible via a TFS server and a file registration database. The TFS server provides controlled, reliable, and secure file transfer and storage by registering all file transactions and meta-data in the file registration database. An API is provided for application programs to communicate with TFS servers and the repository. A command line client implementing this API has been developed as a client tool. This paper describes the architecture, current implementation, but more importantly, the evolution of these services based on evolving community use cases and emerging information system technology.

file management services↗

NASA NTRS1993

Evolution of a high-performance storage system based on magnetic tape instrumentation recorders

In order to provide transparent access to data in network computing environments, high performance storage systems are getting smarter as well as faster. Magnetic tape instrumentation recorders contain an increasing amount of intelligence in the form of software and firmware that manages the processes of capturing input signals and data, putting them on media and then reproducing or playing them back. Such intelligence makes them better recorders, ideally suited for applications requiring the high-speed capture and playback of large streams of signals or data. In order to make recorders better storage systems, intelligence is also being added to provide appropriate computer and network interfaces along with services that enable them to interoperate with host computers or network client and server entities. Thus, recorders are evolving into high-performance storage systems that become an integral part of a shared information system. Data tape has embarked on a program with the Caltech sponsored Concurrent Supercomputer Consortium to develop a smart mass storage system. Working within the framework of the emerging IEEE Mass Storage System Reference Model, a high-performance storage system that works with the STX File Server to provide storage services for the Intel Touchstone Delta Supercomputer is being built. Our objective is to provide the required high storage capacity and transfer rate to support grand challenge applications, such as global climate modeling.

Peters, Bruce↗

NASA NTRS2010

MaROS Strategic Relay Planning and Coordination Interfaces

The Mars Relay Operations Service (MaROS) is designed to provide planning and analysis tools in support of ongoing Mars Network relay operations. Strategic relay planning requires coordination between lander and orbiter mission ground data system (GDS) teams to schedule and execute relay communications passes. MaROS centralizes this process, correlating all data relevant to relay coordination to provide a cohesive picture of the relay state. Service users interact with the system through thin-layer command line and web user interface client applications. Users provide and utilize data such as lander view periods of orbiters, Deep Space Network (DSN) antenna tracks, and reports of relay pass performance. Users upload and download relevant relay data via formally defined and documented file structures including some described in Extensible Markup Language (XML). Clients interface with the system via an http-based Representational State Transfer (ReST) pattern using Javascript Object Notation (JSON) formats. This paper will provide a general overview of the service architecture and detail the software interfaces and considerations for interface design.

Allard, Daniel A.↗

NASA NTRS2021

HAPI: An API Standard for Accessing Heliophysics Time Series Data

Heliophysics data analysis often involves combining diverse science measurements, many of them captured as time series. Although there are now only a few commonly used data file formats, the diversity in mechanisms for automated access to and aggregation of such data holdings can make analysis that requires intercomparison of data from multiple data providers difficult. The Heliophysics Application Programmer's Interface (HAPI) is a recently developed standard for accessing distributed time series data to increase interoperability. The HAPI specification is based on the common elements of existing data services, and it standardizes the two main parts of a data service: the request interface and the response data structures. The interface is based on the REpresentational State Transfer (REST) or RESTful architecture style, and the HAPI specification defines five required REST endpoints. Data are returned via a streaming format that hides file boundaries; the metadata is detailed enough for the content to be scientifically useful, e.g., plotted with appropriate axes layout, units, and labels. Multiple mature HAPI-related open-source projects offer server-side implementation tools and client-side libraries for reading HAPI data in multiple languages (IDL, Java, MATLAB, and Python). Multiple data providers in the US and Europe have added HAPI access alongside their existing interfaces. Based on this experience, data can be served via HAPI with little or no information loss compared to similar existing web interfaces. Finally, HAPI has been recommended as a COSPAR standard for time series data delivery.

Robert S. Weigel↗

NASA NTRS2006

Transferring Files Between the Deep Impact Spacecrafts and the Ground Data System Using the CCSDS File Delivery Protocol (CFDP): A Case Study

The CCSDS File Delivery Protocol (CFDP) Standard could reshape ground support architectures by enabling applications to communicate over the space link using reliable-symmetric transport services. JPL utilized the CFDP standard to support the Deep Impact Mission. The architecture was based on layering the CFDP applications on top of the CCSDS Space Link Extension Services for data transport from the mission control centers to the ground stations. On July 4, 2005 at 1:52 A.M. EDT, the Deep Impact impactor successfully collided with comet Tempel 1. During the final 48 hours prior to impact, over 300 files were uplinked to the spacecraft, while over 6 thousand files were downlinked from the spacecraft using the CFDP. This paper uses the Deep Impact Mission as a case study in a discussion of the CFDP architecture, Deep Impact Mission requirements, and design for integrating the CFDP into the JPL deep space support services. Issues and recommendations for future missions using CFDP are also provided.

CCSDS File Delivery Protocol (CFDP)↗

NASA NTRS1986

PCDS as a tool in teaching and research at the University of Michigan

The Space Physics Research Laboratory's (SPRL) use of the Pilot Climate Data System (PCDS) is discussed. For this purpose, a computer center was established to provide the hardware and software necessary to fully utilize existing data bases for research and teaching purposes. A schematic of the SPRL network is given. The core of the system consists of two VAX 11/750s and a VAX 8600, networked through ETHERNET to several LSI 11/23 microprocessors. Much of the system is used for external communications with major networks and data centers. A VAX 11/750 provides DECNET services through the SPAN network to the PCDS. A functional diagram of PCDS usage is given. The browsing capabilities of the PCDS are used to generate data files, which are later transferred to the SPRL center for further data manipulation and display. This mode of operation for classroom instruction will be used to effectively use terminals and to simplify usage of the data base. The Atmosphere Explorer data base has been used successfully in a similar manner in courses related to the thermosphere and ionosphere. The main motivation to access the PCDS was to complement research efforts related to the High Resolution Doppler Imager (HRDI), to be flown on the Upper Atmosphere Research Satellite (UARS).

Abreu, V.↗

NASA NTRS1989

The Aerospace Energy Systems Laboratory: A BITBUS networking application

The NASA Ames-Dryden Flight Research Facility developed a computerized aircraft battery servicing facility called the Aerospace Energy Systems Laboratory (AESL). This system employs distributed processing with communications provided by a 2.4-megabit BITBUS local area network. Customized handlers provide real time status, remote command, and file transfer protocols between a central system running the iRMX-II operating system and ten slave stations running the iRMX-I operating system. The hardware configuration and software components required to implement this BITBUS application are required.

Glover, Richard D.↗

NASA NTRS2006

X-Windows PVT Widget Class

The X-Windows Process Validation Table (PVT) Widget Class ( Class is used here in the object-oriented-programming sense of the word) was devised to simplify the task of implementing network registration services for Information Sharing Protocol (ISP) graphical-user-interface (GUI) computer programs. Heretofore, ISP PVT programming tasks have required many method calls to identify, query, and interpret the connections and messages exchanged between a client and a PVT server. Normally, programmers have utilized direct access to UNIX socket libraries to implement the PVT protocol queries, necessitating the use of many lines of source code to perform frequent tasks. Now, the X-Windows PVT Widget Class encapsulates ISP client server network registration management tasks within the framework of an X Windows widget. Use of the widget framework enables an X Windows GUI program to interact with PVT services in an abstract way and in the same manner as that of other graphical widgets, making it easier to program PVT clients. Wrapping the PVT services inside the widget framework enables a programmer to treat a PVT server interface as though it were a GUI. Moreover, an alternate subclass could implement another service in a widget of the same type. This program was written by Matthew R. Barry of United Space Alliance for Johnson Space Center. For further information, contact the Johnson Technology Transfer Office at (281) 483-3809. MSC-23582 Shuttle Data Center File- Processing Tool in Java A Java-language computer program has been written to facilitate mining of data in files in the Shuttle Data Center (SDC) archives. This program can be executed on a variety of workstations or via Web-browser programs. This program is partly similar to prior C-language programs used for the same purpose, while differing from those programs in that it exploits the platform-neutrality of Java in implementing several features that are important for analysis of large sets of time-series data. The program supports regular expression queries of SDC archive files, reads the files, interleaves the time-stamped samples according to a chosen output, then transforms the results into that format. A user can choose among a variety of output file formats that are useful for diverse purposes, including plotting, Markov modeling, multivariate density estimation, and wavelet multiresolution analysis, as well as for playback of data in support of simulation and testing.

Barry, Matthew R.↗

NASA NTRS1978

A regional technology transfer program

The final report is presented for the North Carolina Science and Technology Research Center's 14th consecutive contract period as a NASA Industrial Applications Center, serving the information needs of nine Southeastern states. Included in the report are figures for and analysis of marketing efforts, file usage, search delivered, and other services performed for clients; and information on staff changes, workshops, and special projects in 1978. An appendix contains copies of NC/STRC magazine advertisements, letters from clients, and supplementary information on NC/STRC staff and services.

Source record↗

NASA NTRS2019

Medical Data Architecture (MDA) Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.In fiscal year 2018, the MDA project developed Test Bed 2, the second iteration in a series of prototypes with functionality focused on data security through role-based access control and encryption, integration with One Portal exercise software and ingestion of an ultrasound Digital Imaging and Communications in Medicine (DICOM) file and image display. Test Bed 2 advances the medical data system architecture framework by providing these functionalities in a scalable system that maintained a layered, modular design. The architecture framework uses a data services approach with role-based access to data in a customized medical record system suitable for space exploration. These functionalities were demonstrated as part of the Next Space Technologies for Exploration Partnerships (NextSTEP) ground test demonstrated at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Interfacing to a Core Flight Software (CFS) system, the MDA system, using Consultative Committee for Space Data Systems (CCSDS) protocol, transferred an exercise file from the simulated flight MDA system to a mirrored MDA system on the ground through the CFS system. The selection of data sources and demonstrations enabled the team to address stakeholder concerns throughout the development process. In the next iteration, the MDA team will work with stakeholders to identify additional relevant functionalities to further advance system data models, standards and principles that will inform the medical system requirements development.

medical data architecture↗

NASA NTRS1999

Early Communication System (ECOMM) for ISS

The International Space Station (ISS) Early Communications System (ECOMM) was a Johnson Space Center (JSC) Avionic Systems Division (ASD) in-house developed communication system to provide early communications between the ISS and the Mission Control Center-Houston (MCC-H). This system allows for low rate commands (link rate of 6 kbps) to be transmitted through the Tracking and Data Relay Satellite System (TDRSS) from MCC-H to the ISS using TDRSS's S-band Single Access Forward (SSA/) link service. This system also allows for low rate telemetry (link rate of 20.48 kbps) to be transmitted from ISS to MCC-H through the TDRSS using TDRSS's S-band Single Access Return (SSAR) link service. In addition this system supports a JSC developed Onboard Communications Adapter (OCA) that allows for a two-way data exchange of 128 kbps between MCC-H and the ISS through TDRSS. This OCA data can be digital video/audio (two-way videoconference), and/or file transfers, and/or "white board". The key components of the system, the data formats used by the system to insure compatibility with the future ISS S-Band System, as well as how other vehicles may be able to use this system for their needs are discussed in this paper.

Gaylor, Kent↗

NASA NTRS2000

Enhancement of the NMSU Channel Error Simulator to Provide User-Selectable Link Delays

This is the third in a continuing series of reports describing the development of the Space-to-Ground Link Simulator (SGLS) to be used for testing data transfers under simulated space channel conditions. The SGLS is based upon Virtual Instrument (VI) software techniques for managing the error generation, link data rate configuration, and, now, selection of the link delay value. In this report we detail the changes that needed to be made to the SGLS VI configuration to permit link delays to be added to the basic error generation and link data rate control capabilities. This was accomplished by modifying the rate-splitting VIs to include a buffer the hold the incoming data for the duration selected by the user to emulate the channel link delay. In sample tests of this configuration, the TCP/IP(sub ftp) service and the SCPS(sub fp) service were used to transmit 10-KB data files using both symmetric (both forward and return links set to 115200 bps) and unsymmetric (forward link set at 2400 bps and a return link set at 115200 bps) link configurations. Transmission times were recorded at bit error rates of 0 through 10(exp -5) to give an indication of the link performance. In these tests. we noted separate timings for the protocol setup time to initiate the file transfer and the variation in the actual file transfer time caused by channel errors. Both protocols showed similar performance to that seen earlier for the symmetric and unsymmetric channels. This time, the delays in establishing the file protocol also showed that these delays could double the transmission time and need to be accounted for in mission planning. Both protocols also showed a difficulty in transmitting large data files over large link delays. In these tests, there was no clear favorite between the TCP/IP(sub ftp) and the SCPS(sub fp). Based upon these tests, further testing is recommended to extend the results to different file transfer configurations.

Horan, Stephen↗

NASA NTRS1991

Technology transfer at NASA - A librarian's view

The NASA programs, publications, and services promoting the transfer and utilization of aerospace technology developed by and for NASA are briefly surveyed. Topics addressed include the corporate sources of NASA technical information and its interest for corporate users of information services; the IAA and STAR abstract journals; NASA/RECON, NTIS, and the AIAA Aerospace Database; the RECON Space Commercialization file; the Computer Software Management and Information Center file; company information in the RECON database; and services to small businesses. Also discussed are the NASA publications Tech Briefs and Spinoff, the Industrial Applications Centers, NASA continuing bibliographies on management and patent abstracts (indexed using the NASA Thesaurus), the Index to NASA News Releases and Speeches, and the Aerospace Research Information Network (ARIN).

Buchan, Ronald L.↗

NASA NTRS2003

Enhanced Multi-Modal Access to Planetary Exploration

Tomorrow's Interplanetary Network (IPN) will evolve from JPL's Deep-Space Network (DSN) and provide key capabilities to future investigators, such as simplified acquisition of higher-quality science at remote sites and enriched access to these sites. These capabilities could also be used to foster public interest, e.g., by making it possible for students to explore these environments personally, eventually perhaps interacting with a virtual world whose models could be populated by data obtained continuously from the IPN. Our paper looks at JPL's approach to making this evolution happen, starting from improved communications. Evolving space protocols (e.g., today's CCSDS proximity and file-transfer protocols) will provide the underpinning of such communications in the next decades, just as today's rich web was enabled by progress in Internet Protocols starting from the early 1970's (ARPAnet research). A key architectural thrust of this effort is to deploy persistent infrastructure incrementally, using a layered service model, where later higher-layer capabilities (such as adaptive science planning) are enabled by earlier lower-layer services (such as automated routing of object-based messages). In practice, there is also a mind shift needed from an engineering culture raised on point-to-point single-function communications (command uplink, telemetry downlink), to one in which assets are only indirectly accessed, via well-defined interfaces. We are aiming to foster a 'community of access' both among space assets and the humans who control them. This enables appropriate (perhaps eventually optimized) sharing of services and resources to the greater benefit of all participants. We envision such usage to be as automated in the future as using a cell phone is today - with all the steps in creating the real-time link being automated.

interplanetary network (IPN)↗

NASA NTRS2019

Operations of the Optical Communications Demonstration for the Orion EM-2 Mission

The GSFC implementation of an Optical Communication System to demonstrate an operational optical communication link for Orion EM-2. It will serve as a base for providing an operational optical communications capability for future Orion missions. GSFC plans to maintain a development path for the optical communication flight terminal to allow commercialization and implementation on future Orion missions. The Orion optical module part of the optical communications flight terminal and its control electronics have a common architecture with the ILLUMA-T optical terminal provided by GSFC for use on the ISS. The plan is to flow data from Orion through the Optical Communication Fight Terminal to the Optical Communication Ground Terminal and reverse. NASA's Orion spacecraft is an exploratory vehicle designed for longer-duration flights beyond the Moon. Following Orion's Exploration Mission-1 (EM-1), during which the spacecraft will travel beyond the Moon, enter a distant retrograde orbit around the Moon and return to Earth unmanned, Exploration Mission-2 (EM-2) will see a crewed spacecraft complete a slightly different flight path. First crewed test flight of the Orion spacecraft, currently targeting a June 30, 2022 launch. The mission involves: One revolution in Low Earth Orbit (LEO) parking orbit to verify basic Orion systems functionality and deploy solar arrays. A single 42-hour Highly Elliptical Orbit (HEO) intermediate checkout orbit allows characterization of the Orion vehicle system performance prior to committing to a cis-lunar flight. Trans Lunar Injection (TLI) burn using Orion Service Module (SM) main engine, which sends Orion on a lunar flyby and free return. Skip reentry at lunar return velocities to splashdown off the coast of San Diego. Total mission duration is approximately 10 days. EM-2 is the first crewed mission of the Orion Spacecraft that crew brings more video up/downloads, file transfers, and real-time chats with family back home and high-rate communications enables live HD streaming for Crew conferences, Public Affairs Office (PAO) events, and significant mission events. Also still collecting vehicle data on numerous Orion subsystems via Development Flight Instrumentation (DFI) allows large data volume returns sooner for DFI and future science payloads, as opposed to waiting for end-of-mission. O2O is a demonstration of operational utility system tested as a Developmental Test Objective (DTO) and not required to meet mission requirements/success/ Flight Test Objectives (FTO). EM-2 architecture is as close to future mission operational architecture as possible.Orion subsystems (video, DFI, etc.) expected to generate ~250 GB of data in the first 24 hours of flight. Total data generated over the mission estimated to be more than 400 GBUsing S-Band alone, Orion limited to ~ 6GB of data downlink per day. Because of this limitation, Orion is planning to limit live video downlinks on EM-1 in order to downlink high priority fileswith 1 hour/day of Optical Communication, Orion could downlink ~6x more data per day (~ 36GB/day).The optical communication system is capable of multiple data rates up to at least 80 Mbps downlink for the transfer of Orion data to Earth while Orion is operating in the lunar vicinity.

Optical Communication↗

NASA NTRS2014

CNES-NASA Disruption-Tolerant Networking (DTN) Interoperability

Future missions requiring robust internetworking services may use Delay-Disruption-Tolerant Networking (DTN) technology. CNES, NASA, and other international space agencies are committed to using CCSDS standards in their space and ground mission communications systems. The experiment described in this presentation will evaluate operations concepts, system performance, and advance technology readiness for the use of DTN protocols in conjunction with CCSDS ground systems, CCSDS data links, and CCSDS file transfer applications

experiment design↗

NASA NTRS1971

Regional technology transfer program

The continuing operation is reported of a jointly state- and NASA-sponsored Regional Dissemination Center serving the southeastern United States. The NC/STRC offers automated searching of large information collections, such as that assembled by NASA, with emphasis on textile-related files to serve regional industry. During this period, NC/STRC conducted an in-depth analysis of its marketing programs and prepared a series of brochures aimed at various segments of industry. Heavy emphasis was also placed on the Library Search Service inaugurated by NC/STRC, and a total of 32 universities now participate in this service. Smaller schools are served through the university network. Although the nationwide industrial recession caused a general drop in search requests, NC/STRC processed a total of 838 retrospective searches during this period: 39.97% for its industrial clients, 22.9% for university libraries, and 37.1% for other RDC's.

Source record↗

NASA NTRS1993

Progress on GPS standardization

It has been clear for some time that a desirable and necessary step for improvement of the accuracy of GPS time comparisons is to establish GPS standards which may be adopted by receiver designers and users. For this reason, a formal body, the CCDS Group on GPS Time Transfer Standards (CGGTTS), was created in 1991. It operates under the auspices of the permanent CCDS Working Group on TAI, with the objective of recommending procedures and models for operational time transfer by the GPS common-view method. It works in close cooperation with the Subcommittee on Time of the Civil GPS Service Interface Committee. The members of the CGGTTS have met in December 1991 and in June 1992. Following these two formal meetings, a number of decisions were taken for unifying the treatment of GPS short-term data and for standardizing the format of GPS data files. A formal CGGTTS Recommendation is now being written concerning these points. This paper relates on the work carried out by the CGGTTS.

Thomas, C.↗