Search NASA⌕ Search

SEARCH · Search NASA

Results for “The 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.

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

At least 37 records · Page 2

CCSDS - Advancing Spaceflight Technology for International Collaboration

The Consultative Committee for Space Data Systems (CCSDS) has been developing data and communications standards since 1982, with the objective of providing interoperability for enabling international collaboration for spaceflight missions. As data and communications technology has advanced, CCSDS has progressed to capitalize on existing products when available and suitable for spaceflight, and to develop innovative new approaches when available products fail. The current scope of the CCSDS architecture spans the end-to-end data architecture of a spaceflight mission, with ongoing efforts to develop and standardize cutting-edge technology. This manuscript describes the overall architecture, the position of CCSDS in the standards and international mission community, and some CCSDS processes. It then highlights in detail several of the most interesting and critical technical areas in work right now, and how they support collaborative missions. Special topics include: Delay/Disruption Tolerant Networking (DTN), Asynchronous Message Service (AMS), Multispectral/Hyperspectral Data Compression (MHDC), Coding and Synchronization, Onboard Wireless, Spacecraft Monitor and Control, Navigation, Security, and Time Synchronization/Correlation. Broad international participation in development of CCSDS standards is encouraged.

Kearney, Mike↗

CCSDS Advanced Orbiting Systems - International data communications standards for the Space Station Freedom

Established in 1982, the Consultative Committee for Space Data Systems (CCSDS) is an international organization that is staffed by data-handling experts from nearly all of the world's major space agencies. Its goal is to develop standard data-communications techniques so that several agencies may cross-support each other's data flow and thus allow complex, international missions to be flown. Under the general umbrella of Advanced Orbiting Systems (AOS), an international CCSDS task force was formed in 1985 to develop standard data-communications concepts for manned missions, such as the Space Station Freedom and the Hermes space plane, and large unmanned vehicles, such as polar orbiting platforms. The history of the CCSDS and the development of the AOS recommendation are reviewed, and the user services and protocols embodied in its systems architecture are introduced.

Hooke, Adrian J.↗

CCSDS BP V7 Bluebook Recommendation

This export is a CCSDS presentation that recommends what is necessary to create a version (V7) DTN specification for the Consultative Committee for Space Data Systems (CCSDS) blue book and is based on IETF RFC BPBis.v26 (Note the original CCSDS standard as IRTF 5050). The considerations in this presentation follow the current CCSDS specification 734.2-B-1 (​https://public.ccsds.org/Pubs/734x2b1.pdf​) and is consistent with its intent and level of service. In it, are identified areas requiring updates and specification items that are essential to meet current minimums of capability.

Delay Tolerant Networking↗

NASA/Goddard Space Flight Center's testbed for CCSDS compatible systems

A testbed for flight and ground systems compatible with the Consultative Committee for Space Data Systems (CCSDS) Recommendations has been developed at NASA's Goddard Space Flight Center. The subsystems of an end-to-end CCSDS based data system are being developed. All return link CCSDS telemetry services (except Internet) and both versions of the CCSDS frame formats are being implemented. In key areas of uncertainty, multiple design approaches are being performed. In addition, key flight-qualifiable hardware components, such as Reed-Solomon encoders, are being developed to complement the testbed element development. The testbed and its capabilities are described. The method of dissemination of the testbed results are given, as are plans to make the testbed capabilities available to outside users. Plans for the development of standardized conformance and compatibility tests are provided.

Carper, Richard D.↗

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 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. The maturity level of this protocol set is, however, insufficient for mission inclusion at this time. This prototype is intended to provide experience which will raise the Technical Readiness Level (TRL) of these protocols..

Rich, Thomas M.↗

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.↗

Overview of AMS (CCSDS Asynchronous Message Service)

This viewgraph presentation gives an overview of the Consultative Committee for Space Data Systems (CCSDS) Asynchronous Message Service (AMS). The topics include: 1) Key Features; 2) A single AMS continuum; 3) The AMS Protocol Suite; 4) A multi-continuum venture; 5) Constraining transmissions; 6) Security; 7) Fault Tolerance; 8) Performance of Reference Implementation; 9) AMS vs Multicast (1); 10) AMS vs Multicast (2); 11) RAMS testing exercise; and 12) Results.

asynchronous↗

CCSDS concept paper: Delta-DOR

This Concept Paper proposes the development of Consultative Committee for Space Data Systems (CCSDS) standards for the deep space navigation technique known as 'delta-DOR' (Delta Differential One-Way Ranging).

delta-DOR↗

Applications of CCSDS recommendations to Integrated Ground Data Systems (IGDS)

This paper describes an application of the CCSDS Principle Network (CPH) service model to communications network elements of a postulated Integrated Ground Data System (IGDS). Functions are drawn principally from COSMICS (Cosmic Information and Control System), an integrated space control infrastructure, and the Earth Observing System Data and Information System (EOSDIS) Core System (ECS). From functional requirements, this paper derives a set of five communications network partitions which, taken together, support proposed space control infrastructures and data distribution systems. Our functional analysis indicates that the five network partitions derived in this paper should effectively interconnect the users, centers, processors, and other architectural elements of an IGDS. This paper illustrates a useful application of the CCSDS (Consultive Committee for Space Data Systems) Recommendations to ground data system development.

Mizuta, Hiroshi↗

An Object-Oriented Interface to the CCSDS Ground Telecommand Services

The Telecommand Data Routing and Channel Services defined by the Consultative Committee for Space Data Systems (CCSDS) are flexible enough to support a myriad of commanding models. Because the standard is so broad, the traditional approach has been to implement only the portion of the standard needed by the particular spacecraft being tested/operated. Tasked with providing Telecommand Services for an entire class of spacecraft, where each spacecraft may choose any valid CCSDS commanding model, NASA Code 584 designed a common architecture capable of handling the full CCSDS protocol. The solution uses another CCSDS standard - the Standard Formatted Data Unit (SFDU) as the interface to the Telecommand Services. SFDUs provide a consistent way of labelling data objects, as well as allowing data objects to encapsulate other data objects. The resulting interface is: - Flexible: The full Data Routing and Channel Services are available via a single interface. The client (i.e. the command source) may enter commands at any layer within the protocol stack, specify any of the data aggregation or segmentation methods, and dynamically set any configuration parameter defined in the standard. - Object-oriented: Each object specifies both the data and the actions to be performed with the data. An object may contain other objects. - Expandable: New capabilities are added by defining new objects. Objects pass thru the protocol layers until they reach the applicable layer. The resulting design is: - Modular: The logic for each protocol layer is contained in a separate Application Program Interface (API). The objects used for the external interface are also used for communication between layers. - Distributable: The design can be split along any layer boundary for distribution across multiple machines. The objects ensure data consistency across platforms. This paper describes the SFDU-based interface and the resulting protocol implementation. The implementation is currently used by NASA (National Aeronautics and Space Administration) for integration & test of the microwave Anisotropy Probe (MAP) and Earth observer-I (EO-l) spacecraft. It will be used for post-launch operations of these spacecraft as well as the Imager for Magnetopause to Aurora Global Exploration (IMAGE) spacecraft.

Ray, Timothy Joseph↗

Exchange of Standardized Flight Dynamics Data

Spacecraft operations require the knowledge of the vehicle trajectory and attitude and also that of other spacecraft or natural bodies. This knowledge is normally provided by the Flight Dynamics teams of the different space organizations and, as very often spacecraft operations involve more than one organization, this information needs to be exchanged between Agencies. This is why the Navigation Working Group within the CCSDS (Consultative Committee for Space Data Systems), has been instituted with the task of establishing standards for the exchange of Flight Dynamics data. This exchange encompasses trajectory data, attitude data, and tracking data. The Navigation Working Group includes regular members and observers representing the participating Space Agencies. Currently the group includes representatives from CNES, DLR, ESA, NASA and JAXA. This Working Group meets twice per year in order to devise standardized language, methods, and formats for the description and exchange of Navigation data. Early versions of some of these standards have been used to support mutual tracking of ESA and NASA interplanetary spacecraft, especially during the arrival of the 2003 missions to Mars. This paper provides a summary of the activities carried out by the group, briefly outlines the current and envisioned standards, describes the tests and operational activities that have been performed using the standards, and lists and discusses the lessons learned from these activities.

standards↗

CCSDS - A forum to facilitate international cooperation among space agencies

An overview is presented of the Consultative Committee for Space Data Systems (CCSDS) in its role as a promoter the development and utilization of compatible data-systems standards among the principal space agencies of the world. Attention is also given to the CCSDS affiliation categories comprising member agencies, observer agencies, and associates. Consideration is given to the CCSDS organization, the technical panels, and current CCSDS recommendations.

Greene, Edward P.↗

Performance analysis of CCSDS path service

A communications service, called Path Service, is currently being developed by the Consultative Committee for Space Data Systems (CCSDS) to provide a mechanism for the efficient transmission of telemetry data from space to ground for complex space missions of the future. This is an important service, due to the large volumes of telemetry data that will be generated during these missions. A preliminary analysis of performance of Path Service is presented with respect to protocol-processing requirements and channel utilization.

Johnson, Marjory J.↗

Benefits and Challenges of CCSDS File Delivery Protocol as Applied to Europa Clipper

—This paper describes the use of the Consultative Committee for Space Data Systems (CCSDS) File Delivery Protocol (CFDP) on the Europa Clipper mission for both uplink and downlink of files. It includes an overview of CFDP, the history of why CFDP was chosen, how it benefits mission operations, some of the mission scenarios that stress CFDP, operability aspects, the best practices that Clipper adopted from other missions and some of the technical challenges with implementation, and verification and validation. The benefits to mission operations accrue because CFDP reduces the need for manual management of file transfer, including retransmission of missing data, and deletion of files only after confirmation of receipt by the ground. The challenges occur because CFDP is a round-trip protocol – it requires messages in both directions to complete a file transfer, and because it uses timers to ensure that control messages are resent if needed to prevent transactions from going stale. Any situations where communication is restricted to a single direction, interrupted, reordered, or backlogged can pose a challenge. There are also implementation challenges. Europa Clipper is the first mission at the Jet Propulsion Laboratory (JPL) to adopt class 2, fully acknowledged, CFDP for both uplink and downlink. The implementation needed new software, requirements and operational procedures. The experience of the Applied Physics Laboratory (APL) with CFDP from their previous missions was crucial to success for Europa Clipper. Because CFDP relies on timers and messages travel in both directions, verification and validation (V&V) requires new approaches. For certain scenarios, a live ground system talking to a live flight system with realistic simulated one-way light times, data rates and data outages must be used.

Albers, Joshua↗

Proposal for implementation of CCSDS standards for use with spacecraft engineering/housekeeping data

Many of today's low earth orbiting spacecraft are using the Consultative Committee for Space Data Systems (CCSDS) protocol for better optimization of down link RF bandwidth and onboard storage space. However, most of the associated housekeeping data has continued to be generated and down linked in a synchronous, Time Division Multiplexed (TDM) fashion. There are many economies that the CCSDS protocol will allow to better utilize the available bandwidth and storage space in order to optimize the housekeeping data for use in operational trending and analysis work. By only outputting what is currently important or of interest, finer resolution of critical items can be obtained. This can be accomplished by better utilizing the normally allocated housekeeping data down link and storage areas rather than taking space reserved for science.

Welch, Dave↗

Using CCSDS Standards to Reduce Mission Costs

NASA's open source Core Flight System (cFS) software framework has been using several Consultative Committee for Space Data Systems (CCSDS) standards since its inception. Recently developed CCSDS standards are now being applied by NASA, ESA and other organizations to streamline and automate aspects of mission development, test, and operations, speeding mission schedules and reducing mission costs. This paper will present the new CCSDS Spacecraft Onboard Interfaces Services (SOIS) Electronic Data Sheet (EDS) standards and show how they are being applied to data interfaces in the cFS software framework, tool chain, and ground systems across a range of missions at NASA. Although NASA is focusing on the cFS, it expected that these technologies are well suited for use in other system architectures and can lower costs for a wide range of both large and small satellites.

Wilmot, Jonathan↗