DSN Operations Working Group
Explore the source record for details and available documents.
DSN operations working group↗
SEARCH · Search NASA
Results for “DSN operations working group”
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.
NASA deep space network operations planning and preparation
The responsibilities and structural organization of the Operations Planning Group of NASA Deep Space Network (DSN) Operations are outlined. The Operations Planning group establishes an early interface with a user's planning organization to educate the user on DSN capabilities and limitations for deep space tracking support. A team of one or two individuals works through all phases of the spacecraft launch and also provides planning and preparation for specific events such as planetary encounters. Coordinating interface is also provided for nonflight projects such as radio astronomy and VLBI experiments. The group is divided into a Long Range Support Planning element and a Near Term Operations Coordination element.
Jensen, W. N.↗
DSN Antenna Array Architectures Based on Future NASA Mission Needs
A flexible method of parametric, full life-cycle cost analysis has been combined with data on NASA's future communication needs to estimate the required number and operational dates of new antennas for the Deep Space Network (DSN). The requirements were derived from a subset of missions in the Integrated Mission Set database of NASA's Space Communications Architecture Working Group. Assuming that no new antennas are 'constructed', the simulation shows that the DSN is unlikely to meet more than 20% of mission requirements by 2030. Minimum full life-cycle costs result when antennas in the diameter range, 18m-34m, are constructed. Architectures using a mixture of antenna diameters produce a slightly lower full life-cycle cost.
array↗
A Multi-Center Space Data System Prototype Based on CCSDS Standards
Deep space missions beyond earth orbit will require new methods of data communications in order to compensate for increasing Radio Frequency (RF) propagation delay. The Consultative Committee for Space Data Systems (CCSDS) standard protocols Spacecraft Monitor & Control (SM&C), Asynchronous Message Service (AMS), and Delay/Disruption Tolerant Networking (DTN) provide such a method. However, the maturity level of this protocol stack is insufficient for mission inclusion at this time. This Space Data System prototype is intended to provide experience which will raise the Technical Readiness Level (TRL) of this protocol set. In order to reduce costs, future missions can take advantage of these standard protocols, which will result in increased interoperability between control centers. This prototype demonstrates these capabilities by implementing a realistic space data system in which telemetry is published to control center applications at the Jet Propulsion Lab (JPL), the Marshall Space Flight Center (MSFC), and the Johnson Space Center (JSC). Reverse publishing paths for commanding from each control center are also implemented. The target vehicle consists of realistic flight computer hardware running Core Flight Software (CFS) in the integrated Power, Avionics, and Power (iPAS) Pathfinder Lab at JSC. This prototype demonstrates a potential upgrade path for future Deep Space Network (DSN) modification, in which the automatic error recovery and communication gap compensation capabilities of DTN would be exploited. In addition, SM&C provides architectural flexibility by allowing new service providers and consumers to be added efficiently anywhere in the network using the common interface provided by SM&C's Message Abstraction Layer (MAL). In FY 2015, this space data system was enhanced by adding telerobotic operations capability provided by the Robot API Delegate (RAPID) family of protocols developed at NASA. RAPID is one of several candidates for consideration and inclusion in a new international standard being developed by the CCSDS Telerobotic Operations Working Group. Software gateways for the purpose of interfacing RAPID messages with the existing SM&C based infrastructure were developed. Telerobotic monitor, control, and bridge applications were written in the RAPID framework, which were then tailored to the NAO telerobotic test article hardware, a product of Aldebaran Robotics.
Rich, Thomas M.↗
HELIOS Third Joint Working Group Meeting
During the past six months since the Second Helios Joint Working Group Meeting held 27-30 April 1970 at Goddard Space Flight Center, the TDS Sub-Group supported the Helios Project Office and the other Sub-Groups in the timely disposition of action items and the dissemination of information pertinent to the development of interface documentation. Of particular importance during this time period was the Project's decision to incorporate a single-channel telemetry system design aboard the spacecraft. The TDS Sub-Group participated actively in the process that led to this decision. Still under active study with TDS participation is the pending Project Office decision regarding the incorporation of a ranging capability within the telecommunications design. The TDS Sub-Group assisted the Mission Analysis and Operations Sub-Group in establishment of a study effort concerning the Near-Earth Sequence of Events from launch to launch plus 8 hours. This study, which will provide valuable data for the spacecraft telecommunications design, will include participation by the Experiment, Launch Vehicle, Spacecraft, as well as the TDS and MA&O Sub-Groups. Also during the past 6-month period, the TDS, in conjunction with the Spacecraft Sub-Group, initiated activity to develop the Helios Spacecraft/TDS Compatibility Test Plans and Procedures. Activity concerning the foregoing interface discussions has been and will continue to be based upon the "TDS Estimated Capabilities Document for the Helios Missions" (613-1), and the "DSN/Flight Project Interface Design Handbook" (810-5). These will continue to be considered TDS controlling documents until specific Helios Project/TDS interface documentation is generated and signed off by the respective parties. In addition to the above, the DSN continued the Helios Trainee Program with seven GfW/DFVLR trainees in residence at JPL. Two trainees will complete their year's residency concurrent with the Third Helios Joint Working Group Meeting, while four new trainees are expected to arrive following the Third Helios Joint Working Group Meeting. These and other activities are reported in detail in the paragraphs that follow.
Ousley, Gilbert↗
Evolution of the Lunar Network
The National Aeronautics and Space Administration (NASA) is planning to upgrade its network Infrastructure to support missions for the 21st century. The first step is to increase the data rate provided to science missions to at least the 100 megabits per second (Mbps) range. This is under way, using Ka-band 26 Gigahertz (GHz), erecting an 18-meter antenna for the Lunar Reconnaissance Orbiter (LRO), and the planned upgrade of the Deep Space Network (DSN) 34-meter network to support the James Webb Space Telescope (JWST). The next step is the support of manned missions to the Moon and beyond. Establishing an outpost with several activities such as rovers, colonization, and observatories, is better achieved by using a network configuration rather than the current method of point-to-point communication. Another challenge associated with the Moon is communication coverage with the Earth. The Moon's South Pole, targeted for human habitat and exploration, is obscured from Earth view for half of the 28-day lunar cycle and requires the use of lunar relay satellites to provide coverage when there is no direct view of the Earth. The future NASA and Constellation network architecture is described in the Space Communications Architecture Working Group (SCAWG) Report. The Space Communications and Navigation (SCAN) Constellation Integration Project (SCIP) is responsible for coordinating Constellation requirements and has assigned the responsibility for implementing these requirements to the existing NASA communication providers: DSN, Space Network (SN), Ground Network (GN) and the NASA Integrated Services Network (NISN). The SCAWG Report provides a future architecture but does not provide implementation details. The architecture calls for a Netcentric system, using hundreds of 12-meter antennas, a ground antenna array, and a relay network around the Moon. The report did not use cost as a variable in determining the feasibility of this approach. As part of the SCIP Mission Concept Review and the second iteration of the Lunar Architecture Team (LAT), the focus is on cost, as well as communication coverage using operational scenarios. This approach maximizes use of existing assets and adds capability in small increments. This paper addresses architecture decisions such as the Radio Frequency (RF) signal and network (Netcentric) decisions that need to be made and the difficulty of implementing them into the existing Space Network and DSN. It discusses the evolution of the lunar system and describes its components: Tracking and Data Relay Satellite System (TDRSS), Earth-based ground stations, Lunar Relay, and surface systems.
Gal-Edd, Jonathan↗