Search NASASearch

SEARCH · Search NASA

Results for “IP”

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

Space Network IP Services (SNIS): An Architecture for Supporting Low Earth Orbiting IP Satellite Missions

The NASA Space Network (SN) supports a variety of missions using the Tracking and Data Relay Satellite System (TDRSS), which includes ground stations in White Sands, New Mexico and Guam. A Space Network IP Services (SNIS) architecture is being developed to support future users with requirements for end-to-end Internet Protocol (IP) communications. This architecture will support all IP protocols, including Mobile IP, over TDRSS Single Access, Multiple Access, and Demand Access Radio Frequency (RF) links. This paper will describe this architecture and how it can enable Low Earth Orbiting IP satellite missions.

Israel, David J.

Enabling IP Header Compression in COTS Routers via Frame Relay on a Simplex Link

NASA is moving toward a networkcentric communications architecture and, in particular, is building toward use of Internet Protocol (IP) in space. The use of IP is motivated by its ubiquitous application in many communications networks and in available commercial off-the-shelf (COTS) technology. The Constellation Program intends to fit two or more voice (over IP) channels on both the forward link to, and the return link from, the Orion Crew Exploration Vehicle (CEV) during all mission phases. Efficient bandwidth utilization of the links is key for voice applications. In Voice over IP (VoIP), the IP packets are limited to small sizes to keep voice latency at a minimum. The common voice codec used in VoIP is G.729. This new algorithm produces voice audio at 8 kbps and in packets of 10-milliseconds duration. Constellation has designed the VoIP communications stack to use the combination of IP/UDP/RTP protocols where IP carries a 20-byte header, UDP (User Datagram Protocol) carries an 8-byte header, and RTP (Real Time Transport Protocol) carries a 12-byte header. The protocol headers total 40 bytes and are equal in length to a 40-byte G.729 payload, doubling the VoIP latency. Since much of the IP/UDP/RTP header information does not change from IP packet to IP packet, IP/UDP/RTP header compression can avoid transmission of much redundant data as well as reduce VoIP latency. The benefits of IP header compression are more pronounced at low data rate links such as the forward and return links during CEV launch. IP/UDP/RTP header compression codecs are well supported by many COTS routers. A common interface to the COTS routers is through frame relay. However, enabling IP header compression over frame relay, according to industry standard (Frame Relay IP Header Compression Agreement FRF.20), requires a duplex link and negotiations between the compressor router and the decompressor router. In Constellation, each forward to and return link from the CEV in space is treated independently as a simplex link. Without negotiation, the COTS routers are prevented from entering into the IP header compression mode, and no IP header compression would be performed. An algorithm is proposed to enable IP header compression in COTS routers on a simplex link with no negotiation or with a one-way messaging. In doing so, COTS routers can enter IP header compression mode without the need to handshake through a bidirectional link as required by FRF.20. This technique would spoof the routers locally and thereby allow the routers to enter into IP header compression mode without having the negotiations between routers actually occur. The spoofing function is conducted by a frame relay adapter (also COTS) with the capability to generate control messages according to the FRF.20 descriptions. Therefore, negotiation is actually performed between the FRF.20 adapter and the connecting COTS router locally and never occurs over the space link. Through understanding of the handshaking protocol described by FRF.20, the necessary FRF.20 negotiations messages can be generated to control the connecting router, not only to turn on IP header compression but also to adjust the compression parameters. The FRF.20 negotiation (or control) message is composed in the FRF.20 adapter by interpreting the incoming router request message. Many of the fields are simply transcribed from request to response while the control field indicating response and type are modified.

Nguyen, Sam P.

GMI-IPS: Python Processing Software for Aircraft Campaigns

NASA's Atmospheric Tomography Mission (ATom) seeks to understand the impact of anthropogenic air pollution on gases in the Earth's atmosphere. Four flight campaigns are being deployed on a seasonal basis to establish a continuous global-scale data set intended to improve the representation of chemically reactive gases in global atmospheric chemistry models. The Global Modeling Initiative (GMI), is creating chemical transport simulations on a global scale for each of the ATom flight campaigns. To meet the computational demands required to translate the GMI simulation data to grids associated with the flights from the ATom campaigns, the GMI ICARTT Processing Software (GMI-IPS) has been developed and is providing key functionality for data processing and analysis in this ongoing effort. The GMI-IPS is written in Python and provides computational kernels for data interpolation and visualization tasks on GMI simulation data. A key feature of the GMI-IPS, is its ability to read ICARTT files, a text-based file format for airborne instrument data, and extract the required flight information that defines regional and temporal grid parameters associated with an ATom flight. Perhaps most importantly, the GMI-IPS creates ICARTT files containing GMI simulated data, which are used in collaboration with ATom instrument teams and other modeling groups. The initial main task of the GMI-IPS is to interpolate GMI model data to the finer temporal resolution (1-10 seconds) of a given flight. The model data includes basic fields such as temperature and pressure, but the main focus of this effort is to provide species concentrations of chemical gases for ATom flights. The software, which uses parallel computation techniques for data intensive tasks, linearly interpolates each of the model fields to the time resolution of the flight. The temporally interpolated data is then saved to disk, and is used to create additional derived quantities. In order to translate the GMI model data to the spatial grid of the flight path as defined by the pressure, latitude, and longitude points at each flight time record, a weighted average is then calculated from the nearest neighbors in two dimensions (latitude, longitude). Using SciPya's Regular Grid Interpolator, interpolation functions are generated for the GMI model grid and the calculated weighted averages. The flight path points are then extracted from the ATom ICARTT instrument file, and are sent to the multi-dimensional interpolating functions to generate GMI field quantities along the spatial path of the flight. The interpolated field quantities are then written to a ICARTT data file, which is stored for further manipulation. The GMI-IPS is aware of a generic ATom ICARTT header format, containing basic information for all flight campaigns. The GMI-IPS includes logic to edit metadata for the derived field quantities, as well as modify the generic header data such as processing dates and associated instrument files. The ICARTT interpolated data is then appended to the modified header data, and the ICARTT processing is complete for the given flight and ready for collaboration. The output ICARTT data adheres to the ICARTT file format standards V1.1. The visualization component of the GMI-IPS uses Matplotlib extensively and has several functions ranging in complexity. First, it creates a model background curtain for the flight (time versus model eta levels) with the interpolated flight data superimposed on the curtain. Secondly, it creates a time-series plot of the interpolated flight data. Lastly, the visualization component creates averaged 2D model slices (longitude versus latitude) with overlaid flight track circles at key pressure levels. The GMI-IPS consists of a handful of classes and supporting functionality that have been generalized to be compatible with any ICARTT file that adheres to the base class definition. The base class represents a generic ICARTT entry, only defining a single time entry and 3D spatial positioning parameters. Other classes inherit from this base class; several classes for input ICARTT instrument files, which contain the necessary flight positioning information as a basis for data processing, as well as other classes for output ICARTT files, which contain the interpolated model data. Utility classes provide functionality for routine procedures such as: comparing field names among ICARTT files, reading ICARTT entries from a data file and storing them in data structures, and returning a reduced spatial grid based on a collection of ICARTT entries. Although the GMI-IPS is compatible with GMI model data, it can be adapted with reasonable effort for any simulation that creates Hierarchical Data Format (HDF) files. The same can be said of its adaptability to ICARTT files outside of the context of the ATom mission. The GMI-IPS contains just under 30,000 lines of code, eight classes, and a dozen drivers and utility programs. It is maintained with GIT source code management and has been used to deliver processed GMI model data for the ATom campaigns that have taken place to date.

Damon, M. R.

Solar Type II Radio Bursts and IP Type II Events

We have examined radio data from the WAVES experiment on the Wind spacecraft in conjunction with ground-based data in order to investigate the relationship between the shocks responsible for metric type II radio bursts and the shocks in front of coronal mass ejections (CMEs). The bow shocks of fast, large CMEs are strong interplanetary (IP) shocks, and the associated radio emissions often consist of single broad bands starting below approx. 4 MHz; such emissions were previously called IP type II events. In contrast, metric type II bursts are usually narrowbanded and display two harmonically related bands. In addition to displaying complete dynamic spectra for a number of events, we also analyze the 135 WAVES 1 - 14 MHz slow-drift time periods in 2001-2003. We find that most of the periods contain multiple phenomena, which we divide into three groups: metric type II extensions, IP type II events, and blobs and bands. About half of the WAVES listings include probable extensions of metric type II radio bursts, but in more than half of these events, there were also other slow-drift features. In the 3 yr study period, there were 31 IP type II events; these were associated with the very fastest CMEs. The most common form of activity in the WAVES events, blobs and bands in the frequency range between 1 and 8 MHz, fall below an envelope consistent with the early signatures of an IP type II event. However, most of this activity lasts only a few tens of minutes, whereas IP type II events last for many hours. In this study we find many examples in the radio data of two shock-like phenomena with different characteristics that occur simultaneously in the metric and decametric/hectometric bands, and no clear example of a metric type II burst that extends continuously down in frequency to become an IP type II event. The simplest interpretation is that metric type II bursts, unlike IP type II events, are not caused by shocks driven in front of CMEs.

Cane, H. V.

A decentralized software bus based on IP multicas ting

We describe decentralized reconfigurable implementation of a conference management system based on the low-level Internet Protocol (IP) multicasting protocol. IP multicasting allows low-cost, world-wide, two-way transmission of data between large numbers of conferencing participants through the Multicasting Backbone (MBone). Each conference is structured as a software bus -- a messaging system that provides a run-time interconnection model that acts as a separate agent (i.e., the bus) for routing, queuing, and delivering messages between distributed programs. Unlike the client-server interconnection model, the software bus model provides a level of indirection that enhances the flexibility and reconfigurability of a distributed system. Current software bus implementations like POLYLITH, however, rely on a centralized bus process and point-to-point protocols (i.e., TCP/IP) to route, queue, and deliver messages. We implement a software bus called the MULTIBUS that relies on a separate process only for routing and uses a reliable IP multicasting protocol for delivery of messages. The use of multicasting means that interconnections are independent of IP machine addresses. This approach allows reconfiguration of bus participants during system execution without notifying other participants of new IP addresses. The use of IP multicasting also permits an economy of scale in the number of participants. We describe the MULITIBUS protocol elements and show how our implementation performs better than centralized bus implementations.

Callahan, John R.

Challenges Regarding IP Core Functional Reliability

For many years, intellectual property (IP) cores have been incorporated into field programmable gate array (FPGA) and application specific integrated circuit (ASIC) design flows. However, the usage of large complex IP cores were limited within products that required a high level of reliability. This is no longer the case. IP core insertion has become mainstream including their use in highly reliable products. Due to limited visibility and control, challenges exist when using IP cores and subsequently compromise product reliability. We discuss challenges and suggest potential solutions to critical application IP insertion.

IP cores

Mobile-ip Aeronautical Network Simulation Study

NASA is interested in applying mobile Internet protocol (mobile-ip) technologies to its space and aeronautics programs. In particular, mobile-ip will play a major role in the Advanced Aeronautic Transportation Technology (AATT), the Weather Information Communication (WINCOMM), and the Small Aircraft Transportation System (SATS) aeronautics programs. This report presents the results of a simulation study of mobile-ip for an aeronautical network. The study was performed to determine the performance of the transmission control protocol (TCP) in a mobile-ip environment and to gain an understanding of how long delays, handoffs, and noisy channels affect mobile-ip performance.

Ivancic, William D.

GMI-IPS: Processing & Visualization Software Used in ATom DC-8 Aircraft Studies

NASA's Atmospheric Tomography Mission (ATom) deployed in each of the four seasons during 2016-2018, the DC-8 aircraft in order to establish global-scale datasets intended to improve the representation of chemically reactive gases in global atmospheric chemistry models (ACMs). The Global Modeling Initiative (GMI) executed simulations for each ATom flight using the GMI Chemistry Transport Model (GMI-CTM) to provide species concentrations of chemical gases along the DC-8 flight transects. To solve the problem of translating the GMI-CTM simulation data to the unique spatial resolutions of each ATom flight, the GMI ICARTT Processing Software (GMI-IPS) was developed.The GMI-IPS is written in Python and provides data processing, flight extraction, and visualization support for aircraft research projects using ICARTT format, which is a standard format for airborne instrument data. Additionally, the GMI-IPS interpolates global gridded model data from Hierarchical Data Format (HDF) to ICARTT compatible flight transects. Software classes for instruments and collections provided by the ATom DC-8 aircraft such as MER10, MMS, etc. are derived from a common base class. Other functionality provided by the GMI-IPS are: deriving missing flight entries along a transect, reading ICARTT entries from file, and providing Python data structures for storing flight and model information, and more.The GMI-IPS is GIT source controlled, has approximately 30,000 lines of code, and supports parallelization across data collections. It delivered GMI-CTM data for more than forty distinct DC-8 aircraft flights that took place under ATom. The output ICARTT files adhere to format standard V1.1, and pass the scan utility provided by NASA LaRC Airborne Science Data for Atmospheric Composition. This presentation will include a software and methods overview, and results from ATom, including assessments using the GMI-CTM showing how well observations from ATom flight transects represent a broader region.

Damon, M. R.

The Way to the Future Has Already Started: ICAO Aeronautical Telecommunication Network (ATN) Using Internet Protocol Suite (IPS) Standards and Protocol Evolution Update

Millions of people are able to exchange information over phones, computers, tablets and an array of new interconnected devices such as sensors, cameras, home appliances and others are increasingly becoming networked. At the core of this sizeable interconnection is a set of underlying protocols that enable millions of devices to seamlessly talk to each other. Aviation, as many other industries have, utilizes the internet protocol for ground-to-ground network communications and efforts are underway to bring it to the cockpit.In 2015, the International Civil Aviation Organization (ICAO) published the second edition of Document 9896 (Doc 9896) titled: Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. This manual adopted the Internet protocol version 6 (IPv6) for Internet layer interoperability. Document 9896 defined data communications protocols and services to be used for implementing aeronautical telecommunication network (ATN) using the Internet protocol suite (IPS). The document provided technical specifications that addressed security, network and transport protocols, described applications, supported by ATN/IPS and provided communications guidance. The international aviation community working under the guidance of ICAO initiated work on updates to Doc 9896. Under the ICAO Communication Panel, Working Group Internetworking (WG-I) got this challenging task. Key areas of work for WG-I are related to ATN/IPS Security and ANT/IPS Mobility. Two sub-groups have been assembled to work on these elements. The ICAO anticipates the release of updated Doc 9896 in 2020. Additional ATN/IPS standardization efforts include Radio Technical Commission for Aeronautics Special Committee 223 (RTCA SC-223) IPS profile development, Airlines Electronic Engineering Committee (AEEC) A658 Roadmap of IPS future activities and European Organization for Civil Aviation Equipment (EUROCAE) WG-108 development of guidance documentation.This paper describes ICAO WG-I approach to update key areas of the document in closed coordination with AEEC, RTCA and EUROCAE committees supporting the development of ATN/IPS. Additionally, the paper will explore WG-I mobility solutions under investigation, security developments, IPv6 addressing challenges and other proposed updates. Finally, as new operational expectations such as Free Route and Remote Piloted Aircraft System integration are currently pushing the boundaries set by old operational concepts, the paper identifies the emerging new challenges that will drive the ATN/IPS development beyond 2020. They are related to future voice utilization, System Wide Information Management and Remotely Piloted Aircraft System deployment. IPS systems are seen as the only way forward.

Apaza, Rafael

Continuously Connected With Mobile IP

Cisco Systems developed Cisco Mobile Networks, making IP devices mobile. With this innovation, a Cisco router and its connected IP devices can roam across network boundaries and connection types. Because a mobile user is able to keep the same IP address while roaming, a live IP connection can be maintained without interruption. Glenn Research Center jointly tested the technology with Cisco, and is working to use it on low-earth-orbiting research craft. With Cisco's Mobile Networks functionality now available in Cisco IOS Software release 12.2(4)T, the commercial advantages and benefits are numerous. The technology can be applied to public safety, military/homeland security, emergency management services, railroad and shipping systems, and the automotive industry. It will allow ambulances, police, firemen, and the U.S. Coast Guard to stay connected to their networks while on the move. In the wireless battlefield, the technology will provide rapid infrastructure deployment for U.S. national defense. Airline, train, and cruise passengers utilizing Cisco Mobile Networks can fly all around the world with a continuous Internet connection. Cisco IOS(R) Software is a registered trademark of Cisco Systems.

Source record

Rationale, Scenarios, and Profiles for the Application of the Internet Protocol Suite (IPS) in Space Operations

This greenbook captures some of the current, planned and possible future uses of the Internet Protocol (IP) as part of Space Operations. It attempts to describe how the Internet Protocol is used in specific scenarios. Of primary focus is low-earth-orbit space operations, which is referred to here as the design reference mission (DRM). This is because most of the program experience drawn upon derives from this type of mission. Application profiles are provided. This includes parameter settings programs have proposed for sending IP datagrams over CCSDS links, the minimal subsets and features of the IP protocol suite and applications expected for interoperability between projects, and the configuration, operations and maintenance of these IP functions. Of special interest is capturing the lessons learned from the Constellation Program in this area, since that program included a fairly ambitious use of the Internet Protocol.

Benbenek, Daniel B.

IPS activity observed as a precursor of solar induced terrestrial activity

A radio telescope designed to exploit the interplanetary scintillation (IPS) technique and locate, map, and track solar wind disturbances which result in geomagnetic disturbances, thereby providing a forecast capability, is described. Preliminary results from operation of the telescope include: (1) evidence for a precursor signal in the IPS activity with a 1-2 day lead time with respect to density enhancements which frequently give rise to geomagnetic activity; (2) detection of a spectral broadening signature which also serves as a precursor of geomagnetic activity; (3) out-of-the-ecliptic plasma density enhancements which were not detected by near-Earth, ecliptic plane spacecraft; (4) detection of 12 corotating density enhancements;(5) detection of over 80 sources which give detectable scintillation of which 45 have been used for detailed synoptic analysis and 9 for spectral analysis; and (6) measurement of 0-lag coefficient of 0.56 between density and IPS activity enhancements.

Cronyn, W. M.

The velocity and the density spectrum of the solar wind from simultaneous three-frequency IPS observations

Density inhomogeneities in the solar wind cause fluctuations regarding the emission of small diameter radio sources. Such fluctuations are called interplanetary scintillation (IPS). IPS has been studied to obtain information on both the solar wind and on the radio sources. In the present investigation it is attempted to extract information about the solar wind from simultaneous IPS observations at three radio frequencies and a single antenna. Data were recorded at frequencies of 270 MHz, 340 MHz, and 470 MHz on a 91 m telescope. Five different radio sources were observed. The observations are compared with theoretical predictions for spectra, cross-spectra, and cross-correlations using weak scattering theory and various models for the wavenumber spectrum of density inhomogeneities in the solar wind. Good fits are obtained over the observed wavenumbers to a spectrum modeled as a power law.

Scott, S. L.

Actuator development for the Instrument Pointing System (IPS)

The mechanisms of the instrument pointing system (IPS) are described. Particular emphasis is placed on the actuators which are necessary for operating the IPS. The actuators are described as follows: (1) two linear actuators that clamp the gimbals down during ascent and descent; (2) two linear actuators that attach the payload to the IPS during the mission, and release it into the payload clamps; (3) one rotational actuator that opens and closes the payload clamps; and (4) three identical drive units that represent the three orthogonal gimbal axes and are the prime movers for pointing. Design features, manufacturing problems, test performance, and results are presented.

Suttner, K.

IPS guidestar selection for stellar mode (ASTRO)

This report describes how guide stars are selected for the Optical Sensor Package (OSP) for the Instrument Pointing System (IPS) when it is operating in the stellar mode on the ASTRO missions. It also describes how the objective loads are written and how the various roll angles are related; i.e., the celestial roll or position angle, the objective load roll angles, and the IPS gimbal angles. There is a brief description of how the IPS operates and its various modes of operation; i.e., IDOP, IDIN, and OSPCAL.

Mullins, Larry

Time-resolved IUE studies of cataclysmic variables. I - Eclipsing systems IP Peg, PG 1030+590, and V1315 Aql

IUE time-resolved spectra of the high-inclination cataclysmic variables IP Peg, PG 1030+590, and V1315 Aql are analyzed in order to determine the characteristics of the disk, hotspots, and white dwarfs. The UV continuum flux distributions are generally flatter than systems of low inclination and high mass-transfer rate, and the white dwarfs/inner disk appear to be relatively cool (15,000-19,000 K) for their orbital periods, possibly because the boundary layers are blocked from view. The continuum fluxes increase at spot phases, with the spot providing the dominant flux in IP Peg. The spot temperatures range from hot (20,000 K) in IP Peg, and perhaps in PG 1030+590, to cool (11,000 K) in V1315 Aql. The C IV emission lines show slightly larger decreases at spot phases than during eclipse, which implies an extended stream area.

Szkody, Paula

The Spacelab IPS Star Simulator

The cost of doing business in space is very high. If errors occur while in orbit the costs grow and desired scientific data may be corrupted or even lost. The Spacelab Instrument Pointing System (IPS) Star Simulator is a unique test bed that allows star trackers to interface with simulated stars in a laboratory before going into orbit. This hardware-in-the-loop testing of equipment on earth increases the probability of success while in space. The IPS Star Simulator provides three fields of view 2.55 x 2.55 deg each for input into star trackers. The fields of view are produced on three separate monitors. Each monitor has 4096 x 4096 addressable points and can display 50 stars (pixels) maximum at a given time. The pixel refresh rate is 1000 Hz. The spectral output is approximately 550 nm. The available relative visual magnitude range is two to eight visual magnitudes. The star size is less than 100 arcsec. The minimum star movement is less than 5 arcsec and the relative position accuracy is approximately 40 arcsec. The purpose of this paper is to describe the IPS Star Simulator design and to provide an operational scenario so others may gain from the approach and possible use of the system.

Wessling, Francis C., III

Dependence of velocity fluctuations on solar wind speeds: A simple analysis with IPS method

A number of theoretical works have suggested that MHD plasma fluctuations in solar winds should play an important role particularly in the acceleration of high speed winds inside or near 0.1 AU from the sun. Since velocity fluctuations in solar winds are expected to be caused by the MHD plasma fluctuations, measurements of the velocity fluctuations give clues to reveal the acceleration process of solar winds. We made interplanetary scintillation (IPS) observations at the region out of 0.1 AU to investigate dependence of velocity fluctuations on flow speeds. For evaluating the velocity fluctuation of a flow, we selected the IPS data-set acquired at 2 separate antennas which located in the projected flow direction onto the baseline plane, and tried to compare skewness of the observed cross correlation function(CCF) with skewness of modeled CCFs in which velocity fluctuations were parametrized. The integration effect of IPS along a ray path was also taken into account in the estimation of modeled CCFs. Although this analysis method is significant to derive only parallel fluctuation components to the flow directions, preliminary analyses show following results: (1) High speed winds (Vsw greater than or equal to 500 km/s out of 0.3 AU) indicate enhancement of velocity fluctuations near 0.1 AU; and (2) Low speed winds (Vsw less than or equal to 400 Km/s out of 0.3 AU) indicate small velocity fluctuations at any distances.

Misawa, H.