SEARCH · Search NASA
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.
Network Operator Assistant (NOA) is a prototype expert system. NOA uses detailed scheduling knowledge and problem solving heuristics to assist Network Control Center operators schedule the NASA Space Network in time critical situations. The current status of NOA and its future directions is presented.
In 2004, NASA faced major knowledge sharing challenges due to geographically isolated field centers that inhibited engineers from sharing their experiences, expertise, ideas, and lessons learned. The necessity to collaborate on complex development projects and the reality of constrained project resources together drove the need for ensuring that personnel at all NASA centers had comparable skill sets and that engineers could find resources in a timely fashion. Mission failures and new directions for the Agency also demanded better collaborative tools for NASA's engineering workforce. In response to these needs, the online NASA Engineering Network (NEN) was formed by the NASA Office of the Chief Engineer to provide a multi-faceted system for overcoming geographic and cultural barriers. NEN integrates communities of practice with a cross-repository search and the Lessons Learned Information System. This paper describes the features of the GN&C engineering discipline CoP site which went live on NEN in May of 2008 as an online means of gathering input and guidance from practitioners. It allows GN&C discipline expertise captured at one field center to be shared in a collaborative way with the larger discipline CoP spread across the entire Agency. The site enables GN&C engineers to find the information they need quickly, to find solutions to questions from experienced engineers, and to connect with other practitioners regardless of geographic location, thus increasing the probability of project success.
A historical account is provided of NASA's Spaceflight Tracking and Data Network (STDN), starting with its formation in the late 1950s to what it is today in the first decade of the 21st century. It traces the roots of the tracking network from its beginnings at the White Sands Missile Range in New Mexico to the Tracking and Data Relay Satellite System space-based constellation of today. The story spans the early days of satellite tracking using the Minitrack Network, through the expansion of the Satellite Tracking and Data Acquisition Network and the Manned Space Flight Network, and finally, to the Space and Ground networks of today. These accounts tell how international goodwill and foreign cooperation were crucial to the operation of the network and why the space agency chose to build the STDN as it did.
The NASA Near Earth Network (NEN) consists of globally distributed tracking stations, including NASA, commercial, and partner ground stations, that are strategically located to maximize the coverage provided to a variety of orbital and suborbital missions, including those in LEO (Low Earth Orbit), GEO (Geosynchronous Earth Orbit), HEO (Highly Elliptical Orbit), lunar and L1-L2 orbits. The NEN's future mission set includes and will continue to include CubeSat missions. The first NEN-supported CubeSat mission will be the Cubesat Proximity Operations Demonstration (CPOD) launching into LEO in 2017. The majority of the CubeSat missions destined to fly on EM-1, launching in late 2018, many in a lunar orbit, will communicate with ground-based stations via X-band and will utilize the NASA Jet Propulsion Laboratory (JPL)-developed IRIS (Satellite Communication for Air Traffic Management) radio. The NEN recognizes the important role CubeSats are beginning to play in carrying out NASAs mission and is therefore investigating the modifications needed to provide IRIS radio compatibility. With modification, the NEN could potentially expand support to the EM-1 (Exploration Mission-1) lunar CubeSats. The NEN could begin providing significant coverage to lunar CubeSat missions utilizing three to four of the NEN's mid-latitude sites. This coverage would supplement coverage provided by the JPL Deep Space Network (DSN). The NEN, with smaller apertures than DSN, provides the benefit of a larger beamwidth that could be beneficial in the event of uncertain ephemeris data. In order to realize these benefits the NEN would need to upgrade stations targeted based on coverage ability and current configuration ease of upgrade, to ensure compatibility with the IRIS radio. In addition, the NEN is working with CubeSat radio developers to ensure NEN compatibility with alternative CubeSat radios for Lunar and L1-L2 CubeSats. The NEN has provided NEN compatibility requirements to several radio developers who are developing radios that offer lower cost and, in some cases, more capabilities with fewer constraints. The NEN is ready to begin supporting CubeSat missions. The NEN is considering network upgrades to broaden the types of CubeSat missions that can be supported and is supporting both the CubeSat community and radio developers to ensure future CubeSat missions have multiple options when choosing a network for their communications support.
The SmallSat has an unrealized potential in both the private industry and in the federal government. Currently over 70 companies, 50 universities and 17 governmental agencies are involved in SmallSat research and development. In 1994, the U.S. Army Missile and Defense mapped the moon using smallSat imagery. Since then Smart Phones have introduced this imagery to the people of the world as diverse industries watched this trend. The deployment cost of smallSats is also greatly reduced compared to traditional satellites due to the fact that multiple units can be deployed in a single mission. Imaging payloads have become more sophisticated, smaller and lighter. In addition, the growth of small technology obtained from private industries has led to the more widespread use of smallSats. This includes greater revisit rates in imagery, significantly lower costs, the ability to update technology more frequently and the ability to decrease vulnerability of enemy attacks. The popularity of smallSats show a changing mentality in this fast paced world of tomorrow. What impact has this created on the NASA communication networks now and in future years? In this project, we are developing the SmallSat Relational Database which can support a simulation of smallSats within the NASA SCaN Compatability Environment for Networks and Integrated Communications (SCENIC) Modeling and Simulation Lab. The NASA Space Communications and Networks (SCaN) Program can use this modeling to project required network support needs in the next 10 to 15 years. The SmallSat Rational Database could model smallSats just as the other SCaN databases model the more traditional larger satellites, with a few exceptions. One being that the smallSat Database is designed to be built-to-order. The SmallSat database holds various hardware configurations that can be used to model a smallSat. It will require significant effort to develop as the research material can only be populated by hand to obtain the unique data required. When completed it will interface with the SCENIC environment to allow modeling of smallSats. The SmallSat Relational Database can also be integrated with the SCENIC Simulation modeling system that is currently in development. The SmallSat Relational Database simulation will be of great significance in assisting the NASA SCaN group to understand the impact the smallSats have made which have populated the lower orbit around our mother earth. What I have created and worked on this summer session 2015, is the basis for a tool that will be of value to the NASA SCaN SCENIC Simulation Environment for years to come.
Performance evaluation of high speed digital data circuits in NASA communications network /NASCOM/
Given here is an overview analysis of the Father Christmas Worm, a computer worm that was released onto the DECnet Internet three days before Christmas 1988. The purpose behind the worm was to send an electronic mail message to all users on the computer system running the worm. The message was a Christmas greeting and was signed 'Father Christmas'. From the investigation, it was determined that the worm was released from a computer (node number 20597::) at a university in Switzerland. The worm was designed to travel quickly. Estimates are that it was copied to over 6,000 computer nodes. However, it was believed to have executed on only a fraction of those computers. Within ten minutes after it was released, the worm was detected at the Space Physics Analysis Network (SPAN), NASA's largest space and Earth science network. Once the source program was captured, a procedural cure, using the existing functionality of the computer operating systems, was quickly devised and distributed. A combination of existing computer security measures, the quick and accurate procedures devised to stop copies of the worm from executing, and the network itself, were used to rapidly provide the cure. These were the main reasons why the worm executed on such a small percentage of nodes. This overview of the analysis of the events concerning the worm is based on an investigation made by the SPAN Security Team and provides some insight into future security measures that will be taken to handle computer worms and viruses that may hit similar networks.
Historically, engineers at the National Aeronautics and Space Administration (NASA) had few opportunities or incentives to share their technical expertise across the Agency. Its center- and project- focused culture often meant that knowledge never left organizational and geographic boundaries. With increasingly complex missions, the closeout of the Shuttle Program, and a new generation entering the workforce, developing a knowledge sharing culture became critical. To address this need, the Office of the Chief Engineer established communities of practice on the NASA Engineering Network. These communities were strategically aligned with NASA's core competencies in such disciplines as avionics, flight mechanics, life support, propulsion, structures, loads and dynamics, human factors, and guidance, navigation, and control. This paper describes the process used to identify and develop communities, from establishing simple websites that compiled discipline-specific resources to fostering a knowledge-sharing environment through collaborative and interactive technologies. It includes qualitative evidence of improved availability and transfer of knowledge. It focuses on pivotal capabilities that increased knowledge exchange such as a custom-made Ask An Expert system, community contact lists, publication of key resources, and submission forms that allowed any user to propose content for the sites. It discusses the peer relationships that developed through the communities and the leadership and infrastructure that made them possible.
The Kappa Cygnid (KCG) meteor shower exhibited unusually high activity in 2014, producing ten times the typical number of meteors. The shower was detected in both radar and optical systems and meteoroids associated with the outburst spanned at least five decades in mass. In total, the Canadian Meteor Orbit Radar, European Network, and NASA All Sky and Southern Ontario Meteor Network produced thousands of KCG meteor trajectories. Using these data, we have undertaken a new and improved characterization of the dynamics of this little-studied, variable meteor shower. The Cygnids have a di use radiant and a significant spread in orbital characteristics, with multiple resonances appearing to play a role in the shower dynamics. We conducted a new search for parent bodies and found that several known asteroids are orbitally similar to the KCGs. N-body simulations show that the two best parent body candidates readily transfer meteoroids to the Earth in recent centuries, but neither produces an exact match to the KCG radiant, velocity, and solar longitude. We nevertheless identify asteroid 2001 MG1 as a promising parent body candidate.
The Office of Tracking and Data Acquisition (OTDA) and its two worldwide tracking network facilities, the Spaceflight Tracking and Data Network and the Deep Space Network, are described. Other topics discussed include the NASA communications network, the tracking and data relay satellite system, other OTDA tracking activities, and OTDA milestones.
Network Control Architecture for a 30/20 GHz flight experiment system operating in the Time Division Multiple Access (TDMA) was studied. Architecture development, identification of processing functions, and performance requirements for the Master Control Station (MCS), diversity trunking stations, and Customer Premises Service (CPS) stations are covered. Preliminary hardware and software processing requirements as well as budgetary cost estimates for the network control system are given. For the trunking system control, areas covered include on board SS-TDMA switch organization, frame structure, acquisition and synchronization, channel assignment, fade detection and adaptive power control, on board oscillator control, and terrestrial network timing. For the CPS control, they include on board processing and adaptive forward error correction control.
Explore the source record for details and available documents.
This paper describes the new architecture, implementation, and lessons learned in the Deep Space Network Simplification Project.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
This paper describes the current DSN automation system design, functions, test results, and actual field implementation experience.