cesg-104 November 2009

CESG FALL 2009:items brought to attention

of the CMC

cesg-2

IOAG-13 Communiqués

to CCSDS

cesg-3

To: CCSDS Secretariat From: IOAG Secretariat Subject: IOAG-13 Liaison Statement The Interagency Operations Advisory Group (IOAG) held its 13th annual meeting on 22-24 September, 2009. During this meeting, the delegates of the IOAG received presentations from the Consultative Committee for Space Data Systems (CCSDS) that were provided by its liaisons.

In response to these presentations, the IOAG makes the following observations and requests to the CCSDS:

1. IOAG thanks the CCSDS Spacecraft Monitor and Control Working Group (SM&C) for its presentation of current efforts to develop a top level space mission operations service architecture. The IOAG invites the CCSDS to submit its “Mission Operations Services Concept” Green Book to the IOAG for study by the IOAG agencies, with a view to determining if the scope of the IOAG should be expanded in the future to embrace a potential “IOAG Service Catalog 3” that would cover Mission Operations applications. The IOAG also asks the CCSDS to study whether the current CCSDS work could be expanded to embrace the production of a “Service Oriented Architecture (SOA) for Space Missions.”

2. IOAG requests that an update to the channel coding blue book should be processed whenever an LDPC code is ready for publication, in association with its mission profile(s).

3. IOAG asks the CCSDS to assume responsibility for producing a Solar System Internetwork (SSI) Architecture Definition Document in response to the SSI Operations Concept to be delivered by IOAG to CCSDS in May 2010), in time for an IOP-3 that is anticipated not earlier than 2012.

4. As a complement to the IOAG response letter to the CMC dated June 23, 2009, for clarification of the standards to be produced in answer to resolution R 12.9.1, and on the particular subject of the “ancillary services,” the IOAG recommends that some new standards be produced by CCSDS according to the time frames indicated in the attached table.

01 October 2009

1. IOAG Communiqué of 01 October 2009

cesg-4

DESCRIPTION OF SERVICES TO BE CONSIDERED BY THE CMC FOR THE DEVELOPMENT OF FUTURE STANDARDS IN THE DOMAIN OF CROSS SUPPORT

CORRESPONDING RESOLUTION OF IOAG 13, WITH INDICATION OF THE REQUIRED TARGET DATE FOR COMPLETION, WHEREVER APPLICABLE

1 A ground-based space link monitoring cross-support transfer service standard

IOAG resolves to ask the CCSDS to develop a standard for a protocol to transfer space link monitoring data from ground communication assets to their users. The purpose is to exchange a limited set of ground station parameters in cross support operations.The IOAG further resolves that this standard should be available by the end of CY2011.

2 A ground space link control cross-support transfer service standard

IOAG resolves that an online service to control the ground space link is not needed for transfers in cross-support operations and that the service provided by the CSSM standard is estimated to be sufficient.

3 A data relay standard for: a) requesting the acquisition of; and, b) transferring remote orbiter-derived Doppler observables and orbiter trajectory and clock information to support landed vehicle position determination

IOAG resolves that it recognizes the need to acquire and transfer remote orbiter-derived Doppler observables and orbiter trajectory and clock information to support landed vehicle position determination. The IOAG further resolves that this is of medium priority and that availability of a standard is requested by the end of CY2012.

4 A data relay standard for: a) requesting the acquisition of; and, b) transferring remote orbiter-derived open-loop recording and digitization of Entry, Descent and Landing (EDL) signals

IOAG resolves that it recognizes the need to acquire and transfer remote orbiter-derived open-loop recording and digitization of Entry, Descent and Landing (EDL) signals. The IOAG further resolves C that this is of medium priority and that the availability of a standard is requested by the end of CY2012.

5 A data relay standard for: a) requesting the acquisition of; and, b) transferring remote orbiter-derived orbiter clock calibration and proximity time correlation data to support landed vehicle time correlation

IOAG resolves that it recognizes the need to request and transfer remote orbiter-derived orbiter clock calibration and proximity time correlation data to support landed vehicle time correlation. The IOAG further resolves that this topic is of moderate importance and needs further engineering assessment. Availability of a standard before the end of CY2014 is not needed.

6 An end-to-end standard for correlating space vehicle clocks and distributing time synchronization information

IOAG recognizes the need to develop a set of standards for correlating space vehicle clocks and distributing time synchronization information. The IOAG resolves that this topic needs further engineering assessment and that various mission scenarios should be identified, possibly with different priority levels for standards development. Availability of a standard before the end of CY 2014 is not needed.

7 A space-based data relay cross-support transfer service standard for monitoring the performance of remote space-space links

IOAG resolves to ask the CCSDS to develop a standard for acquiring and transferring space-to-space link monitoring data in order to exchange a limited set of parameters in cross support operations between, typically, rover and orbiter control centers The IOAG further resolves that this is of medium priority and that the availability of a standard is requested by the end of CY2012.

8 A data relay pass planning service for exchanging, e.g.; orbiter geometrical data slant range; off-pointing angle from antenna boresight; relative velocity of orbiter; orbiter elevation seen from the surface element; AOS & LOS times; etc.

The IOAG resolves to request the CCSDS to define an interface standard for transferring contact planning information concerning TT&C services to be provided by a relay orbiter to remote landed or descending space vehicles, including the interface protocol and parameters required for the contact planning and contact plan generation. . Availability of a standard before the end of CY2014 is not needed.

cesg-5

1. The CESG has formed a BOF which has the task of identifying the charter and program of work for a Working Group to develop a top-level CCSDS reference/service architecture• The CESG will transmit the MOIMS “Mission Operations Services Concept” Green Book to IOAG as soon as it

has been updated to reflect recent RIDs.

2. The LDPC codes have been sent for Agency Red-1 review3. The CESG is studying how to create the SSI Architecture in time for IOP-3. The CESG understands

the intention of the IOAG to produce a layered set of service catalogs and asks the IOAG to confirm that the context of the SSI Architecture is the architecture for Service Catalog-2, as indicated below:

CESG Analysis of IOAG-13 Communiqué [1]

IOAG Service Catalog 1

CCSDS Cross Support Service

Architecture

IOAG Service Catalog 2

CCSDS Solar System

Internetwork Architecture

IOAG Service Catalog 3

CCSDS Mission Operations

Service Architecture

cesg-6

4. With respect to the CSTS Space Link Monitoring Service requested by the IOAG (end CY 2011), this is already in the CCSDS program of work.

5. With respect to the four data relay standards requested by the IOAG, the CESG has concerns that this could result in a very heavy standardization effort for a relatively small (Mars relay) market:• A data relay standard for: a) requesting the acquisition of; and, b) transferring remote orbiter-derived Doppler

observables and orbiter trajectory and clock information to support landed vehicle position determination (end CY 2012)

• A data relay standard for: a) requesting the acquisition of; and, b) transferring remote orbiter-derived open-loop recording and digitization of Entry, Descent and Landing (EDL) signals (end CY 2012)

• A space-based data relay cross-support transfer service standard for monitoring the performance of remote space-space links (end CY 2012)

• A data relay standard for: a) requesting the acquisition of; and, b) transferring remote orbiter-derived orbiter clock calibration and proximity time correlation data to support landed vehicle time correlation (end CY 2014)

The initial CESG thought is to standardize just the containers (e.g., the mechanisms for formatting the information) and the transfer mechanisms for passing the information between ground and space (e.g., CFDP, AMS, etc.) but not the semantics of the information being transferred. The semantics might be standardized later by MOIMS as part of Service Catalog-3. The CESG seeks more IOAG guidance on this point.

6. With respect to the time correlation and clock synchronization standard requested by the IOAG (end CY 2014) , CCSDS has created a BOF to study this topic.

7. With respect to the data relay pass planning standard requested by the IOAG (end CY 2014), CCSDS proposes to defer this item until the scope of Service Catalog-3 is better understood.

CESG Analysis of IOAG-13 Communiqué [2]

cesg-7

IOAG Service Catalog-1

• IOAG has adopted the notion of a phased set of services that Agencies will be asked to cross support:• Catalog-1: consolidation of space link services (now -2015)• Catalog-2: addition of Internetworking services (2015 – 2020)• Catalog-3: (possible) addition of Mission Operations services (2020+?)

• Catalog-1 was agreed at IOAG-13• “Core” (shaded) and “Extended”• Standards gaps exist; IOAG is still voting on priorities to send to CCSDS

2. Untransmitted IOAG Communiqué re: Service Catalog 1 “gap fillers”

cesg-8

IOAG Service Group IOAG Service TypesSpace Link Interface

Standards

Ground Link Interface

Standards

Forward Data Delivery Services

Forward CLTU Service

Radio Frequency and Modulation [RFM]

TC Synchronization and Channel Coding [TC-S&C]

SLE Forward CLTU Service [CLTU]

Forward Space Packet Service

Those for “Forward CLTU Service” plus: TC Space Data Link

Protocol [TC-DLP] Communications Operation

Procedure-1 [TC-COP]

SLE Forward Space Packet Service [FSP]

Forward AOS Frame Service

Radio Frequency and Modulation [RFM]

TM Synchronization and Channel Coding [TM-S&C]

AOS Space Data Link Protocol [AOS]

SLE Forward AOS Frame Service [FAOS]

Forward File Service

Those for “Forward CLTU Service” and/or “Forward AOS Frame Service” plus: Space Packet Protocol

[SPP] Encapsulation Service

[ENC] CCSDS File Delivery

Protocol [CFDP]

CSTS Forward File Service [CFFS], over

CSTS Transfer File Service [CFXS]

IOAG Service Catalog-1: Forward

cesg-9

IOAG Service Catalog-1: ReturnIOAG Service Group IOAG Service Types Space Link Interface

StandardsGround Link

InterfaceStandards

Return Data Delivery Services

Return All Frames Service

Radio Frequency and Modulation [RFM]

TM Synchronization and Channel Coding [TM-S&C]

SLE Return All Frames [RAF]

Return Channel Frames Service

Those for “Return All Frames Service” plus: TM Space Data Link

Protocol [TM-DLP] AOS Space Data Link

Protocol [AOS]

SLE Return Channel Frames [RCF]

Return Operational Control Field Service

Those for “Return Channel Frames Service”

SLE Return Operational Control Field [ROCF]

Return Unframed Telemetry Service

Those for “Return All Frames Service”

CSTS Return Unframed Telemetry [RUTM]

Return File Service

Those for “Return Channel Frames Service” plus: Space Packet Protocol

[SPP] Encapsulation Service

[ENC] CCSDS File Delivery

Protocol [CFDP]

CSTS Return File Service [CRFS] over

CSTS Transfer File Service [CFXS]

cesg-10

IOAG Service Catalog-1: Radio Metric

IOAG Service Group IOAG Service Types

Space Link Interface

Standards

Ground Link Interface

Standards

Radio Metric Services

Validated Data Radio Metric Service

Radio Frequency and Modulation [RFM]

Pseudo-Noise (PN) Ranging Systems [PNR]

CSTS Offline Radio Metric Service [CORS] over

CSTS Transfer File Service [CFXS]

Raw Data Radio Metric Service

Those for “Validated Data Radio Metric Service”

CSTS Real Time Radio Metric Service [CRTRM]

Delta DOR Service

Radio Frequency and Modulation [RFM]

Delta-Differential One Way Ranging (Delta-DOR) Operations [DDORO]

CSTS D-DOR Data Service [DDORS] over

CSTS Transfer File Service [CFXS]

cesg-11

CSTS File Transfer ServiceCSTS Forward File ServiceCSTS Return File ServiceCSTS Offline Radio Metric ServiceCSTS Real Time Radio Metric ServiceCSTS Delta DOR ServiceCSTS Engineering Data Monitoring Service SLE Forward AOS Frame Service SLE Return Unframed Telemetry Service

IOAG Service Catalog-1: Gap Analysis

• CESG understands that IOAG is still not in agreement on the priorities to assign for CCSDS to develop these standards.

• CESG interprets the “CSTS File Transfer Service” as some sort of secure terrestrial file transfer which then gateways into CFDP-based “CSTS Forward File Service” and “CSTS Return File Service” as Extended Services for single space/ground link transmission. This appears to be related to IOAG R12.9.1 and subsequent discussions. We request confirmation from the IOAG Service Catalog-2 and SISG activities on this point.

cesg-12

• Considering that:• The CCSDS received the Liaison Statement from IOAG-12, dated 10 September 2008.• The CCSDS did not respond to this Liaison Statement at its October 2008 meeting in view of the upcoming IOP-2.• CCSDS needed to analyze the intent of Resolution R12.9.1 after IOP-2.

• And recognizing that:• Accordingly, CCSDS convened an ad-hoc technical group from 21-23 April in Colorado Springs in order to analyze and clarify the

intent of R12.9.1• Technical consensus was reached by that group and was reported to the CCSDS Management Council

• The CCSDS Management Council resolves that it interprets the intent of R12.9.1 as follows:• For missions that may need to conduct file transfer over a single space/space link, CCSDS is requested to develop a Recommended

Practice that defines the profile of CCSDS standards required to operate CFDP over Space Packet over a single Proximity-1 link.• For missions that may need to conduct file transfer over a single ground/space link, CCSDS is requested to develop:

a) a Recommended Practice that defines the profile of CCSDS standards required to operate CFDP over Space Packet over a single TM/TC/AOS link;

b) a cross-support standard for transferring files between ground communications complexes and ground users to support a variety of applications, including emergency commanding

• CCSDS is requested to initiate the development of an end-to-end networked communications architecture:a) by developing Recommended Standards for the DTN suite and Recommended Practices for its deploymentb) by developing a Recommended Practice for the deployment of the IP suitec) by evaluating the potential need for CSTS ground/ground specifications for [forward and return Space Packet] and [forward

and return Encapsulation Packet] in the context of this work • The CCSDS Management Council further notes that R12.9.1 also defines a need for a space link monitoring cross-support transfer

service standard (which has been accepted into the CCSDS Program of work) and for an interagency routine file transfer service (which is addressed above). However, the Resolution also asks for a standard for “time synchronization services” and this is not well-understood by CCSDS. The IOAG is therefore asked to clarify its needs for ancillary data standards.

“IOAG 12 Liaison Statement to CCSDS” (dated 10 September 2008) also contained a Resolution R12.9.1 that was unclear to CCSDS. In May 2009 the CCSDS Management Council responded to the IOAG as follows:

IOAG R12.9.1[1] – CCSDS Request for Clarification

cesg-13

Illustrative scope of proposed R12.9.1 developments

CFDP

CFDPSpace Packet

Prox-1

CFDP over Proximity Link Magenta Book

A

B

CFDP

CFDP

Space Packet

TM/TC/AOS

CFDP over Space LinkMagenta BookCross-Support Ground File Transfer

Blue Book

A

A

BPlus existing CSTS Services• Return All Frames• Return Channel Frames• Forward CLTU ( Forward AOS)

cesg-14

The IOAG also confirms its acceptance of the proposed standardization activities, i.e., 1) Best Practice for CFDP over a single space to space link (Prox-1); 2) Best Practice for CFDP over a single ground to space link (TM/TC/AOS); and,3) Standard for bidirectional ground File Transfer for a variety of applications.

However, IOAG understanding of the proposed CCSDS standard on file transfers is that it shall cover all types of file transfers, i.e., for the single ground/space link and for the single space/space link. It shall also cover the file transfers for the single space/space link for the purpose of Emergency Commanding and Essential Telemetry. This understanding is to be confirmed in the CCSDS resolution.

The IOAG acknowledges that CCSDS plans to initiate the evaluation and/or the development of best practices and standards for an end-to-end networked communications architecture.

Finally, the IOAG agrees to revisit and clarify its requirements for standards on ancillary data and

will conduct some inventory and definition work to be presented, tentatively for endorsement, at the upcoming IOAG-13, which is planned for 22-24 September, 2009.

R12.9.1[2] – IOAG clarification back to CCSDS

In June 2009 the IOAG responded to the CCSDS as follows:

CCSDS advises the IOAG that the status of this resolution is shown in Table 2.

cesg-15

1. Magenta Book: “CFDP over TM/TC/AOS”

Awaiting draft Working Group charter and commitment of resources from ESA. Need for interoperability testing is under discussion in CCSDS.

2. Magenta Book: “CFDP overProx-1”

Awaiting draft Working Group charter and commitment of resources from ESA. Need for interoperability testing is under discussion in CCSDS

3. Blue Book: “Ground-Ground File Transfer” cross-support transfer service

Recommended Practice book (Magenta) on use of Secure FTP (SFTP) to transfer files and framework (syntax) for metadata targeted for Oct 2011 release. However, if standardization of the semantics of the metadata for end-end file transfer and emergency TM/TC cross support is now required by the IOAG then scope of work is unknown and resources need definition. Will form BOF at CCSDS Fall 2009 meeting to discuss.

Blue Book: “Space Link Monitoring” cross-support transfer service

Red-1/start of Agency reviews anticipated as output from Oct 2009 meetings

Blue Book(s) and Magenta Book(s) for the DTN suite

Concept papers for (a) Bundle Protocol and (b) LTP, as well as Draft Green Book, are in DTN Working Group review; plan is to issue Red-1 after Fall CCSDS meeting, after requirements update from SISG

Magenta Book for the IP Suite Working Group expected to be chartered at Fall 2009 CCSDS meeting, assuming allocation of NASA Constellation program resources

Evaluate potential need for CSTS ground/ground specifications for [forward and return Space Packet] and [forward and return Encapsulation Packet]

Future study.

Ancillary Standards Awaiting further IOAG input.

R12.9.1[3] – current CCSDS status

Table 2

cesg-16

IOAG R12.9.1[4] – Current Status

• CESG notes that the strategies for evolving from IOAG Service Catalog-1 to IOAG Service Catalog-2 are still under discussion in the IOAG Space Internetworking Strategy Group (SISG)

• A SISG work plan has been developed which corresponds to a bilateral ESA/NASA management recommendation• The SISG has agreed in principle on the envisioned Solar System Internetwork (SSI) for

2020• Issues concern the evolution and the implementation/operation of the final SSI• Work plan to resolve the issues is established to accomplish:

- SSI Operations Concept by 15 May 2010- Draft IOAG Service Catalog #2 (Draft 0 by 15 Dec 2009)- SSI Requirements Draft 0 by 23 Oct 2009 (discussed at DTN Working Group meeting)

• IOAG plans to hand over an agreed SSI Operations Concept to CCSDS in May 2009 for CCSDS to take over the SSI Architecture development

Nov 2009 Jan 2010 Apr 2010DOCUMENTS

SSI Operations Concept D1 V1Service Catalog #2 Draft D1SSI Requirements Draft D0 D1

SSI ISSUE RESOLUTIONIssue 1Issue 2Issue 3Issue 4Issue 5Issue 6Issue 7Issue 8Issue 9

MEETINGSVITSFace-to-Face Meeting

May 2010Sep 2009 Dec 2009 Mar 2010Feb 2010Oct 2009

Recommendation: allow these evolutionary issues to play-out in the SISG forum until Spring 2010

cesg-17

Other Issues and Concerns

from the

Fall 2009 CESG meeting

cesg-18

• CESG would appreciate early publication of the updated CCSDS Procedures Manual.

• CESG notes that the PAIMAS and OIAS models were originally published as Recommended Standards (Blue Books) but advises the CMC that in view of their technical content they should be moved to the Recommended Practice (Magenta) branch of the Standards Track now that they are being reconfirmed and updated.

• CESG notes that the “Requirements for Bodies Providing Audit and Certification of Digital Repositories” Red Book is ready for Agency review. The working group wants to get a parallel ISO review in order to get a wider set of comments. This creates a problem because the asynchronous ISO/CCSDS review schedules will hold up the CCSDS work. One possibility is to do one or more CCSDS reviews and then circulate the mature CCSDS Red Book to ISO as an FDIS.

• CESG notes that the SANA Working Group is almost ready to disband and that NASA has secured initial funding to implement the SANA Operator. However, it is not clear where the permanent SANA organizational and funding home will be: IOAG? CCSDS?• This is a very important operational function fore future international cross support and it needs

a permanent and stable parent.

CESG General Issues/Concerns [1]

cesg-19

• CESG notes the US patent question concerning the SCCC channel code and believes that until this is resolved the “fair and non-discriminatory” requirement is not met and that this therefore prevents the document from moving forward:• ESA believes that the Agency review should go ahead even though there is an unresolved

legal taint

• CESG notes the BOF proposal to move the ECSS “PUS” standards into CCSDS:• The PUS standards need updating to reflect the overall updating of the underlying Packet books

that has taken place in recent years• The proposal is for CCSDS to undertake that updating• The CESG notes that a possible eventual end-state of the PUS will be to separate the mission

operations services embodied by them from the underlying Space Packet Protocol, in which case those mission operations services may become part of the SM&C suite

• Elements of the CESG advocate that the ECSS should first update the PUS, then separate the mission operations services and then introduce those services to CCSDS via proposed extension of the SM&C services. Other international agencies should also be encouraged to bring forward their spacecraft monitor and control approaches for potential standardization. This strategy would also allow time for the overall CCSDS service framework to be clarified.

• Such a move would also have impact on SOIS services, which would require updating.

CESG General Issues/Concerns [2]

cesg-20

• CESG strongly advocates that CCSDS needs an overall reference architectural framework into which all of its work can be aligned in terms of services and standards, and that it also needs a consistent way to express how those services should be defined and specified. CESG recommends that the CMC should endorse the “way forward” proposal made by the CSS Area:

• CESG notes that this activity is likely to need temporary redirection of resources from several information architecture-related activities in MOIMS and SEA, including SM&C• Current work cannot totally stop• Question of where eventual WG would be located?• CESG Chair files a “friend of court” brief that – as the major stakeholder in the outcome –

SM&C should be given this job

CESG General Issues/Concerns [3]

Team-1: Services, Scenarios, Framework

Team-2: Service Definition Technology28 Feb 10

WG ConceptWG

FormedMay 09

cesg-2104 November 2009