Skip Ribbon Commands
Skip to main content
SharePoint

Charters : 6.05 Asynchronous Message Service Working Group

Manage PermissionsManage Permissions
|
Version HistoryVersion History

Name of Group

Short Name

Area

Chairperson

Chairperson E-Mail Address

Chairperson Agency

Deputy Chairperson

Deputy Chairperson E-Mail Address

Deputy Chairperson Agency

Mailing List

Scope of Activity

Rationale for Activity

Goals

Survey of Similar Standards Efforts Undertaken in Other Bodies and elsewhere in CCSDS

Patent Licensing Applicability for Future Standards

Technical Risk Mitigation Strategy

Management Risk Mitigation Strategy

Description of Change

Disable Alert

Area Director E-Mail Address

Deputy Area Director E-Mail Address

Create Poll

CC Yourself

Completed/Closed

Approval Status

Attachments

Version:
Created at by
Last modified at by

Manage PermissionsManage Permissions
|
Version HistoryVersion History

Name of Group

6.05 Asynchronous Message Service Working Group

Area

Space Internetworking Services Area (SIS)

Chairperson

Scott Burleigh

Chairperson E-Mail Address

Scott.C.Burleigh@jpl.nasa.gov

Chairperson Agency

NASA

Deputy Chairperson

Deputy Chairperson E-Mail Address

Deputy Chairperson Agency

Mailing List

sis-ams@mailman.ccsds.org

Scope of Activity

Rationale for Activity

The CCSDS File Delivery Protocol (CFDP) provides file transfer functionality that can offer significant benefits for spacecraft operations.  Not all spacecraft communication requirements necessarily fit the file transfer model, however.  In particular, continuous, event-driven asynchronous message exchange may also be useful for communications with and among spacecraft.  Examples include: – streaming engineering (housekeeping) data; – real-time commanding; – continuous collaborative operation among robotic craft. NASA’s proposed new Command, Control, Communications, and Information (C3I) architecture for the Crew Exploration Vehicle and other Constellation program elements is based on an asynchronous message exchange framework. At the same time, large-scale, efficient, robust asynchronous message exchange can be difficult to implement.  Among the challenges: – A successful large-scale message system must tolerate heterogeneity in deployment platforms, security regimes, communication environments, QOS requirements, performance requirements, and levels of cost tolerance. – In order to support continuous mission-critical operation, a message system must tolerate unplanned changes in application topology.  This tolerance of change entails autonomous discovery of communication endpoints and automatic reconfiguration, to minimize operations cost and risk. – Distributed systems based on asynchronous message exchange are typically less labor-intensive to configure, upgrade, and operate if message transmission conforms to the peer-to-peer ‘publish/subscribe’ (or ‘push’) model rather than the ‘client/server’ model.  But publish/subscribe communication is made possible only by extensive underlying automation. Consequently most existing asynchronous message exchange systems are proprietary, licensed products rather than open international standards.  Moreover, no such system is designed for mission-critical operation on deep space robots. We believe that an open CCSDS standard for large-scale, publish/subscribe-based asynchronous message exchange would be a useful alternative.

Goals

AMS-WG is a Standards Track Working Group.  The Working Group will develop a Recommended Standard for an Asynchronous Message Service, based on the Concept Paper submitted with this Charter, that satisfies the requirements identified by the AMS BOF group. Per standard CCSDS procedure, development of this Recommended Standard will entail demonstration of two interoperable implementations of the protocol and service.

Survey of Similar Standards Efforts Undertaken in
Other Bodies and elsewhere in CCSDS

The RTPS (Real-Time Publish-Subscribe) protocol standardized by the Object Management Group is comparable to AMS. An objective comparative evaluation of AMS and RTPS is recommended.

Patent Licensing Applicability for Future Standards

No patented technologies apply.
 

Technical Risk Mitigation Strategy

The service concept is derived from a design, developed at JPL in the mid-1990s, which has proved efficient and stable in a number of deployments over the past decade; JPL’s initial implementation of AMS will be adapted from that established code base.  Technical risk therefore appears to be minimal.

Management Risk Mitigation Strategy

Unavailability of resources could delay achievement of milestones.  Fallback option would be to reschedule the milestones.
Version:
Created at by
Last modified at by

Note - To view "Draft" projects, which are not yet approved Click Here.

 Approved Projects

|Export to Spreadsheet|
Currently 2 Projects     
Document Type
Project Status
Project Phase
Modified By
Asynchronous Message ServiceBlueAll Tasks CompletedProject CompletedCCSDS Tech Support 
Asynchronous Message ServiceGreenAll Tasks CompletedProject CompletedCCSDS Tech Support