Search NASA⌕ Search

Engineering topics

Hooke, A. J.

Publications and source records attributed to Hooke, A. J..

At least 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Towards an interplanetary internet: a proposed strategy for standardization

This paper reviews the current set of standard data communications capabilities that exist to support advanced missions, discusses the architectural concepts for the future Interplanetary Internet, and suggests how a standardized set of space communications protocols that can grow to support future scenarios where human intelligence is widely distributed across the Solar System.

interplanetary internet space communications proto↗
NASA NTRS2000

The interplanetary Internet

Architectural design of the interplanetary internet is now underway and prototype flight testing of some of the candidate protocols is anticipated within a year. This talk will describe the current status of the project.

Internet space communications↗
NASA NTRS2000

Low-Cost Approaches to Deep Space Missions

The past decade has brought about a radical transformation in NASA's planetary exploration program. At the beginning of this decade, NASA was focused on the Cassini mission to Saturn. Following on the heels of the successful Voyager and Galileo missions, Cassini represents the culmination of an evolution towards successively larger, more complex, and more expensive spacecraft. The Cassini spacecraft weighs in at over 5 metric tons, and carries an entry probe and a sophisticated suite of sensors supporting 27 different science investigations enabling a comprehensive scientific investigation of Saturn with a single spacecraft. The cost of this spacecraft exceeded $2B, including the cost of the large Titan IV launch vehicle. During Cassini development, NASA realized that it could no longer afford these "flagship" missions, and the agency moved aggressively towards a "faster, better, cheaper" design philosophy of focused science goals and simpler, rapidly-developed spacecraft, allowing much more frequent launches of smaller, lower-cost missions. The Mars Global Surveyor, launched in November 1996, is an example of this new paradigm. Developed in less than 3-years, MGS is only one-fifth the mass of Cassini, and only cost on the order of $220M. The reduced spacecraft mass allows use of the smaller, lower cost Delta launch vehicle. Currently in orbit about Mars, MGS carries a focused suite of six science instruments that are currently returning high-resolution remote sensing of the Martian surface. The future calls for continued even more aggressive mass and cost targets. Examples of these next-generation goals are embodied in the Mars Micromission spacecraft concept, targeted for launch in 2003. With a mass of only 200kg, this lightweight bus can be tailored to carry a variety of payloads to Mars or other inner-planet destinations. The design of the Micromission spacecraft enable them to be launched at extremely low cost as a secondary "piggyback" payload.

Squibb, G. F.↗
NASA NTRS1995

The Next Generation of Space Telemetry and Telecommand Standards

New standards for space/ground communications protocols are suggested for the following areas: a) file transfer based on the Internet, b) transport based on the Internet TCP/UDP, c) security derived from the ISO NLSP, a new space network, and a new space data link.

spacecraft communications telemetry standards tele↗
NASA NTRS1986

Standard data systems architecture for the Space Station

Attention is given to an end-to-end Space Station Data System (SSDS) architecture which is based on internationally-recommended standards developed by the Consultative Committee for Space Data Systems (CCSDS). The proposed system uses simple modular building blocks that are recursively replicated and linked to construct essentially any desired data system configuration. The SSDS concept provides for a user-transparent data transport system which is entirely independent of the characteristics of the user data being transported, and in addition, has the flexibility to accommodate mission-induced changes in data traffic. SSDS physical elements include the following: (1) on-orbit local area networks, (2) space-to-ground, ground-to-space, and space-to-space data links, and (3) ground mission support facilities containing telemetry and telecommand data handling termini and preprocessing services.

Greenberg, E.↗
NASA NTRS1985

Packet Telemetry and Packet Telecommand

Two communication protocols for telemetry and telecommand reduce amount of required hardware and software and facilitate bidirectional information exchange.

Hooke, A. J.↗
NASA NTRS1983

Packet telemetry and packet telecommand - The new generation of spacecraft data handling techniques

Because of rising costs and reduced reliability of spacecraft and ground network hardware and software customization, standardization Packet Telemetry and Packet Telecommand concepts are emerging as viable alternatives. Autonomous packets of data, within each concept, which are created within ground and space application processes through the use of formatting techniques, are switched end-to-end through the space data network to their destination application processes through the use of standard transfer protocols. This process may result in facilitating a high degree of automation and interoperability because of completely mission-independent-designed intermediate data networks. The adoption of an international guideline for future space telemetry formatting of the Packet Telemetry concept, and the advancement of the NASA-ESA Working Group's Packet Telecommand concept to a level of maturity parallel to the of Packet Telemetry are the goals of the Consultative Committee for Space Data Systems. Both the Packet Telemetry and Packet Telecommand concepts are reviewed.

Hooke, A. J.↗
NASA NTRS1980

Efficient telemetry format

Format would simplify ground processing of telemetry data. Also, missing minor frame would create error in only one set of source data instead of disrupting all sets. Format organizes data from various sources into autonomous blocks. Data are pre-processed, in effect, so main computer only needs to determine block type and process data set as batch.

Greenberg, E.↗