Search NASA⌕ Search

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 289 records · Page 16

Reconfigurable Protocol Sensing in an End-to-End Demonstration

In this work, we present sensing performance using an architecture for a reconfigurable protocol chip for spacebased applications. Toward utilizing the IP packet architecture, utilizing data link layer framing structures for multiplexed data on a channel are the targeted application considered for demonstration purposes. Specifically, we examine three common framing standards and present the sensing performance of these standards and their relative de-correlation metrics. Some analysis is performed to investigate the impact of lossy links. Finally, we present results on a demonstration platform that integrated reconfigurable sensing technology into the Ground Station Interface Device (GRID) for End-to-End IP demonstrations in space.

space based applications↗

Technology Developments Integrating a Space Network Communications Testbed

As future manned and robotic space explorations missions involve more complex systems, it is essential to verify, validate, and optimize such systems through simulation and emulation in a low cost testbed environment. The goal of such a testbed is to perform detailed testing of advanced space and ground communications networks, technologies, and client applications that are essential for future space exploration missions. We describe the development of new technologies enhancing our Multi-mission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE) that enable its integration in a distributed space communications testbed. MACHETE combines orbital modeling, link analysis, and protocol and service modeling to quantify system performance based on comprehensive considerations of different aspects of space missions. It can simulate entire networks and can interface with external (testbed) systems. The key technology developments enabling the integration of MACHETE into a distributed testbed are the Monitor and Control module and the QualNet IP Network Emulator module. Specifically, the Monitor and Control module establishes a standard interface mechanism to centralize the management of each testbed component. The QualNet IP Network Emulator module allows externally generated network traffic to be passed through MACHETE to experience simulated network behaviors such as propagation delay, data loss, orbital effects and other communications characteristics, including entire network behaviors. We report a successful integration of MACHETE with a space communication testbed modeling a lunar exploration scenario. This document is the viewgraph slides of the presentation.

hybrid simulation↗

IPv6 and IPsec Tests of a Space-Based Asset, the Cisco Router in Low Earth Orbit (CLEO)

This report documents the design of network infrastructure to support testing and demonstrating network-centric operations and command and control of space-based assets, using IPv6 and IPsec. These tests were performed using the Cisco router in Low Earth Orbit (CLEO), an experimental payload onboard the United Kingdom – Disaster Monitoring Constellation (UKDMC) satellite built and operated by Surrey Satellite Technology Ltd (SSTL). On Thursday, 29 March 2007, NASA Glenn Research Center, Cisco Systems and SSTL performed the first configuration and demonstration of IPsec and IPv6 onboard a satellite in low Earth orbit. IPv6 is the next generation of the Internet Protocol (IP), designed to improve on the popular IPv4 that built the Internet, while IPsec is the protocol used to secure communication across IP networks. This demonstration was made possible in part by NASA’s Earth Science Technology Office (ESTO) and shows that new commercial technologies such as mobile networking, IPv6 and IPsec can be used for commercial, military and government space applications. This has direct application to NASA’s Vision for Space Exploration. The success of CLEO has paved the way for new space-based Internet technologies, such as the planned Internet Routing In Space (IRIS) payload at geostationary orbit, which will be a U.S. Department of Defense Joint Capability Technology Demonstration. This is a sanitized report for public distribution. All real addressing has been change to psueco addressing.

Communication↗

Autonomic Communications for Space: The Next Frontier?

Autonomic communications has been gaining ground as a vision for next generation communications. The success and flexibility of the Internet has lead to evaluations of utilizing IP for communications in space. The limitations of today's Internet ultimately also imply limitations for an IP deployment in space. Issues affecting the design of a future self-directing and self-managing data communications network for future space missions based on autonomic communications concepts are described and examined.

Rash, James L.↗

Use of the Delay-Tolerant Networking Bundle Protocol from Space

The Disaster Monitoring Constellation (DMC), constructed by Survey Satellite Technology Ltd (SSTL), is a multisatellite Earth-imaging low-Earth-orbit sensor network where captured image swaths are stored onboard each satellite and later downloaded from the satellite payloads to a ground station. Store-and-forward of images with capture and later download gives each satellite the characteristics of a node in a Delay/Disruption Tolerant Network (DTN). Originally developed for the Interplanetary Internet, DTNs are now under investigation in an Internet Research Task Force (IRTF) DTN research group (RG), which has developed a bundle architecture and protocol. The DMC is currently unique in its adoption of the Internet Protocol (IP) for its imaging payloads and for satellite command and control, based around reuse of commercial networking and link protocols. These satellites use of IP has enabled earlier experiments with the Cisco router in Low Earth Orbit (CLEO) onboard the constellation's UK-DMC satellite. Earth images are downloaded from the satellites using a custom IPbased high-speed transfer protocol developed by SSTL, Saratoga, which tolerates unusual link environments. Saratoga has been documented in the Internet Engineering Task Force (IETF) for wider adoption. We experiment with use of DTNRG bundle concepts onboard the UKDMC satellite, by examining how Saratoga can be used as a DTN convergence layer to carry the DTNRG Bundle Protocol, so that sensor images can be delivered to ground stations and beyond as bundles. This is the first successful use of the DTNRG Bundle Protocol in a space environment. We use our practical experience to examine the strengths and weaknesses of the Bundle Protocol for DTN use, paying attention to fragmentation, custody transfer, and reliability issues.

Wood, Lloyd↗

Use of Cumulative Degradation Factor Prediction and Life Test Result of the Thruster Gimbal Assembly Actuator for the Dawn Flight Project

The Dawn Ion Propulsion System is the ninth project in NASA s Discovery Program. The Dawn spacecraft is being developed to enable the scientific investigation of the two heaviest main-belt asteroids, Vesta and Ceres. Dawn is the first mission to orbit two extraterrestrial bodies, and the first to orbit a main-belt asteroid. The mission is enabled by the onboard Ion Propulsion System (IPS) to provide the post-launch delta-V. The three Ion Engines of the IPS are mounted on Thruster Gimbal Assembly (TGA), with only one engine operating at a time for this 10-year mission. The three TGAs weigh 14.6 kg.

Lo, C. John↗

EVA 2010: Preparing for International Space Station EVA Operations Post-Space Shuttle Retirement

The expected retirement of the NASA Space Transportation System (also known as the Space Shuttle ) by 2011 will pose a significant challenge to Extra-Vehicular Activities (EVA) on-board the International Space Station (ISS). The EVA hardware currently used to assemble and maintain the ISS was designed assuming that it would be returned to Earth on the Space Shuttle for refurbishment, or if necessary for failure investigation. With the retirement of the Space Shuttle, a new concept of operations was developed to enable EVA hardware (Extra-vehicular Mobility Unit (EMU), Airlock Systems, EVA tools, and associated support hardware and consumables) to perform ISS EVAs until 2015, and possibly beyond to 2020. Shortly after the decision to retire the Space Shuttle was announced, the EVA 2010 Project was jointly initiated by NASA and the OneEVA contractor team. The challenges addressed were to extend the operating life and certification of EVA hardware, to secure the capability to launch EVA hardware safely on alternate launch vehicles, to protect for EMU hardware operability on-orbit, and to determine the source of high water purity to support recharge of PLSSs (no longer available via Shuttle). EVA 2010 Project includes the following tasks: the development of a launch fixture that would allow the EMU Portable Life Support System (PLSS) to be launched on-board alternate vehicles; extension of the EMU hardware maintenance interval from 3 years (current certification) to a minimum of 6 years (to extend to 2015); testing of recycled ISS Water Processor Assembly (WPA) water for use in the EMU cooling system in lieu of water resupplied by International Partner (IP) vehicles; development of techniques to remove & replace critical components in the PLSS on-orbit (not routine); extension of on-orbit certification of EVA tools; and development of an EVA hardware logistical plan to support the ISS without the Space Shuttle. Assumptions for the EVA 2010 Project included no more than 8 EVAs per year for ISS EVA operations in the Post-Shuttle environment and limited availability of cargo upmass on IP launch vehicles. From 2010 forward, EVA operations on-board the ISS without the Space Shuttle will be a paradigm shift in safely operating EVA hardware on orbit and the EVA 2010 effort was initiated to accommodate this significant change in EVA evolutionary history.

Chullen, Cinda↗

Evolution of Interplanetary Shocks and their CME Drivers

Shock-driving coronal mass ejections (CMEs) constitute the most energetic phenomena in the heliosphere. The shocks can be identified in a number of ways based on remote-sensing and in situ observations. Type II radio bursts are the earliest indicators of shocks that accelerate electrons to energies up to -10 keV. Solar energetic particle (SEP) events are always accompanied by long wavelength type II bursts indicating that the same shock accelerates ions and electrons. A recent investigation involving a large number of interplanetary (IP) shocks revealed that about 35% of them do not produce type II bursts (radio quiet, RQ) or SEPs. Comparison of the RQ shocks with the radio loud (RL) ones revealed some interesting results such as: (1) the lack of evidence for blast waves,(2) energetic particle enhancement in the shock front in -20% of RQ shocks, and (3) determination of the difference between the RQ and RL shocks in terms of the different kinematic properties of the associated CMEs. On the other hand the shock properties measured at I AU are not too different for the RQ and RL cases. This can be attributed to the interaction with the IP medium, which seems to erase the difference. Implications of this evolution for the geoeffectiveness is also discussed.

Gopalswamy, Natchimuthuk↗

Post-Shuttle EVA Operations on ISS

The expected retirement of the NASA Space Transportation System (also known as the Space Shuttle ) by 2011 will pose a significant challenge to Extra-Vehicular Activities (EVA) on-board the International Space Station (ISS). The EVA hardware currently used to assemble and maintain the ISS was designed assuming that it would be returned to Earth on the Space Shuttle for refurbishment, or if necessary for failure investigation. With the retirement of the Space Shuttle, a new concept of operations was developed to enable EVA hardware (Extra-vehicular Mobility Unit (EMU), Airlock Systems, EVA tools, and associated support hardware and consumables) to perform ISS EVAs until 2015, and possibly beyond to 2020. Shortly after the decision to retire the Space Shuttle was announced, the EVA 2010 Project was jointly initiated by NASA and the One EVA contractor team. The challenges addressed were to extend the operating life and certification of EVA hardware, to secure the capability to launch EVA hardware safely on alternate launch vehicles, to protect for EMU hardware operability on-orbit, and to determine the source of high water purity to support recharge of PLSSs (no longer available via Shuttle). EVA 2010 Project includes the following tasks: the development of a launch fixture that would allow the EMU Portable Life Support System (PLSS) to be launched on-board alternate vehicles; extension of the EMU hardware maintenance interval from 3 years (current certification) to a minimum of 6 years (to extend to 2015); testing of recycled ISS Water Processor Assembly (WPA) water for use in the EMU cooling system in lieu of water resupplied by International Partner (IP) vehicles; development of techniques to remove & replace critical components in the PLSS on-orbit (not routine); extension of on-orbit certification of EVA tools; and development of an EVA hardware logistical plan to support the ISS without the Space Shuttle. Assumptions for the EVA 2010 Project included no more than 8 EVAs per year for ISS EVA operations in the Post-Shuttle environment and limited availability of cargo upmass on IP launch vehicles. From 2010 forward, EVA operations on-board the ISS without the Space Shuttle will be a paradigm shift in safely operating EVA hardware on orbit and the EVA 2010 effort was initiated to accommodate this significant change in EVA evolutionary history. 1

West, William↗

Shock-Driving CMEs Near the Sun, in the Interplanetary Medium, and Near Earth

The excellent correspondence between type II radio bursts and solar energetic particles (SEPs) made it clear that the same shock accelerates ions and electrons. A recent investigation involving a large number of I shocks revealed that about 35% of IP shocks do not produce type II bursts (radio quiet) or SEPs. Comparing the RQ shocks with the radio loud (RL) ones revealed some interesting results, which will be summarized in this poster. (1) There is no evidence for blast waves. (2) Even a small fraction (20%) of RQ shocks is associated with ion enhancements at the shock when the shock passes the spacecraft. (3) The primary difference between the RQ and RL shocks can be traced to the different kinematic properties of the associated CMEs, although the shock properties measured at 1 AU are not too different for the RQ and RL cases. This can be attributed to the interaction with the IP medium, which seems to erase the difference. More details can be found in Astrophysical Journal 710, 1111, 2010 (http://adsabs.harvard.edu/absZ2009arXivO9l2.4719G).

Gopalswamy, N.↗

Proposal for Ground Safety Review Coordination at ISS Launch Sites

As the transportation of ISS payloads and cargo shifts from KSC to other launch sites, close coordination of ground safety review processes would be of benefit to all parties. The benefit would have the launch sites receiving consistent data that would require less effort to review while still meeting their needs. Until recently, ground safety focus for the ISS program has been almost exclusively for prelaunch processing at KSC/post-landing processing at KSC/DFRC Each launch site, used by the ISS Program, has a ground safety review process. Ground safety viewed as local prerogative. Up till now, ground processing has consisted of low risk/low hazard items; but this will not always be the case. Recent coordination issues associated with the ground safety review of ORU's to be processed at Tanegashima for HTV-2, illustrate that IP ground safety review processes are not well understood by the ISS community at large. Confusion for data providers (US only?). Lack of internal review process for data being submitted to launch sites can lead to inconsistent submittals. NCRs/HRs. Majority of IP ground safety requirements are based upon old KHB 1700.7 (now KNPR 8715.3, Chapter 20). Proposals include: Establish a ground safety working group as part of the MS&MAP. Search for efficiencies in requirements and data submittal processes. Document processes in NSTS 13830/SSP 30599. Each launch site report out its payload ground safety status at the F2F (Monthly's as required). Completions/due dates/NCRs/issues/changes. Establish internal processes for review of ground safety submittals.

Kirkpatrick, Paul D.↗

Implementation of Joint Multi-Segment Training

The highest level of training for ISS flight is Joint Multi-Segment Training (JMST) simulations. These simulations allow two or more partners to conduct multi-segment training for their respective Mission Control Centers (MCC), include actual crew members, and usually include training facilities in each of the participating International Partner (IP) locations. It is the dress rehearsal for those events that exercise the interface between different IP modules and/or the decision making process between the different MCCs involved. This presentation will describe the challenge of successfully implementing JMST. It will start with a brief overview of who is involved, where they are located, and when JMSTs are required. Finally, it will illustrate many of the complications involved in just running a JMST between MCC-M and MCC-H. The viewer will leave with a much better appreciation for the complexities involved in successfully conducting a JMST of this nature, as well as an idea of how the picture will change as the other partners and payloads become involved.

Reagan, Marc↗

Astronaut Medical Selection and Flight Medicine Care During the Shuttle ERA 1981 to 2011

The NASA Shuttle Program began with congressional budget approval in January 5, 1972 and the launch of STS-1 on April 12, 1981 and recently concluded with the landing of STS-135 on July 21, 2011. The evolution of the medical standards and care of the Shuttle Era Astronauts began in 1959 with the first Astronaut selection. The first set of NASA minimal medical standards were documented in 1977 and based on Air Force, Navy, Department of Defense, and the Federal Aviation Administration standards. Many milestones were achieved over the 30 years from 1977 to 2007 and the subsequent 13 Astronaut selections and 4 major expert panel reviews performed by the NASA Flight Medicine Clinic, Aerospace Medicine Board, and Medical Policy Board. These milestones of aerospace medicine standards, evaluations, and clinical care encompassed the disciplines of preventive, occupational, and primary care medicine and will be presented. The screening and retention standards, testing, and specialist evaluations evolved through periodic expert reviews, evidence based medicine, and Astronaut medical care experience. The last decade of the Shuttle Program saw the development of the International Space Station (ISS) with further Space medicine collaboration and knowledge gained from our International Partners (IP) from Russia, Canada, Japan, and the European Space Agencies. The Shuttle Program contribution to the development and implementation of NASA and IP standards and waiver guide documents, longitudinal data collection, and occupational surveillance models will be presented along with lessons learned and recommendations for future vehicles and missions.

Johnston, S.↗

Tools for Administration of a UNIX-Based Network

Several computer programs have been developed to enable efficient administration of a large, heterogeneous, UNIX-based computing and communication network that includes a variety of computers connected to a variety of subnetworks. One program provides secure software tools for administrators to create, modify, lock, and delete accounts of specific users. This program also provides tools for users to change their UNIX passwords and log-in shells. These tools check for errors. Another program comprises a client and a server component that, together, provide a secure mechanism to create, modify, and query quota levels on a network file system (NFS) mounted by use of the VERITAS File SystemJ software. The client software resides on an internal secure computer with a secure Web interface; one can gain access to the client software from any authorized computer capable of running web-browser software. The server software resides on a UNIX computer configured with the VERITAS software system. Directories where VERITAS quotas are applied are NFS-mounted. Another program is a Web-based, client/server Internet Protocol (IP) address tool that facilitates maintenance lookup of information about IP addresses for a network of computers.

LeClaire, Stephen↗

CCSDS Advanced Orbiting Systems Virtual Channel Access Service for QoS MACHETE Model

To support various communications requirements imposed by different missions, interplanetary communication protocols need to be designed, validated, and evaluated carefully. Multimission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE), described in "Simulator of Space Communication Networks" (NPO-41373), NASA Tech Briefs, Vol. 29, No. 8 (August 2005), p. 44, combines various tools for simulation and performance analysis of space networks. The MACHETE environment supports orbital analysis, link budget analysis, communications network simulations, and hardware-in-the-loop testing. By building abstract behavioral models of network protocols, one can validate performance after identifying the appropriate metrics of interest. The innovators have extended the MACHETE model library to include a generic link-layer Virtual Channel (VC) model supporting quality-of-service (QoS) controls based on IP streams. The main purpose of this generic Virtual Channel model addition was to interface fine-grain flow-based QoS (quality of service) between the network and MAC layers of the QualNet simulator, a commercial component of MACHETE. This software model adds the capability of mapping IP streams, based on header fields, to virtual channel numbers, allowing extended QoS handling at link layer. This feature further refines the QoS v existing at the network layer. QoS at the network layer (e.g. diffserv) supports few QoS classes, so data from one class will be aggregated together; differentiating between flows internal to a class/priority is not supported. By adding QoS classification capability between network and MAC layers through VC, one maps multiple VCs onto the same physical link. Users then specify different VC weights, and different queuing and scheduling policies at the link layer. This VC model supports system performance analysis of various virtual channel link-layer QoS queuing schemes independent of the network-layer QoS systems.

Jennings, Esther H.↗

Ascent/Descent Software

The Ascent/Descent Software Suite has been used to support a variety of NASA Shuttle Program mission planning and analysis activities, such as range safety, on the Integrated Planning System (IPS) platform. The Ascent/Descent Software Suite, containing Ascent Flight Design (ASC)/Descent Flight Design (DESC) Configuration items (Cis), lifecycle documents, and data files used for shuttle ascent and entry modeling analysis and mission design, resides on IPS/Linux workstations. A list of tools in Navigation (NAV)/Prop Software Suite represents tool versions established during or after the IPS Equipment Rehost-3 project.

Brown, Charles↗

An Offload NIC for NASA, NLR, and Grid Computing

This work addresses distributed data management and access dynamically configurable high-speed access to data distributed and shared over wide-area high-speed network environments. An offload engine NIC (network interface card) is proposed that scales at nX10-Gbps increments through 100-Gbps full duplex. The Globus de facto standard was used in projects requiring secure, robust, high-speed bulk data transport. Novel extension mechanisms were derived that will combine these technologies for use by GridFTP, bandwidth management resources, and host CPU (central processing unit) acceleration. The result will be wire-rate encrypted Globus grid data transactions through offload for splintering, encryption, and compression. As the need for greater network bandwidth increases, there is an inherent need for faster CPUs. The best way to accelerate CPUs is through a network acceleration engine. Grid computing data transfers for the Globus tool set did not have wire-rate encryption or compression. Existing technology cannot keep pace with the greater bandwidths of backplane and network connections. Present offload engines with ports to Ethernet are 32 to 40 Gbps f-d at best. The best of ultra-high-speed offload engines use expensive ASICs (application specific integrated circuits) or NPUs (network processing units). The present state of the art also includes bonding and the use of multiple NICs that are also in the planning stages for future portability to ASICs and software to accommodate data rates at 100 Gbps. The remaining industry solutions are for carrier-grade equipment manufacturers, with costly line cards having multiples of 10-Gbps ports, or 100-Gbps ports such as CFP modules that interface to costly ASICs and related circuitry. All of the existing solutions vary in configuration based on requirements of the host, motherboard, or carriergrade equipment. The purpose of the innovation is to eliminate data bottlenecks within cluster, grid, and cloud computing systems, and to add several more capabilities while reducing space consumption and cost. Provisions were designed for interoperability with systems used in the NASA HEC (High-End Computing) program. The new acceleration engine consists of state-ofthe- art FPGA (field-programmable gate array) core IP, C, and Verilog code; novel communication protocol; and extensions to the Globus structure. The engine provides the functions of network acceleration, encryption, compression, packet-ordering, and security added to Globus grid or for cloud data transfer. This system is scalable in nX10-Gbps increments through 100-Gbps f-d. It can be interfaced to industry-standard system-side or network-side devices or core IP in increments of 10 GigE, scaling to provide IEEE 40/100 GigE compliance.

Awrach, James↗

A Comparison of Three Algorithms for Orion Drogue Parachute Release

The Orion Multi-Purpose Crew Vehicle is susceptible to ipping apex forward between drogue parachute release and main parachute in ation. A smart drogue release algorithm is required to select a drogue release condition that will not result in an apex forward main parachute deployment. The baseline algorithm is simple and elegant, but does not perform as well as desired in drogue failure cases. A simple modi cation to the baseline algorithm can improve performance, but can also sometimes fail to identify a good release condition. A new algorithm employing simpli ed rotational dynamics and a numeric predictor to minimize a rotational energy metric is proposed. A Monte Carlo analysis of a drogue failure scenario is used to compare the performance of the algorithms. The numeric predictor prevents more of the cases from ipping apex forward, and also results in an improvement in the capsule attitude at main bag extraction. The sensitivity of the numeric predictor to aerodynamic dispersions, errors in the navigated state, and execution rate is investigated, showing little degradation in performance.

Matz, Daniel A.↗