SEARCH · Search NASA

Results for “Consultative Committee for Space Data Systems (CCSDS)”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 55 records · Page 3

All sources NASA NTRS DOE OSTI

NASA NTRS1992

The experiment of CCSDS packet telemetry using a highly elliptical orbit satellite 'Hiten'

This paper describes the outline of the telemetry scheme proposed by the Consultative Committee of Space Data Systems (CCSDS), and the on-orbit experiment which was carried out to show the applicability of the CCSDS packet telemetry scheme using the Japan's satellite Hiten in a highly elliptical orbit. The telemetry data which are generated by the instruments are packetized in Hiten and reformed to the original data in earth stations successfully. The experimental results showed that the standardized scheme is helpful in allowing for tracking cross support between organizations, and the concatenated code is quite effective to transmit data in a low C/N condition.

Takano, Tadashi↗

NASA NTRSDate not supplied

Latest Status of the CCSDS Optical Communications Working Group

International civil space agencies around the world are working together in the Interagency Operation Advisory Group (IOAG) and the Consultative Committee for Space Data Systems (CCSDS) to develop interoperability architectures and standards for space communications. Within CCSDS, there is a working group dedicated on developing recommendations and standards for optical communications. These standards include recommendations for the physical layer, coding and synchronization layer, and best practices for measuring and monitoring atmospheric conditions and operating optical links. The working group has developed standards for both Near Earth and deep space robotic and hum exploration missions. The standards generally address both free space links between spacecraft and free space links between spacecraft and ground. This paper will provide an overview and update on the set of standards the CCSDS Optical Communications Working Group has developed

Bernard L Edwards↗

NASA NTRS1995

Incorporating CCSDS telemetry standards and philosophy on Cassini

The Cassini project at the Jet Propulsion Laboratory (JPL) is implementing a spacecraft telemetry system based on the Consultative Committee for Space Data Systems (CCSDS) packet telemetry standards. Resolving the CCSDS concepts with a Ground Data System designed to handle time-division-multiplexed telemetry and also handling constraints unique to a deep-space planetary spacecraft (such as fixed downlink opportunities, small downlink rates and requirements for on-board data storage) have resulted in spacecraft and ground system design challenges. Solving these design challenges involved adapting and extending the CCSDS telemetry standards as well as changes to the spacecraft and ground system designs. The resulting spacecraft/ground system design is an example of how new ideas and philosophies can be incorporated into existing systems and design approaches without requiring significant rework. In addition, it shows that the CCSDS telemetry standards can be successfully applied to deep-space planetary spacecraft.

Day, John C.↗

NASA NTRS1995

Incorporating CCSDS Telemetry Standards and Philosophy on Cassini

CCSDS↗

NASA NTRS1996

Use of CCSDS and OSI Protocols on the Advanced Communications Technology Satellite

Although ACTS (Advanced Communications Technology Satellite) provides an almost error-free channel during much of the day and under most conditions, there are times when it is not suitable for reliably error-free data communications when operating in the uncoded mode. Because coded operation is not always available to every earth station, measures must be taken in the end system to maintain adequate throughput when transferring data under adverse conditions. The most effective approach that we tested to improve performance was the addition of an 'outer' Reed-Solomon code through use of CCSDS (Consultative Committee for Space Data Systems) GOS 2 (a forward error correcting code). This addition can benefit all users of an ACTS channel including those applications that do not require totally reliable transport, but it is somewhat expensive because additional hardware is needed. Although we could not characterize the link noise statistically (it appeared to resemble uncorrelated white noise, the type that block codes are least effective in correcting), we did find that CCSDS GOS 2 gave an essentially error-free link at BER's (bit error rate) as high as 6x10(exp -4). For users that demand reliable transport, an ARQ (Automatic Repeat Queuing) protocol such as TCP (Transmission Control Protocol) or TP4 (Transport Protocol, Class 4) will probably be used. In this category, it comes as no surprise that the best choice of the protocol suites tested over ACTS was TP4 using CCSDS GOS 2. TP4 behaves very well over an error-free link which GOS 2 provides up to a point. Without forward error correction, however, TP4 service begins to degrade in the 10(exp -7)-10(exp -6) range and by 4x10(exp -6), it barely gives any throughput at all. If Congestion Avoidance is used in TP4, the degradation is even more pronounced. Fortunately, as demonstrated here, this effect can be more than compensated for by choosing the Selective Acknowledgment option. In fact, this option can enable TP4 to deliver some throughput at error rates as high as 10(exp -5).

Chirieleison, Don↗

NASA NTRS2019

An Update on the CCSDS Optical Communications Working Group Interoperability Standards

International space agencies around the world are working together in the Interagency Operation Advisory Group (IOAG) and the Consultative Committee for Space Data Systems (CCSDS) to develop interoperability standards for optical communications. The standards support optical communication systems for both Near Earth and Deep Space robotic and human-rated spacecraft. The standards generally address both free space links between spacecraft and free space links between spacecraft and ground. This paper will overview the history and structure of the CCSDS Optical Communications Working Group and provide an update on the set of optical communications standards being developed. The paper will address the ongoing work on High Photon Efficiency communications, High Data Rate communications, and Optical On/Off Keying communications. It will also cover the working being done within CCSDS on documenting atmospheric measurement techniques and link operations concepts.

Edwards, Bernard L.↗

NASA NTRS2015

Telescience Resource Kit (TReK)

Telescience Resource Kit (TReK) is one of the Huntsville Operations Support Center (HOSC) remote operations solutions. It can be used to monitor and control International Space Station (ISS) payloads from anywhere in the world. It is comprised of a suite of software applications and libraries that provide generic data system capabilities and access to HOSC services. The TReK Software has been operational since 2000. A new cross-platform version of TReK is under development. The new software is being released in phases during the 2014-2016 timeframe. The TReK Release 3.x series of software is the original TReK software that has been operational since 2000. This software runs on Windows. It contains capabilities to support traditional telemetry and commanding using CCSDS (Consultative Committee for Space Data Systems) packets. The TReK Release 4.x series of software is the new cross platform software. It runs on Windows and Linux. The new TReK software will support communication using standard IP protocols and traditional telemetry and commanding. All the software listed above is compatible and can be installed and run together on Windows. The new TReK software contains a suite of software that can be used by payload developers on the ground and onboard (TReK Toolkit). TReK Toolkit is a suite of lightweight libraries and utility applications for use onboard and on the ground. TReK Desktop is the full suite of TReK software -most useful on the ground. When TReK Desktop is released, the TReK installation program will provide the option to choose just the TReK Toolkit portion of the software or the full TReK Desktop suite. The ISS program is providing the TReK Toolkit software as a generic flight software capability offered as a standard service to payloads. TReK Software Verification was conducted during the April/May 2015 timeframe. Payload teams using the TReK software onboard can reference the TReK software verification. TReK will be demonstrated on-orbit running on an ISS provided T61p laptop. Target Timeframe: September 2015 -2016. The on-orbit demonstration will collect benchmark metrics, and will be used in the future to provide live demonstrations during ISS Payload Conferences. Benchmark metrics and demonstrations will address the protocols described in SSP 52050-0047 Ku Forward section 3.3.7. (Associated term: CCSDS File Delivery Protocol (CFDP)).

Lippincott, Jeff↗

NASA NTRS1996

Maximum ADPE Approach for a High Rate CCSDS Return Link Processing System

The earth observing system data and operations system (EDOS) multi-mission data processing and distribution system for the earth observing system is considered. The EDOS was based on the Consultative Committee for Space Data Systems (CCSDS) protocols. The development included the challenge of developing and demonstrating a 150 Mbps CCSDS return link processing capability for the support of the first EDOS delivery. The approach used general-purpose automated data processing equipment (ADPE) and minimized the use of customized hardware. The way in which the system was developed is described. The principle design decisions and the performance benchmark results are presented.

Krimchansky, Alexander↗

NASA NTRS2015

Finalizing the CCSDS Space-Data Link Layer Security Protocol: Setup and Execution of the Interoperability Testing

The protection of data transmitted over the space-link is an issue of growing importance also for civilian space missions. Through the Consultative Committee for Space Data Systems (CCSDS), space agencies have reacted to this need by specifying the Space Data-Link Layer Security (SDLS) protocol which provides confidentiality and integrity services for the CCSDS Telemetry (TM), Telecommand (TC) and Advanced Orbiting Services (AOS) space data-link protocols. This paper describes the approach of the CCSDS SDLS working group to specify and execute the necessary interoperability tests. It first details the individual SDLS implementations that have been produced by ESA, NASA, and CNES and then the overall architecture that allows the interoperability tests between them. The paper reports on the results of the interoperability tests and identifies relevant aspects for the evolution of the test environment.

Fischer, Daniel↗

NASA NTRS2016

Next Generation Flight Displays Using HTML5

The Human Integrated Vehicles and Environments (HIVE) lab at Johnson Space Center (JSC) is focused on bringing together inter-disciplinary talent to design and integrate innovative human interface technologies for next generation manned spacecraft. As part of this objective, my summer internship project centered on an ongoing investigation in to building flight displays using the HTML5 standard. Specifically, the goals of my project were to build and demo "flight-like" crew and wearable displays as well as create a webserver for live systems being developed by the Advanced Exploration Systems (AES) program. In parallel to my project, a LabVIEW application, called a display server, was created by the HIVE that uses an XTCE (XML (Extensible Markup Language) Telemetry and Command Exchange) parser and CCSDS (Consultative Committee for Space Data System) space packet decoder to translate telemetry items sent by the CFS (Core Flight Software) over User Datagram Protocol (UDP). It was the webserver's job to receive these UDP messages and send them to the displays. To accomplish this functionality, I utilized Node.js and the accompanying Express framework. On the display side, I was responsible for creating the power system (AMPS) displays. I did this by using HTML5, CSS and JavaScript to create web pages that could update and change dynamically based on the data they received from the webserver. At this point, I have not started on the commanding, being able to send back to the CFS, portion of the displays but hope to have this functionality working by the completion of my internship. I also created a way to test the webserver's functionality without the display server by making a JavaScript application that read in a comma-separate values (CSV) file and converted it to XML which was then sent over UDP. One of the major requirements of my project was to build everything using as little preexisting code as possible, which I accomplished by only using a handful of JavaScript libraries. As a side project, I created a model of the HIVE lab and Building 29 using SketchUp. I obtained the floorplans of the building from the JSC Geographic Information Systems (GIS), which were computer-aided design (CAD) files, and imported them into SketchUp. I then took those floorplans and created a 3D model of the building from them. Working in conjunction with the Hybrid Reality lab in Building 32, the SketchUp model was imported into Unreal Engine for use with the HTC Vive. Using the Vive, I was able to interact with the model I created in virtual reality (VR). The purpose of this side project was to be able to visualize potential lab layouts and mockup designs as they are in development in order to finalize design decisions. Pending approval, the model that I created will be used in the Build-As-You-Test: Can Hybrid Reality Improve the SE/HSI Design Process project in the fall. Getting the opportunity to work at NASA has been one of the most memorable experiences of my life. Over the course of my internship, I improved my programming and web development abilities substantially. I will take all the skills and experiences I have had while at NASA back to school with me in the fall and hope to pursue a career in the aerospace industry after graduating in the spring.

Greenwood, Brian↗

NASA NTRS2009

Developing a Standard Method for Link-Layer Security of CCSDS Space Communications

Communications security for space systems has been a specialized field generally far removed from considerations of mission interoperability and cross-support in fact, these considerations often have been viewed as intrinsically opposed to security objectives. The space communications protocols defined by the Consultative Committee for Space Data Systems (CCSDS) have a twenty-five year history of successful use in over 400 missions. While the CCSDS Telemetry, Telecommand, and Advancing Orbiting Systems protocols for use at OSI Layer 2 are operationally mature, there has been no direct support within these protocols for communications security techniques. Link-layer communications security has been successfully implemented in the past using mission-unique methods, but never before with an objective of facilitating cross-support and interoperability. This paper discusses the design of a standard method for cryptographic authentication, encryption, and replay protection at the data link layer that can be integrated into existing CCSDS protocols without disruption to legacy communications services. Integrating cryptographic operations into existing data structures and processing sequences requires a careful assessment of the potential impediments within spacecraft, ground stations, and operations centers. The objective of this work is to provide a sound method for cryptographic encapsulation of frame data that also facilitates Layer 2 virtual channel switching, such that a mission may procure data transport services as needed without involving third parties in the cryptographic processing, or split independent data streams for separate cryptographic processing.

Biggerstaff, Craig↗

NASA NTRS1990

CCSDS transfer frames in the realtime NASA/DLR link for the Spacelab-D2 mission

The German Space Operations Center (GSOC) Spacelab D2 mission system is a forerunner of the GSOC system which will accept 'virtual channel' transfer frame data directly from the NASA Consumer Data and Operations System (and/or the equivalent European and Japanese ground data handling systems). This experience with the Consultative Committee for Space Data Systems (CCSDS) will prepare GSOC to implement an effective and efficient system for control of payloads and for the handling of CCSDS-format data well into the 21st century.

Kelly, Angelita C.↗

NASA NTRS2012

Use of CCSDS Packets Over SpaceWire to Control Hardware

For the Lunar Reconnaissance Orbiter, the Command and Data Handling subsystem consisted of several electronic hardware assemblies that were connected with SpaceWire serial links. Electronic hardware would be commanded/controlled and telemetry data was obtained using the SpaceWire links. Prior art focused on parallel data buses and other types of serial buses, which were not compatible with the SpaceWire and the core flight executive (CFE) software bus. This innovation applies to anything that utilizes both SpaceWire networks and the CFE software. The CCSDS (Consultative Committee for Space Data Systems) packet contains predetermined values in its payload fields that electronic hardware attached at the terminus of the SpaceWire node would decode, interpret, and execute. The hardware s interpretation of the packet data would enable the hardware to change its state/configuration (command) or generate status (telemetry). The primary purpose is to provide an interface that is compatible with the hardware and the CFE software bus. By specifying the format of the CCSDS packet, it is possible to specify how the resulting hardware is to be built (in terms of digital logic) that results in a hardware design that can be controlled by the CFE software bus in the final application

Haddad, Omar↗

NASA NTRS2003

CCSDS File Delivery Protocol (CFDP): Why it's Useful and How it Works

Reliable delivery of data products is often required across space links. For example, a NASA mission will require reliable delivery of images produced by an on-board detector. Many missions have their own (unique) way of accomplishing this, requiring custom software. Many missions also require manual operations (e.g. the telemetry receiver software keeps track of what data is missing, and a person manually inputs the appropriate commands to request retransmissions). The Consultative Committee for Space Data Systems (CCSDS) developed the CCSDS File Delivery Protocol (CFDP) specifically for this situation. CFDP is an international standard communication protocol that provides reliable delivery of data products. It is designed for use across space links. It will work well if run over the widely used CCSDS Telemetry and Telecommand protocols. However, it can be run over any protocol, and will work well as long as the underlying protocol delivers a reasonable portion of the data. The CFDP receiver will autonomously determine what data is missing, and request retransmissions as needed. The CFDP sender will autonomously perform the requested transmissions. When the entire data product is delivered, the CFDP receiver will let the CFDP sender know that the transaction has completed successfully. The result is that custom software becomes standard, and manual operations become autonomous. This paper will consider various ways of achieving reliable file delivery, explain why CFDP is the optimal choice for use over space links, explain how the core protocol works, and give some guidance on how to best utilize CFDP within various mission scenarios. It will also touch on additional features of CFDP, as well as other uses for CFDP (e.g. the loading of on-board memory and tables).

Ray, Tim↗

NASA NTRS1990

CCSDS telemetry systems experience at the Goddard Space Flight Center

NASA Goddard Space Flight Center (GSFC) designs, builds, manages, and operates science and applications spacecraft in near-earth orbit, and provides data capture, data processing, and flight control services for these spacecraft. In addition, GSFC has the responsibility of providing space-ground and ground-ground communications for near-earth orbiting spacecraft, including those of the manned spaceflight programs. The goal of reducing both the developmental and operating costs of the end-to-end information system has led the GSFC to support and participate in the standardization activities of the Consultative Committee for Space Data Systems (CCSDS), including those for packet telemetry. The environment in which such systems function is described, and the GSFC experience with CCSDS packet telemetry in the context of the Gamma-Ray Observatory project is discussed.

Carper, Richard D.↗

NASA NTRS2017

An Update on the CCSDS Optical Communications Working Group

International space agencies around the world are currently developing optical communication systems for Near Earth and Deep Space applications for both robotic and human rated spacecraft. These applications include both links between spacecraft and links between spacecraft and ground. The Interagency Operation Advisory Group (IOAG) has stated that there is a strong business case for international cross support of spacecraft optical links. It further concluded that in order to enable cross support the links must be standardized. This paper will overview the history and structure of the space communications international standards body, the Consultative Committee for Space Data Systems (CCSDS), that will develop the standards and provide an update on the proceedings of the Optical Communications Working Group within CCSDS. This paper will also describe the set of optical communications standards being developed and outline some of the issues that must be addressed in the next few years. The paper will address in particular the ongoing work on application scenarios for deep space to ground called High Photon Efficiency, for LEO to ground called Low Complexity, for inter-satellite and near Earth to ground called High Data Rate, as well as associated atmospheric measurement techniques and link operations concepts.

Laser and Optical Communications↗

NASA NTRS2020

The Use of the CCSDS Unified Space Data Link Protocol on All Space Links

NASA is actively pursuing the development of data link layer protocols for the human space program with the added intent of infusing the key capabilities of efficient space link security, support for inter-networking, and compatible operational modes with Optical Communications. There seems to be two divergent technical approaches on how to provide these capabilities: one associated with the use of a fixed length Protocol Data Unit (PDU) i.e., a fixed length transfer frame, and the other advocating the use of a variable length transfer frame. The objective of this paper is to evaluate the pros and cons of these two approaches within the context of existing Consultative Committee for Space Data Systems (CCSDS) Space Data Link Protocols and Channel Coding Recommendations for all space links: space to ground (return) link, ground to space (forward) link and space to space (proximity) links.

Kazz, Greg J↗

NASA NTRS2011

Interplanetary Overlay Network Bundle Protocol Implementation

The Interplanetary Overlay Network (ION) system's BP package, an implementation of the Delay-Tolerant Networking (DTN) Bundle Protocol (BP) and supporting services, has been specifically designed to be suitable for use on deep-space robotic vehicles. Although the ION BP implementation is unique in its use of zero-copy objects for high performance, and in its use of resource-sensitive rate control, it is fully interoperable with other implementations of the BP specification (Internet RFC 5050). The ION BP implementation is built using the same software infrastructure that underlies the implementation of the CCSDS (Consultative Committee for Space Data Systems) File Delivery Protocol (CFDP) built into the flight software of Deep Impact. It is designed to minimize resource consumption, while maximizing operational robustness. For example, no dynamic allocation of system memory is required. Like all the other ION packages, ION's BP implementation is designed to port readily between Linux and Solaris (for easy development and for ground system operations) and VxWorks (for flight systems operations). The exact same source code is exercised in both environments. Initially included in the ION BP implementations are the following: libraries of functions used in constructing bundle forwarders and convergence-layer (CL) input and output adapters; a simple prototype bundle forwarder and associated CL adapters designed to run over an IPbased local area network; administrative tools for managing a simple DTN infrastructure built from these components; a background daemon process that silently destroys bundles whose time-to-live intervals have expired; a library of functions exposed to applications, enabling them to issue and receive data encapsulated in DTN bundles; and some simple applications that can be used for system checkout and benchmarking.

Burleigh, Scott C.↗