Charters : 3.07 Cross Support Space Communications Architecture Working Group

 

CCSDS has many recommendations that range from very specific physical spacelink protocols to (an eventual) routed space internetworked environment. CCSD offers no guidance as to how the broad set of recommendations  fit together and more importantly what are the best approaches with regard to the various options identified in the various recommendations.  A cross support architecture definition is needed.  This will benefit CCSDS member agencies by providing a ready reference and guide for implementation of  services that more often than not involve many aspects of standardization.

The goals of the Working Group are development of:
1) A reference model that includes the concept and the detailed technical rationale for a normative Space Communication Architecture, and
2)  Space Communication Cross Support Architecture normative recommended practice that
  a) Identifies the cross support forward and return services including, but not necessarily limited to the following classes of data
    i. Telemetry,
    ii. Telecommand,
    iii. Radiometric (Raw and Processed)
    iv. Audio,
    v. Video,
    vi. Time correlation and synchronization;
  b) Identifies the management functions including, but not necessarily limited to
    i. Mission Support Planning,
    ii. Mission Service Agreement,
    iii. Service Package Management, include service package execution monitoring and control,
    iv. Service Delivery Assessment and Accounting;
  c) Offers various views to fully describe the architecture, including, but not necessarily limited to
    i. Physical View
    ii. Communication View
    iii. Service View
    iv. Information View
    v. Enterprise View
  d) Defines a framework for addition or modification of services offered;
  e) Is coordinated  with the CSS CSTS and CSSM draft recommendations;
  f)    Addresses the above, as applicable, from both a link-layer and inter-networked cross support perspectives.

Interagency Operations Advisory Group (IOAG)

DRAFT GUIDANCE DOCUMENT FOR
SPACE OPERATIONS STANDARDS

CROSS SUPPORT SERVICE ARCHITECTURE
(June 2007)

There are no patents and associated licensing concerns.

From a technical perspective the most significant risk is the scoping and attainment of common conceptual models among the participants of the various agencies.  .  Alignment of the architecture definition with  scenarios and use cases from member agencies and IOAG serves as a risk mitigation.
The demonstration that the scenarios and use cases are accommodated within the architecture will help validate the architecture developed. Furthermore, it is expected that each agency will check that the standards developed are technically applicable with respect to processes, political environment, and current implementation and future implementation plans.

Lack of resources or reassignment of previously-committed personnel is a constant risk to all standards-making processes. Risk for this WG is minimized by keeping the number deliverables to a minimum, i.e. one Green Book and one Magenta Book.