Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Communication architecture”

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 541 records · Page 30

Space Station communications and tracking system

A comprehensive description of the existing Space Station communications and tracking system requirements, architecture, and design concepts is provided. Areas which will require innovative solutions to provide cost-effective flight systems are emphasized. Among these are the space-to-space links, the differential global positioning system for determining relative position with free-flying vehicles, multitarget radar, packet/isochronous signal processing, and laser docking systems. In addition, the importance of advanced development, tests, and analyses is summarized.

Dietz, Reinhold H.↗

Ada/POSIX binding: A focused Ada investigation

NASA is seeking an operating system interface definition (OSID) for the Space Station Program (SSP) in order to take advantage of the commercial off-the-shelf (COTS) products available today and the many that are expected in the future. NASA would also like to avoid the reliance on any one source for operating systems, information system, communication system, or instruction set architecture. The use of the Portable Operating System Interface for Computer Environments (POSIX) is examined as a possible solution to this problem. Since Ada is already the language of choice for SSP, the question of an Ada/POSIX binding is addressed. The intent of the binding is to provide access to the POSIX standard operation system (OS) interface and environment, by which application portability of Ada applications will be supported at the source code level. A guiding principle of Ada/POSIX binding development is a clear conformance of the Ada interface with the functional definition of POSIX. The interface is intended to be used by both application developers and system implementors. The objective is to provide a standard that allows a strictly conforming application source program that can be compiled to execute on any conforming implementation. Special emphasis is placed on first providing those functions and facilities that are needed in a wide variety of commercial applications

Legrand, Sue↗

A study of System Interface Sets (SIS) for the host, target and integration environments of the Space Station Program (SSP)

System interface sets (SIS) for large, complex, non-stop, distributed systems are examined. The SIS of the Space Station Program (SSP) was selected as the focus of this study because an appropriate virtual interface specification of the SIS is believed to have the most potential to free the project from four life cycle tyrannies which are rooted in a dependance on either a proprietary or particular instance of: operating systems, data management systems, communications systems, and instruction set architectures. The static perspective of the common Ada programming support environment interface set (CAIS) and the portable common execution environment (PCEE) activities are discussed. Also, the dynamic perspective of the PCEE is addressed.

Mckay, Charles↗

Abnormal fault-recovery characteristics of the fault-tolerant multiprocessor uncovered using a new fault-injection methodology

An investigation was made in AIRLAB of the fault handling performance of the Fault Tolerant MultiProcessor (FTMP). Fault handling errors detected during fault injection experiments were characterized. In these fault injection experiments, the FTMP disabled a working unit instead of the faulted unit once in every 500 faults, on the average. System design weaknesses allow active faults to exercise a part of the fault management software that handles Byzantine or lying faults. Byzantine faults behave such that the faulted unit points to a working unit as the source of errors. The design's problems involve: (1) the design and interface between the simplex error detection hardware and the error processing software, (2) the functional capabilities of the FTMP system bus, and (3) the communication requirements of a multiprocessor architecture. These weak areas in the FTMP's design increase the probability that, for any hardware fault, a good line replacement unit (LRU) is mistakenly disabled by the fault management software.

Padilla, Peter A.↗

Hypermedia as medium

Claims and rebuttals that hypermedia (the associative, nonlinear interconnection of multimedia materials) is a fundamentally innovative means of thinking and communicating are described. This representational architecture has many advantages that make it a major advance over other media; however, it also has several intrinsic problems that severly limits its effectiveness as a medium. These advantages and limits in applications are discussed.

Dede, Christopher J.↗

Performance of a Ka-band transponder breadboard for deep-space applications

This article summarizes the design concepts applied in the development of and advanced Ka-band (34.4 GHz/32 GHz) transponder breadboard for the next generation of space communications systems applications. The selected architecture upgrades the X-band (7.2 GHz/8.4 GHz) deep-space transponder (DST) to provide Da-band up/Ka- and X-band down capability. The Ka-band transponder breadboard incorporates several state-of-the-art components, including sampling mixers, a Ka-band dielectric resonator oscillator, and microwave monolithic integrated circuits (MMICs). The MMICs that were tested in the breadboard include upconverters, downconverters, automatic gain control circuits, mixers, phase modulators, and amplifiers. The measured receiver dynamic range, tracking range, acquisition rate, static phase error, and phase jitter characteristics of the Ka-band breadboard interfaced to the advanced engineering model X-band DST are in good agreement with the expected performance. The results show a receiver tracking threshold of -149 dBm with a dynamic range of 80 dB and a downlink phase jitter of 7 deg rms. The analytical results of phase noise and Allan standard deviation are in good agreement with the experimental results.

Mysoor, N. R.↗

Structural Health Management for Future Aerospace Vehicles

Structural Health Management (SHM) will be of critical importance to provide the safety, reliability and affordability necessary for the future long duration space missions described in America's Vision for Space Exploration. Long duration missions to the Moon, Mars and beyond cannot be accomplished with the current paradigm of periodic, ground based structural integrity inspections. As evidenced by the Columbia tragedy, this approach is also inadequate for the current Shuttle fleet, thus leading to its initial implementation of on-board SHM sensing for impact detection as part of the return to flight effort. However, future space systems, to include both vehicles as well as structures such as habitation modules, will require an integrated array of onboard in-situ sensing systems. In addition, advanced data systems architectures will be necessary to communicate, store and process massive amounts of SHM data from large numbers of diverse sensors. Further, improved structural analysis and design algorithms will be necessary to incorporate SHM sensing into the design and construction of aerospace structures, as well as to fully utilize these sensing systems to provide both diagnosis and prognosis of structural integrity. Ultimately, structural integrity information will feed into an Integrated Vehicle Health Management (IVHM) system that will provide real-time knowledge of structural, propulsion, thermal protection and other critical systems for optimal vehicle management and mission control. This paper will provide an overview of NASA research and development in the area of SHM as well as to highlight areas of technology improvement necessary to meet these future mission requirements.

Prosser, W. H.↗

Spinoff 2009

Topics covered include: Image-Capture Devices Extend Medicine's Reach; Medical Devices Assess, Treat Balance Disorders; NASA Bioreactors Advance Disease Treatments; Robotics Algorithms Provide Nutritional Guidelines; "Anti-Gravity" Treadmills Speed Rehabilitation; Crew Management Processes Revitalize Patient Care; Hubble Systems Optimize Hospital Schedules; Web-based Programs Assess Cognitive Fitness; Electrolyte Concentrates Treat Dehydration; Tools Lighten Designs, Maintain Structural Integrity; Insulating Foams Save Money, Increase Safety; Polyimide Resins Resist Extreme Temperatures; Sensors Locate Radio Interference; Surface Operations Systems Improve Airport Efficiency; Nontoxic Resins Advance Aerospace Manufacturing; Sensors Provide Early Warning of Biological Threats; Robot Saves Soldier's Lives Overseas (MarcBot); Apollo-Era Life Raft Saves Hundreds of Sailors; Circuits Enhance Scientific Instruments and Safety Devices; Tough Textiles Protect Payloads and Public Safety Officers; Forecasting Tools Point to Fishing Hotspots; Air Purifiers Eliminate Pathogens, Preserve Food; Fabrics Protect Sensitive Skin from UV Rays; Phase Change Fabrics Control Temperature; Tiny Devices Project Sharp, Colorful Images; Star-Mapping Tools Enable Tracking of Endangered Animals; Nanofiber Filters Eliminate Contaminants; Modeling Innovations Advance Wind Energy Industry; Thermal Insulation Strips Conserve Energy; Satellite Respondent Buoys Identify Ocean Debris; Mobile Instruments Measure Atmospheric Pollutants; Cloud Imagers Offer New Details on Earth's Health; Antennas Lower Cost of Satellite Access; Feature Detection Systems Enhance Satellite Imagery; Chlorophyll Meters Aid Plant Nutrient Management; Telemetry Boards Interpret Rocket, Airplane Engine Data; Programs Automate Complex Operations Monitoring; Software Tools Streamline Project Management; Modeling Languages Refine Vehicle Design; Radio Relays Improve Wireless Products; Advanced Sensors Boost Optical Communication, Imaging; Tensile Fabrics Enhance Architecture Around the World; Robust Light Filters Support Powerful Imaging Devices; Thermoelectric Devices Cool, Power Electronics; Innovative Tools Advance Revolutionary Weld Technique; Methods Reduce Cost, Enhance Quality of Nanotubes; Gauging Systems Monitor Cryogenic Liquids; Voltage Sensors Monitor Harmful Static; and Compact Instruments Measure Heat Potential.

Source record↗

Adaptation of the Electra Radio to Support Multiple Receive Channels

Proposed future Mars missions plan communication between multiple assets (rovers). This paper presents the results of a study carried out to assess the potential adaptation of the Electra radio to a multi-channel transceiver. The basic concept is a Frequency Division multiplexing (FDM) communications scheme wherein different receiver architectures are examined. Options considered include: (1) multiple IF slices, A/D and FPGAs each programmed with an Electra baseband modem; (2) common IF but multiple A/Ds and FPGAs and (3) common IF, single A/D and single or multiple FPGAs programmed to accommodate the FDM signals. These options represent the usual tradeoff between analog and digital complexity. Given the space application, a common IF is preferable; however, multiple users present dynamic range challenges (e.g., near-far constraints) that would favor multiple IF slices (Option 1). Vice versa, with a common IF and multiple A/Ds (Option 2), individual AGC control of the A/Ds would be an important consideration. Option 3 would require a common AGC control strategy and would entail multiple digital down conversion paths within the FPGA. In this paper, both FDM parameters as well as the different Electra design options will be examined. In particular, signal channel spacing as a function of user data rates and transmit powers will be evaluated. In addition, tradeoffs between the different Electra design options will be presented with the ultimate goal of defining an augmented Electra radio architecture for potential future missions.

Time Division multiplexing↗

On-board communication for active-control transport aircraft

An investigation of active control communications sponsored by the NASA Langley Research Center is summarized. Particular attention is given to comparative architectures, for which a common set of requirements is generated as a baseline. Most of the requirements are aircraft functional in nature, such as stability and command augmentation, structural load relief, flight path control, flight control linkage, flight monitoring, management, navigation, engine control, and ground communication; the time element, the hazard environment, and the communications capacity estimation are also important factors. The architectures involve several communication technologies, including dedicated links, broadcast busing, and multiplex busing. The multiplex bus system provides the greatest flexibility and installation efficiency. A future homogeneous network system is also proposed, which would be fault and damage tolerant and would, with advanced technology, avoid the problems of designing a very large and flight critical multiplex bus system.

Brock, L. D.↗

Communication Network Awareness Machine System Phase I Development: The Intelligent Party-Line Schema

As NextGen continues toward the full implementation of a Net-Centric Architecture (N-CA)it will inherently provide a continuous increase to the Three-Vs components (Volume, Velocity, and Variety) of big data . This will create an insurmountable environment for direct-action aviation personnel (DAAP)as the DAAP’s natural abilities to manage and process data into actionable information will be overmatched by the Three-Vs. Therefore, conducting operations within a N-CA requires that new tools and applications be researched and developed to aid the DAAP’s ability to understand and manage data, mitigate non-normals, create contingency plans and actions. This paper will describe a research area at NASA Langley Research Center known as the Intelligent Party-Line (IPL).

Intelligent Party-Line↗

Mission science value-cost savings from the Advanced Imaging Communication System (AICS)

An Advanced Imaging Communication System (AICS) was proposed in the mid-1970s as an alternative to the Voyager data/communication system architecture. The AICS achieved virtually error free communication with little loss in the downlink data rate by concatenating a powerful Reed-Solomon block code with the Voyager convolutionally coded, Viterbi decoded downlink channel. The clean channel allowed AICS sophisticated adaptive data compression techniques. Both Voyager and the Galileo mission have implemented AICS components, and the concatenated channel itself is heading for international standardization. An analysis that assigns a dollar value/cost savings to AICS mission performance gains is presented. A conservative value or savings of $3 million for Voyager, $4.5 million for Galileo, and as much as $7 to 9.5 million per mission for future projects such as the proposed Mariner Mar 2 series is shown.

Rice, R. F.↗

Concept of Operations for a Prospective "Proving Ground" in the Lunar Vicinity

NASA is studying conceptual architectures for a "Proving Ground" near the Moon or in high lunar orbit to conduct human space exploration missions that bridge the gap between today's operations with the International Space Station (ISS) and future human exploration of Mars beginning in the 2030s. This paper describes the framework of a concept of operations ("Conops") for candidate activities in the Proving Ground. The Conops discusses broad goals that the Proving Ground might address, such as participation from commercial entities, support for human landings on the Moon, use of mature technologies, and growth of capability through a steady cadence of increasingly ambitious piloted missions. Additional Proving Ground objectives are outlined in a companion paper. Key elements in the Conops include the Orion spacecraft (with mission kits for docking and other specialized operations) and the Space Launch System (SLS) heavy-lift rocket. Potential additions include a new space suit, commercial launch vehicles and logistics carriers, Solar Electric Propulsion (SEP) stages to move elements between different orbits and eventually take them on excursions to deep space, a core module with multiple docking ports, a habitation block, and robotic and piloted lunar landers. The landers might include reusable ascent modules which could remain docked to in-space elements between lunar sorties. A module providing advanced regenerative life support functions could launch to the ISS, and later move to the Proving Ground. The architecture will include infrastructure for launch preparation, communication, mission control, and range safety. The Conops describes notional missions chosen to guide the design of the architecture and its elements. One such mission might be the delivery of a approximately 10-t Transit Habitat element, comanifested with Orion on a Block 1B SLS launcher, to the Proving Ground. In another mission, the architecture might participate in direct human exploration of an asteroidal boulder brought to high lunar orbit by the Asteroid Redirect Mission. The Proving Ground stack could serve as a staging point and tele-operation center for robotic and piloted Moon landings. With the addition of a SEP stage, the architecture could support months-long excursions within and beyond the Earth's sphere of influence, possibly culminating in a year-long mission to land humans on a near-Earth asteroid. In the last case, after returning to near-lunar space, two of the asteroid explorers could join two crewmembers freshly arrived from Earth for a Moon landing, helping to quantify the risk of landing deconditioned crews on Mars. In a conceptual mission particularly stressing to system design, Proving Ground elements could transit to Mars orbit. Other possible design-driving operations include relocation of the stack with no crew on board, the unpiloted journey of the advanced life support module from ISS to the lunar vicinity, excursions to other destinations in near-Earth space, and additional support for Mars exploration in conjunction with the Evolvable Mars Campaign. The Proving Ground Conops concludes with a discussion of aborts and contingency operations

Love, Stanley G.↗

Generalized hypercube structures and hyperswitch communication network

This paper discusses an ongoing study that uses a recent development in communication control technology to implement hybrid hypercube structures. These architectures are similar to binary hypercubes, but they also provide added connectivity between the processors. This added connectivity increases communication reliability while decreasing the latency of interprocessor message passing. Because these factors directly determine the speed that can be obtained by multiprocessor systems, these architectures are attractive for applications such as remote exploration and experimentation, where high performance and ultrareliability are required. This paper describes and enumerates these architectures and discusses how they can be implemented with a modified version of the hyperswitch communication network (HCN). The HCN is analyzed because it has three attractive features that enable these architectures to be effective: speed, fault tolerance, and the ability to pass multiple messages simultaneously through the same hyperswitch controller.

Young, Steven D.↗

Re-engineering Nascom's network management architecture

The development of Nascom systems for ground communications began in 1958 with Project Vanguard. The low-speed systems (rates less than 9.6 Kbs) were developed following existing standards; but, there were no comparable standards for high-speed systems. As a result, these systems were developed using custom protocols and custom hardware. Technology has made enormous strides since the ground support systems were implemented. Standards for computer equipment, software, and high-speed communications exist and the performance of current workstations exceeds that of the mainframes used in the development of the ground systems. Nascom is in the process of upgrading its ground support systems and providing additional services. The Message Switching System (MSS), Communications Address Processor (CAP), and Multiplexer/Demultiplexer (MDM) Automated Control System (MACS) are all examples of Nascom systems developed using standards such as, X-windows, Motif, and Simple Network Management Protocol (SNMP). Also, the Earth Observing System (EOS) Communications (Ecom) project is stressing standards as an integral part of its network. The move towards standards has produced a reduction in development, maintenance, and interoperability costs, while providing operational quality improvement. The Facility and Resource Manager (FARM) project has been established to integrate the Nascom networks and systems into a common network management architecture. The maximization of standards and implementation of computer automation in the architecture will lead to continued cost reductions and increased operational efficiency. The first step has been to derive overall Nascom requirements and identify the functionality common to all the current management systems. The identification of these common functions will enable the reuse of processes in the management architecture and promote increased use of automation throughout the Nascom network. The MSS, CAP, MACS, and Ecom projects have indicated the potential value of commercial-off-the-shelf (COTS) and standards through reduced cost and high quality. The FARM will allow the application of the lessons learned from these projects to all future Nascom systems.

Drake, Brian C.↗

INCO shuttle communication system

In a previous work we have defined a general architectural model for autonomous systems, which can be mapped easily to describe the functions of any automated system (SDAG-86-01). In this note, we use the model to describe the Shuttle communication system. First we briefly review the architecture, then we present the environment of our application, and finally we detail the specific function for each functional block of the architecture for that environment.

Dikshit, Piyush↗

Prototyping Operational Autonomy for Space Traffic Management

Current state of the art in Space Traffic Management (STM) relies on a handful of providers for surveillance and collision prediction, and manual coordination between operators. Neither is scalable to support the expected 10x increase in spacecraft population in less than 10 years, nor does it support automated manuever planning. We present a software prototype of an STM architecture based on open Application Programming Interfaces (APIs), drawing on previous work by NASA to develop an architecture for low-altitude Unmanned Aerial System Traffic Management. The STM architecture is designed to provide structure to the interactions between spacecraft operators, various regulatory bodies, and service suppliers, while maintaining flexibility of these interactions and the ability for new market participants to enter easily. Autonomy is an indispensable part of the proposed architecture in enabling efficient data sharing, coordination between STM participants and safe flight operations. Examples of autonomy within STM include syncing multiple non-authoritative catalogs of resident space objects, or determining which spacecraft maneuvers when preventing impending conjunctions between multiple spacecraft. The STM prototype is based on modern micro-service architecture adhering to OpenAPI standards and deployed in industry standard Docker containers, facilitating easy communication between different participants or services. The system architecture is designed to facilitate adding and replacing services with minimal disruption. We have implemented some example participant services (e.g. a space situational awareness provider/SSA, a conjunction assessment supplier/CAS, an automated maneuver advisor/AMA) within the prototype. Different services, with creative algorithms folded into then, can fulfil similar functional roles within the STM architecture by flexibly connecting to it using pre-defined APIs and data models, thereby lowering the barrier to entry of new players in the STM marketplace. We demonstrate the STM prototype on a multiple conjunction scenario with multiple maneuverable spacecraft, where an example CAS and AMA can recommend optimal maneuvers to the spacecraft operators, based on a predefined reward function. Such tools can intelligently search the space of potential collision avoidance maneuvers with varying parameters like lead time and propellant usage, optimize a customized reward function, and be implemented as a scheduling service within the STM architecture. The case study shows an example of autonomous maneuver planning is possible using the API-based framework. As satellite populations and predicted conjunctions increase, an STM architecture can facilitate seamless information exchange related to collision prediction and mitigation among various service applications on different platforms and servers. The availability of such an STM network also opens up new research topics on satellite maneuver planning, scheduling and negotiation across disjoint entities.

space traffic management↗

Network-Attached Solid-State Recorder Architecture

A document discusses placing memory modules on the high-speed serial interconnect, which is used by a spacecraft s computer elements for inter-processor communications, to allow all multiple computer system architectures to access the spacecraft data storage at the same time. Each memory board is identical electrically and receives its bus ID upon connection to the system. The computer elements are configured in a similar fashion. The architecture allows for multiple memory boards to be accessed simultaneously by different computer elements, and results in a scalable, strong, fault-tolerant system. The IEEE-1393 ring bus can be routed so that multiple card failures can occur and the mass memory storage will still function.

Cox, Brian↗