SEARCH · Engineering Papers

Results for “IP networks”

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 109 records · Page 6

All sources NASA NTRS DOE OSTI

NASA NTRS2011

Backplane Design Considerations for High Speed SpaceWire Networks

SpaceWire is becoming a preferred protocol for board to board communication over a backplane in addition to its existing use over cabled interfaces, replacing other protocols due to its simplicity and readily available flight quality physical layer devices, IP cores and test equipment. However, without specific guidelines for implementing SpaceWire over a backplane, designers are left to make trade decisions regarding connector selection, layout design rules and test accessibility issues. This paper will discuss NASA's Goddard Space Flight Center s implementation of high speed SpaceWire over backplane on James Webb Space Telescope and other missions.

Pagen, Shahana Aziz↗

NASA NTRS2004

Overview of NASA Glenn Aero/Mobile Communication Demonstrations

The Glenn Research Center at Lewis Field (GRC) has been involved with several other NASA field centers on various networking and RF communications demonstrations and experiments since 1998. These collaborative experiments investigated communications technologies new to aviation, such as wideband Ku satcom, L-band narrowband satcom, and IP (Internet Protocol), using commercial off-the-shelf (COTS) components These technologies can be used to distribute weather and hazard data, air traffic management and airline fleet management information, and passenger cabin Internet service.

Brooks, David↗

NASA NTRS2004

Overview of NASA Glenn Aero/Mobile Communications Demonstrations

Brooks, David↗

NASA NTRS2001

Networks for Autonomous Formation Flying Satellite Systems

The performance of three communications networks to support autonomous multi-spacecraft formation flying systems is presented. All systems are comprised of a ten-satellite formation arranged in a star topology, with one of the satellites designated as the central or "mother ship." All data is routed through the mother ship to the terrestrial network. The first system uses a TCP/lP over ATM protocol architecture within the formation the second system uses the IEEE 802.11 protocol architecture within the formation and the last system uses both of the previous architectures with a constellation of geosynchronous satellites serving as an intermediate point-of-contact between the formation and the terrestrial network. The simulations consist of file transfers using either the File Transfer Protocol (FTP) or the Simple Automatic File Exchange (SAFE) Protocol. The results compare the IF queuing delay, and IP processing delay at the mother ship as well as application-level round-trip time for both systems, In all cases, using IEEE 802.11 within the formation yields less delay. Also, the throughput exhibited by SAFE is better than FTP.

Knoblock, Eric J.↗

NASA NTRS2012

BPTAP: A New Approach to IP over DTN

Traditional Internet protocols have been widely deployed for a variety of applications. However such protocols generally perform poorly in situations in which, round trip delays are very large (interplanetary distances) or . persistent connectivity is not always available (widely dispersed MANET). Delay/Disruption Tolerant Network (DTN) technology was invented to address these issues: (1) . Relay nodes "take custody" of blocks of network traffic on a hop-by -hop basis and retransmit them in cases of expected or unexpected link outage (2) Bundle lifetime may be configured for long round trip light times. BPTAP is novel by encapsulating Ethernet frames in BP

space links↗

NASA NTRS2000

Global Interoperability of High Definition Video Streams Via ACTS and Intelsat

In 1993, a proposal at the Japan.-U.S. Cooperation in Space Program Workshop lead to a subsequent series of satellite communications experiments and demonstrations, under the title of Trans-Pacific High Data Rate Satellite Communications Experiments. The first of which is a joint collaboration between government and industry teams in the United States and Japan that successfully demonstrated distributed high definition video (HDV) post-production on a global scale using a combination of high data rate satellites and terrestrial fiber optic asynchronous transfer mode (ATM) networks. The HDV experiment is the first GIBN experiment to establish a dual-hop broadband satellite link for the transmission of digital HDV over ATM. This paper describes the team's effort in using the NASA Advanced Communications Technology Satellite (ACTS) at rates up to OC-3 (155 Mbps) between Los Angeles and Honolulu, and using Intelsat at rates up to DS-3 (45 Mbps) between Kapolei and Tokyo, with which HDV source material was transmitted between Sony Pictures High Definition Center (SPHDC) in Los Angeles and Sony Visual Communication Center (VCC) in Shinagawa, Tokyo. The global-scale connection also used terrestrial networks in Japan, the States of Hawaii and California. The 1.2 Gbps digital HDV stream was compressed down to 22.5 Mbps using a proprietary Mitsubishi MPEG-2 codec that was ATM AAL-5 compatible. The codec: employed four-way parallel processing. Improved versions of the codec are now commercially available. The successful post-production activity performed in Tokyo with a HDV clip transmitted from Los Angeles was predicated on the seamless interoperation of all the equipment between the sites, and was an exciting example in deploying a global-scale information infrastructure involving a combination of broadband satellites and terrestrial fiber optic networks. Correlation of atmospheric effects with cell loss, codec drop-out, and picture quality were made. Current efforts in the Trans-Pacific series plan to examine the use of Internet Protocol (IP)-related technologies over such an infrastructure. The use of IP allows the general public to be an integral part of the exciting activities, helps to examine issues in constructing the solar-system internet, and affords an opportunity to tap the research results from the (reliable) multicast and distributed systems communities. The current Trans- Pacific projects, including remote astronomy and digital library (visible human) are briefly described.

Hsu, Eddie↗

NASA NTRS1997

High-Performance, Reliable Multicasting: Foundations for Future Internet Groupware Applications

Network protocols that provide efficient, reliable, and totally-ordered message delivery to large numbers of users will be needed to support many future Internet applications. The Reliable Multicast Protocol (RMP) is implemented on top of IP multicast to facilitate reliable transfer of data for replicated databases and groupware applications that will emerge on the Internet over the next decade. This paper explores some of the basic questions and applications of reliable multicasting in the context of the development and analysis of RMP.

Callahan, John↗

NASA NTRS2000

Internet over the VDL-2 Subnetwork: the VDL-2/IP Aviation Datalink System

This report describes the design to operate the standard Internet communications protocols (IP) over the VHF aviation Data Link Mode 2 (VDL-2) subnetwork. The VDL-2/IP system specified in this report can operate transparently with the current aviation users of VDL-2 (Airline Communications and Reporting System, ACARS and Aeronautical Telecommunications Network, ATN) and proposed users (Flight Information Service via Broadcast, FIS-B). The VDL-2/IP system provides a straightforward mechanisms to utilize inexpensive, commercial off-the-shelf (COTS) communications packages developed for the Internet as part of the aviation datalink system.

Grappel, R. D.↗

NASA NTRS2011

Interface Supports Multiple Broadcast Transceivers for Flight Applications

A wireless avionics interface provides a mechanism for managing multiple broadcast transceivers. This interface isolates the control logic required to support multiple transceivers so that the flight application does not have to manage wireless transceivers. All of the logic to select transceivers, detect transmitter and receiver faults, and take autonomous recovery action is contained in the interface, which is not restricted to using wireless transceivers. Wired, wireless, and mixed transceiver technologies are supported. This design s use of broadcast data technology provides inherent cross strapping of data links. This greatly simplifies the design of redundant flight subsystems. The interface fully exploits the broadcast data link to determine the health of other transceivers used to detect and isolate faults for fault recovery. The interface uses simplified control logic, which can be implemented as an intellectual-property (IP) core in a field-programmable gate array (FPGA). The interface arbitrates the reception of inbound data traffic appearing on multiple receivers. It arbitrates the transmission of outbound traffic. This system also monitors broadcast data traffic to determine the health of transmitters in the network, and then uses this health information to make autonomous decisions for routing traffic through transceivers. Multiple selection strategies are supported, like having an active transceiver with the secondary transceiver powered off except to send periodic health status reports. Transceivers can operate in round-robin for load-sharing and graceful degradation.

Block, Gary L.↗

NASA NTRSDate not supplied

The Surface Longwave Downward Fluxes of the NASA GEWEX SRB Release 4.0 IP Products: Validation Against the Surface-Based BSRN and PMEL Observed Data

Since the NASA Global Energy Water Exchanges (GEWEX) Surface Radiation Budget (SRB) project released its 3rd version of products in 2010, the GEWEX Data Assessments Panel (GDAP) has been working on integrating various data products to address issues in the closing of the global energy and water cycles. The 4th version of the SRB products, Rel. 4.0-IP, has integrated data products from the cloud, aerosol, atmosphere, ocean surface, and land surface projects, coordinating within GDAP, to produce a long-term time series of TOA and surface radiative estimates. The Rel. 4-IP shortwave products span 34 years continuously from July 1983 to June 2017 on a quasi-equal-area 1degree longitude by 1degree latitude grid system. The longwave products are for land only from 1983-07 to 1987-12; for both land and ocean from 1988-01 to 2009-12; and ocean only from 2010-01 to 2017-06. The data are provided at 3 hourly, 3-hourly-monthly, daily and monthly means. The ISCCP HXS clouds and radiances are the key cloud input of the current GEWEX SRB algorithms. In addition, the longwave algorithm has also made changes in cloud microphysical property, surface skin temperature input, surface emissivity, atmospheric profile, adding longwave aerosol optical properties, revising cloud overlap procedure, and so on. Details of changes in both inputs and algorithms are documented in a NASA Algorithm Theoretical Basis Document (ATBD). We have validated the surface longwave downward fluxes against the surface-based Baseline Surface Radiation Network (BSRN) and the Pacific Marine Environmental Laboratory (PMEL) buoy data. As of 2020, the BSRN archive has 12,116 site-months of observed records from 73 stations on all seven continents, and as of 2017, PMEL archive has 4389 buoy months of observed records from 64 buoys deployed in the tropics of Pacific, Atlantic and Indian Oceans. This paper presents how the SRB Rel. 4.0-IP surface longwave downward fluxes compare with these surface-based measurements and how the comparison statistics differ from that of Rel. 3.0.

GEWEX SRB↗

NASA NTRSDate not supplied

Toward an Integrated Product of Higher Accuracy and Longer Time Span: Improvement of the Upcoming NASA GEWEX SRB Data Release 4 over Release 3 Based on Validation Against Surface-Based Measurements

The NASA Global Energy and Water Exchanges (GEWEX) Surface Radiation Budget (SRB) is moving toward its next generation, the Release 4 Integrated Product (Rel. 4-IP), and its shortwave algorithm preliminary results as of this writing span 34 years continuously from July 1983 to June 2017 on a quasi-equal-area grid system with 44,016 gridboxes ranging from 1 longitude times 1 latitude around the Equator to 120 longitude times 1 latitude. The data are in the form of 3-hourly, 3-hourly-monthly, daily and monthly means. The Baseline Surface Radiation Network (BSRN) is a project of the Data and Assessments Panel from the GEWEX under the umbrella of the World Climate Research Programme (WCRP). Currently in the archive there are data from 67 sites located in all seven continents spanning from 1992 to the very present. The original BSRN records are at 1-, 2-, 3- or 5-minute intervals, and sophisticated quality-control procedures have been developed to eliminate erroneous records before hourly, daily and monthly means are computed. The Pacific Marine Environmental Laboratory (PMEL) arrays of buoys in the tropical oceans, TAO/TRITON (Pacific Ocean), RAMA (Indian Ocean) and PITARA (Atlantic Ocean), measure shortwave downward fluxes using pyranometers. These buoys transmit measured data to shore in real-time via the Argos satellite system. And these buoys are major components of the CLIVAR climate analysis project and the GOOS, GCOS, and GEOSS observing systems. So far there are data from 64 buoys and the earliest data start from 2000. We have extensively validated the Rel. 4-IP preliminary results against the BSRN and PMEL 3-hourly, daily and monthly means. In this paper, we will show that the new results not only temporally span 10 years longer than its predecessor, Release 3, but agree significantly better with the BSRN data over the land and PMEL data over the ocean.

Taiping Zhang↗

NASA NTRS2002

Internet Data Delivery for Future Space Missions

Ongoing work at National Aeronautics and Space Administration Goddard Space Flight Center (NASA/GSFC), seeks to apply standard Internet applications and protocols to meet the technology challenge of future satellite missions. Internet protocols and technologies are under study as a future means to provide seamless dynamic communication among heterogeneous instruments, spacecraft, ground stations, constellations of spacecraft, and science investigators. The primary objective is to design and demonstrate in the laboratory the automated end-to-end transport of files in a simulated dynamic space environment using off-the-shelf, low-cost, commodity-level standard applications and protocols. The demonstrated functions and capabilities will become increasingly significant in the years to come as both earth and space science missions fly more sensors and as the need increases for more network-oriented mission operations. Another element of increasing significance will be the increased cost effectiveness of designing, building, integrating, and operating instruments and spacecraft that will come to the fore as more missions take up the approach of using commodity-level standard communications technologies. This paper describes how an IP (Internet Protocol)-based communication architecture can support all existing operations concepts and how it will enable some new and complex communication and science concepts. The authors identify specific end-to-end data flows from the instruments to the control centers and scientists, and then describe how each data flow can be supported using standard Internet protocols and applications. The scenarios include normal data downlink and command uplink as well as recovery scenarios for both onboard and ground failures. The scenarios are based on an Earth orbiting spacecraft with downlink data rates from 300 Kbps to 4 Mbps. Included examples are based on designs currently being investigated for potential use by the Global Precipitation Measurement (GPM) mission.

Rash, James↗

NASA NTRS1995

Fault recovery in the reliable multicast protocol

The Reliable Multicast Protocol (RMP) provides a unique, group-based model for distributed programs that need to handle reconfiguration events at the application layer. This model, called membership views, provides an abstraction in which events such as site failures, network partitions, and normal join-leave events are viewed as group reformations. RMP provides access to this model through an application programming interface (API) that notifies an application when a group is reformed as the result of a some event. RMP provides applications with reliable delivery of messages using an underlying IP Multicast (12, 5) media to other group members in a distributed environment even in the case of reformations. A distributed application can use various Quality of Service (QoS) levels provided by RMP to tolerate group reformations. This paper explores the implementation details of the mechanisms in RMP that provide distributed applications with membership view information and fault recovery capabilities.

Callahan, John R.↗

NASA NTRS1996

Specification and Design of a Fault Recovery Model for the Reliable Multicast Protocol

The Reliable Multicast Protocol (RMP) provides a unique, group-based model for distributed programs that need to handle reconfiguration events at the application layer. This model, called membership views, provides an abstraction in which events such as site failures, network partitions, and normal join-leave events are viewed as group reformations. RMP provides access to this model through an application programming interface (API) that notifies an application when a group is reformed as the result of a some event. RMP provides applications with reliable delivery of messages using an underlying IP Multicast media to other group members in a distributed environment even in the case of reformations. A distributed application can use various Quality of Service (QoS) levels provided by RMP to tolerate group reformations. This paper explores the implementation details of the mechanisms in RMP that provide distributed applications with membership view information and fault recovery capabilities.

Montgomery, Todd↗

NASA NTRS2001

Network Configuration Analysis for Formation Flying Satellites

The performance of two networks to support autonomous multi-spacecraft formation flying systems is presented. Both systems are comprised of a ten-satellite formation, with one of the satellites designated as the central or 'mother ship.' All data is routed through the mother ship to the terrestrial network. The first system uses a TCP/EP over ATM protocol architecture within the formation, and the second system uses the IEEE 802.11 protocol architecture within the formation. The simulations consist of file transfers using either the File Transfer Protocol (FTP) or the Simple Automatic File Exchange (SAFE) Protocol. The results compare the IP queuing delay, IP queue size and IP processing delay at the mother ship as well as end-to-end delay for both systems. In all cases, using IEEE 802.11 within the formation yields less delay. Also, the throughput exhibited by SAFE is better than FTP.

Knoblock, Eric J.↗

NASA NTRS1983

Satellite systems requirements for land mobile communications

The system design objective is to provide a satellite link through a gateway station, connecting mobile users in areas not served by a terrestrial cellular system to the switched telephone network (STN). The proposed frequency allocation comprises a pair of 10-MHz bands in the 806-890 MHz range specified by the 1979 World Administrative Radio Conference (WARC) for land-mobile satellite service (LMSS). The satellite design is constrained by projected STS capability with an upper stage of the wide-body Centaur or Integral Propulsion System (IPS) type. For the latter (a TRW design), the payload is limited to approximately 10,400 lb. The design is to be based on 1990's technology, with initial operating capability scheduled for 1995. The satellite should be designed for a 7-year life. Mobile-unit compatibility with cellular system specifications is desirable, if consistent with other system requirements.

Horstein, M.↗

NASA NTRS2004

Adding HDLC Framing to CCSDS Recommendations

Current Space IP missions use High-Level Data Link Control (HDLC) framing to provide standard serial link interfaces over a space link. HDLC is the standard framing technique used by all routers over clock and data serial lines and is also the basic framing used in all Frame Relay services which are widely deployed in national and international communication networks. In late 2003 a presentation was made to CCSDS committees to initiate discussion on including HDLC in the CCSDS recommendations for space systems. This presentation will summarize the differences between variable length HDLC frames and fixed length CCSDS frames. It will also discuss where and how HDLC framing would fit into the overall CCSDS structures.

Hogie, Keith↗

NASA NTRS2013

System Administrator for LCS Development Sets

The Spaceport Command and Control System Project is creating a Checkout and Control System that will eventually launch the next generation of vehicles from Kennedy Space Center. KSC has a large set of Development and Operational equipment already deployed in several facilities, including the Launch Control Center, which requires support. The position of System Administrator will complete tasks across multiple platforms (Linux/Windows), many of them virtual. The Hardware Branch of the Control and Data Systems Division at the Kennedy Space Center uses system administrators for a variety of tasks. The position of system administrator comes with many responsibilities which include maintaining computer systems, repair or set up hardware, install software, create backups and recover drive images are a sample of jobs which one must complete. Other duties may include working with clients in person or over the phone and resolving their computer system needs. Training is a major part of learning how an organization functions and operates. Taking that into consideration, NASA is no exception. Training on how to better protect the NASA computer infrastructure will be a topic to learn, followed by NASA work polices. Attending meetings and discussing progress will be expected. A system administrator will have an account with root access. Root access gives a user full access to a computer system and or network. System admins can remove critical system files and recover files using a tape backup. Problem solving will be an important skill to develop in order to complete the many tasks.

Virtualizing in Linux↗