ccsds engineering group: report to the

CCSDSCCSDSEngineering Steering Group:Engineering Steering Group:

RReporteport to theto theRReport eport to theto theCCSDS Management CouncilCCSDS Management Council

ESTEC, Noordwijk, NL

04 November 2009

cesg-104 November 2009

04 November 2009

CCSDS CCSDS OverviewOverview

53+ 53+ StandardsStandards

420+ missions420+ missions


CCSDS Working GroupsCCSDS Working Groups Systems ArchitectureSecurityInformation ArchitectureSpace Addressing and NamingDelta‐DOR

dSystemsEngineering

SystemsEngineering Time Code Formats

XMLRegistries/Repositories

MCC

EngineeringEngineering

MCC

CrossSupportS i

Spacecraft OnboardInterface

Mission Ops& Info. Mgt.S i

SpaceInternetworkingS i

SpaceLinkS i

Cross SupportServices

Spacecraft OnboardInterface Services

Mission Ops& Info. Mgt.S i

SpaceInternetworking

S i

Space LinkServices

Onboard Subnet. Services Onboard Application ServicesWireless WG

RF & Modulation Space Link Coding & Sync. Multi/Hyper Data Compress.Space Link Protocols Ranging High Rate Uplink

CS Service ManagementCS Transfer ServicesCross Support

Space Packet ProtocolAsynchMessagingIP‐over‐CCSDS LinksMotion Imagery & AppsDelay Tolerant Networking

Data Archive IngestionNavigation Info. Pack. & RegistriesSpacecraft Monitor & Control

ServicesServices ServicesServicesServices Services ServicesServicesServices

cesg-3

Onboard Plug‐n‐Play High Rate UplinkSpace Link SecurityLong Erasure CodesPlanetary Surface Comm.Optical Modulation/Coding

Architecturey g

VoiceControlDigital Repository Audit/CertificationESA‐PUS

37 Working Groups, 104 Projects= forming

04 November 2009

CESG CESG REPORT OUTLINEREPORT OUTLINE

• Spacecraft Onboard Interface Services (SOIS) A

By Area:

A. CURRENTLY ACTIVE WGs, SIGs and BOFs

B. MEETING DEMOGRAPHICS

Area

• Space Link Services (SLS) Area

• Cross Support Services (CSS) Area

• Space Internetworking Services (SIS) Area

C. SUMMARY TECHNICAL STATUS OF EACH WG & BOF

D. CROSS‐AREA MEETINGS

E. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD

• Mission Operations and Information Management Services (MOIMS) Area

• Systems Engineering Area (SEA)

• Meeting Statistics, CESG Resolutions


CONCERNS IN LAST REPORTING PERIOD

SPACECRAFT ONBOARDSPACECRAFT ONBOARDSPACECRAFT ONBOARD SPACECRAFT ONBOARD INTERFACES SERVICESINTERFACES SERVICES

(SOIS) AREA(SOIS) AREA

Chris Taylor (AD)Stuart Fowell (DAD)


A

Spacecraft Onboard Interface Services Area ReportSpacecraft Onboard Interface Services Area Report

1. Application Support Services WG (including Plug & Play)

A. CURRENT GROUPS WITHIN AREA

1. Application Support Services WG (including Plug & Play)

2. Subnetwork Services WG (work terminating)

3 Wireless WG3. Wireless WG





SOIS

Plenary Wireless WG APPs support WG Plenary

ASI

BNSC 1 2 1

CNES

CSA

FSA

DLR

ESA 10 3 6 5

RSA 2 2 2

JAXA

USA 5 5 4

Total 18 8 14 8

MeetingDuration

0.5 2.5 4 0.5


AgencyDiversity

4 3 4 4

C. SUMMARY TECHNICAL STATUS


1. Application Services Working Group

Goal: Develop SOIS Application support layer services and associated protocols if required


q

Working Group Summary progress:

• Three Red books under prep for final Agency review

• Three Red Books under WG updateThree Red Books under WG update

• One Red book related to plug & play blocked until decision on how to proceed

• First ESA prototype completed, 2nd initiated,

• Liaison with external groups (ECSS and SpaceWire WG SAVIOR)Liaison with external groups (ECSS and SpaceWire WG, SAVIOR)

Problems and Issues:

• Need to agree a way forward on Plug and Play

Working Group Summary Situation: Some resource limitations

status: OK CAUTION PROBLEM


comment: Prototyping ongoing P&P

Application Services Working Group


pp g p• Plug and Play

• Dedicated session held on P&P came to the following main conclusions:• P&P is of high interest and is also being worked by a number of external

b t i t l id d t ll A i t thgroups but scope is extremely wide and not all Agencies are at the same level of progress, or have the same immediate objectives

• The full scope of P&P affects not only SOIS but other CCSDS areas (mainly MOIMS)

• Within the overall context there is common agreement on a subset which is applicable to the present scope of SOIS

• This focuses on achieving interoperability for discovering devices and their capabilities using a standardized format based on Electronic Data sheetscapabilities, using a standardized format based on Electronic Data sheets (EDS)

• IEEE 1451 TEDS and XTEDS are candidate capability descriptions and are proposed for detailed work

• To minimise resources it is proposed to slightly extend the charter of the APPS to cover P&P for the enumeration service,

• Resources: ESA, BNSC OK, commitment required from NASA and other Agencies if possible


g p


Application Support WGWorking Group Planning:

Task/Milestone Description Date

Forward TAS to CESG for final check and publication December 09

Update and release MTS and FPSS Red books for 2nd Agency review December 09

Update charter to absorb P&P November 09

Adjust work plan for remaining books according to decisions on plug and play decisions and resources (All but Enumeration service)

November 09

Perform EDS analysis and determine end-date for enumeration service April 2010

Continue prototyping End 2010

Continue monthly telecons


2 Subnetwork Services Working Group


2. Subnetwork Services Working GroupGoal: Develop SOIS Subnetwork Services and associated protocols if requiredWorking Group Summary progress:• Agency review for all subnetwork red books completed• Agency review for all subnetwork red books completed• CESG “quality” checks required editorial updates, under update • Latest status to be reflected in Green Book• ECSS developing compliant protocols for Milbus (available), CanBUS (in p g p p ( ), (

progress) and SpaceWire (planned)

Working Group Summary Situation: To be terminated when Magenta books are publishedpublished


h d f


comment: Finished after editorial update

3 Wireless WG


3. Wireless WGGoals: CCSDS focus group for wireless technologies. Make recommendations

pursuant to standardization of applicable wireless protocolsWorking Group Summary progress:g p y p g• Green book finished and under publication process• Magenta Books on schedule for:

• Asset management (RFID) Magenta book contents baselined• Spacecraft (sensor networks) Magenta book contents baselined

• Evaluation activities initiated for candidate specificationsProblems and Issues:

Th b dth f li ti f i l t h l diffi lt t t i (The breadth of application of wireless technology, difficult to categorise (same technology has many different uses). Magenta format needs to allow evolution.

Working Group Summary Situation:



comment: Very Good


Wireless WGWorking Group Planning: RFID


RFID-Based I/M MB out for informal internal review 15-Jan-2009

Informal RFID-Based I/M MB review period complete 01-Mar-2010Informal RFID Based I/M MB review period complete 01 Mar 2010

MB publication preparation for agency review complete; out for Agency Review 01-May-2010

Agency review complete 15-Jun-2010

Disposition of RIDS 15-Jul-2010

RFID-Based I/M MB publication and release 01-Sep-2010



Wireless WGWorking Group Planning: Spacecraft


Drafting of the standard testing methodology and metrics for the MB; document to ensure proper comparisons

15-Jan-2010

Agency testing on 802.15.4, ISA100, WirelessHART complete and technology trade-off

15-Mar-2010

Incorporate supporting test data into Spacecraft MB 30-Mar-2010

Spacecraft MB initial draft 15-Apr-2010


D C A M ti


D. Cross Area Meetings• Joint SOA BOF

• Reported elsewhere• Introduction of SOA would assist SOIS particularly in area of plug an play where a global• Introduction of SOA would assist SOIS particularly in area of plug an play where a global

architecture is necessary to ensure success of individual developments• SOIS App support services will probably be affected and some extensions may be

necessary, • Close cooperation required

• Joint SM&C (including PUS BOF)• Reported elsewhere• May have significant impact on SOIS and vice versa as SOIS services would form part of the

onboard architectureC id d i i b k i• Considered positive but more work necessary to assess impact

• Joint AMS Meeting• The AMS subset being used by SOIS is complete and AMS RB has completed Agency

reviewreview• Interoperability testing discussed and technically possible but currently no budget

• Joint SLS Meeting (Planetary comms SIG/SOIS wireless WG)• Reported elsewhere





• Application Services WG• Time Access service Red book 2 in prep for final Agency review• File and Packet Store Red book 2 in prep for final Agency reviewp p g y• Message Transfer service Red book 1 in prep for final Agency review• Device Access service Red book 2 depends on P&P progress• Device Data Pooling service Red book 2 depends on P&P progress• Device Virtualisation Service Red Book 1 depends on P&P progress• Device Virtualisation Service Red Book 1 depends on P&P progress• Enumeration service Red Book 1 depends on P&P progress

• Subnetwork Services WGk i di i l d b f bli i• Packet service Editorial update before publication

• Test Service Editorial update before publication• Memory Access service Editorial update before publication• Device Discovery Service Editorial update before publication• Synchronisation service Editorial update before publication• Green Book Version 2 under preparation

• Wireless


• Green Book Completed, in publication process• Magenta Books Initiated

SPACE LINK SERVICESSPACE LINK SERVICESSPACE LINK SERVICESSPACE LINK SERVICES(SLS) AREA(SLS) AREA

Jean‐Luc Gerner (AD)Gilles Moury (DAD)


Space Link Services Area Report

A. CURRENTLY ACTIVE WGs, BOFs & SIGs WITHIN AREA

1. RFM WG Radio Frequency & Modulation

2. RNG WG Ranging

3. C&S WG Coding & Synchronisation

4. LEC BOF Long Erasure Codes

5. SLP WG Space Link Protocols

NGUWG G i U li k6. NGU WG Next Generation Uplink

7. MHDC WG Multi/Hyperspectral Data Compression

8 SDLS WG Space Data Link Security (Joint with SEA)8. SDLS WG Space Data Link Security (Joint with SEA)

9. PlaCom SIG Planetary Communications

10 OCM SIG Optical Coding & Modulation


10. OCM SIG Optical Coding & Modulation

X

Space Link Services Area Report

B. STATISTICS


SLS REPORT

C. SUMMARY TECHNICAL STATUS1. RFM WG

Goal (deadline October 2009):

C SU C C S US

Initial studies on 8PSK, 16-APSK, 32-APSK and 64-APSK in support of coding and synchronization WG;

Review Prox-1 Physical layer (211.1-B-3) book and extract idle pattern sections for C&S layer book;

White recommendation on HR telemetry and PN ranging;

Red recommendation on 2 GHz modulation for missions supported by data relay satellites;

Working Group Status: Active

White recommendation on comms requirements in emergency;

White recommendation on 22 GHz modulation.Working Group Status: Active

Working Group Summary Situationstatus: OK CAUTION PROBLEM

comment: Good progress



SLS REPORT

RFM WGSUMMARY TECHNICAL STATUS

Working Group Summary Situation (October 2009):

Studies on 8PSK, 16-APSK, 32-APSK and 64-APSK in support of coding and synchronization WG completed;coding and synchronization WG completed;

Review of Prox-1 Physical layer (211.1-B-3) book completed; revised (white) book - planned for February 2010 - to remain in WG iti th P 1 b k iWG awaiting other Prox-1 books review;

Initial studies on HR telemetry and PN ranging available;

Red recommendation on 2 GHz modulation for missions supported by data relay satellites technically agreed (requires fixing formatting/editorial problems).


SLS REPORT

RFM WG

Working Group identified need for following additions to charter:

Revision to HR telecommand rec to support the NGU file upload profile (minor effort);Study and definition of flexible turn-around ratios to support MSPA requirement by NGU (major effort in cooperation with SFCG);Green Book on 2 GHz modulation for missions supported by data relay satellites.y

Working Group identified need for following revision to charter:

Delay HR telemetry and PN ranging milestones (twoDelay HR telemetry and PN ranging milestones (two solutions with many different options under evaluation);Delay 22 GHz and emergency comms milestones (no inputs).


SLS REPORT

2. RNG WG

Goal (deadline October 2009): Issue Green Book on PN rangingGoal (deadline October 2009): Issue Green Book on PN ranging techniques.




Working Group Summary Progress:


Working Group Summary Progress:Green Book on PN ranging techniques technically agreed (twoindependent editorial reviews initiated – book planned to bereleased by end of December).


Note: expected to disband WG as soon as GB approved by CMC.

3 C&S: Coding & Synchronization WG

SLS REPORT

3. C&S: Coding & Synchronization WG

• Working Group Status: Active

• Working Group Summary Situation:


comment: X

• Working Group Summary progress :

See next slides


C&S C di & S h i ti WG W ki G S

SLS REPORT

C&S: Coding & Synchronization WG - Working Group Summary progress Revision of CCSDS 131.0-B-1 TM Synchronization and Channel Coding (LDPC

Codes addition & Five Years Review )Pink Sheets finalizedCMC poll for starting Agency Review is ongoing.CMC poll for starting Agency Review is ongoing.

LDPC CodesOngoing implementation activities have been presented and discussed.

LDPC Codes for Proximity-1NASA ask to add new coding option to Proximity-1. g p yMore input documentation (trade-offs) expected.Agencies to evaluate proposal.

SCCC StandardizationStandardization of the modulation items approved by the RFM Working GroupGroup.C&S and RFM WGs agreed to keep this specification within a single book including both coding and modulation aspects.RESOLUTION SLS-C&S-200910-01: The WG resolves to request the SLS Area Director to pass the SCCC to the standardization track and start Agency Review with a proviso of resolution at CESG/CMC of patent issueAgency Review with a proviso of resolution at CESG/CMC of patent issue

Outcomes of SLS Plenary: Patent issue closed (see annex)DVB-S2 Standardization

CNES proposal: develop a standard for AOS data link protocol over DVB-S2 links; to be submitted to C&S WG by Spring meeting

AOB


AOBAt Plenary, it was concluded that licences on patented technologies shall be available on a fair and non-discriminatory basis

C&S: Coding & Synchronization WG - Working Group Summary progress

SLS REPORTg y g p y p g

Revision of CCSDS 231.0-B-1 TC Synchronization and Channel Coding. Blue Book. (Introduction of TC Repeated Transmission)

Proposed changes and resolution approved.p g ppCoordinated resolutions in SLP on TC SDLP and COP-1RESOLUTION SLS-C&S-200910-01: the WG resolves to request the SLS Area Director to start Agency Review for the Pink Sheets for CCSDS-231.0-B.

Silverization of PLOP-1? (may slightly delay resolution above)NASA proposal to remove PLOP-1 from the book agreed in principleNASA proposal to remove PLOP-1 from the book agreed in principle. Modalities of removal under discussion

Turbo Codes Attached Sync Marker rates ¼ and 1/6Proposal for better performance ASM under investigation (benefits, impacts)Pending above, the WG will decide about follow up activities :

Replace the two ASM’s in Blue Book with better ones, orComplement the two ASM’s in Book with better ones applicable to e.g. higher order modulations or low Eb/No scenarios (e.g. deep space)Report issues in Green Book.


C&S: Coding & Synchronization WG - Working Group Summary progress

SLS REPORTg y g p y p g

Channel Coding Green Book(s) update ongoingIn relation with BBs updates

Five Years Review CCSDS 211.2 Recommendation for Proximity-1 Space Link Protocol – Coding and Synchronization Sublayer

The activity has been extended to the other 2 books of Proximity-1 to ensure harmonized revision. Activity on going.

Long Erasure CodesDLR & NASA/JPL to provide a CCSDS Concept Paper for the creation of a CCSDS Project on Erasure CodesDecision on new CCSDS Project at Spring’10 meeting.j p g gUse of Long Erasure Codes over the CCSDS File Delivery Protocol (CFDP)considered promising

Action taken by WG chair to forward presentation to SISSLS AD to organize a joint session with SIS in Spring 2010.

Interaction with NGU WG• NGU requires the C&S WG to investigate a coding scheme for file upload:• The C&S WG charter shall be updated accordingly and a new project shall be

added in CWE


added in CWE.

4 SLS LEC L E C d BOF

SLS REPORT

4. SLS‐LEC: Long Erasure Codes BOF

• Goal:Make if conclusive a proposal for the creation of a WG on• Goal: Make, if conclusive, a proposal for the creation of a WG on application of long erasure‐correction codes.

• BOF Status : Closed

• BOF Summary Situation:status: OK CAUTION PROBLEM

comment: X

• BOF Summary progress:

comment: X

• Completed

• New project in preparation in C&S WG


SLS REPORT

5. SLS-SLP WG

Goal:• Progress TM AOS Space Data Link Protocol Pink Sheets to Blue (OID frame)* Hold due to FSH/Insert• Progress TM, AOS Space Data Link Protocol Pink Sheets to Blue (OID frame) Hold due to FSH/Insert

Zone/Security discussion

• Progress Encapsulation Service Pink Sheets (including SDLP Channel parameter) to Blue

• Progress Space Packet Protocol Pink Sheets to Blue book for APID defn. *(but locate pink sheets!)

Progress the TC AOS TM Prox 1 and SPP CRC pink sheets to Blue book* Hold due to FSH/Insert• Progress the TC, AOS, TM, Prox-1, and SPP CRC pink sheets to Blue book* Hold due to FSH/Insert Zone/Security discussion

• Progress Space Link Identifiers Pink Sheet ( including deprecation of IPv4) to Blue Book• Progress TC Space Data Link Protocol & COP-1 to Blue for Systematic Retransmission parameter

• Progress TC Space Data Link Protocol for CRC normalization and APID definition*

• Progress Prox-1 Space Data Link Protocol pink sheets to Agency Review (Source/Dest. Flag clarification)

• WG Status: Active X IdleWG Status: Active X Idle ____

WG Summary Situation:status: OK CAUTION PROBLEM

t G d


29


SLS REPORT

WG Summary progress:

• Encapsulation Service

SLS-SLP WG (cnt’d)

• Encapsulation Service Two Rids overlooked during agency review. Consensus of WG was to add the changes with the previously approved CESG/CMC changes for a new CESG/CMC poll.

• Space Link Identifiers R l f IPV4 k t i b t d b th WG i llRemoval of IPV4 packet version number was accepted by the WG, since all agencies polled approve of the deprecation. Consensus of WG was to add these changes with previously approved CESG/CMC changes for a new CESG/CMC poll.

• COP-1 and TC Space Data Link ProtocolC f WG t d t Bl f th t ti t i iConsensus of WG to advance to Blue for the systematic retransmission parameter

• Proximity-1 Data Link ServiceSource/Destination Flag text updated to reflect the description from both the receive and send side. Pink Sheets to go to Agency Reviewg g y

• FSH and Insert Zones Discussion on harmonizing FSH and Insert Zones in AOS, TC, TM, and Prox-1 occurred. NASA proposed that for at least AOS due to the need on Program Constellation, there is a sufficient need to place security Information into a new FSH for AOS (virtual channel based) and Insert Zone


30

( )when security is appropriate for the entire Master Channel.

SLS-SLP WG (cnt’d)

SLS REPORT

SLS SLP WG (cnt d)

Problems and Issues:• Several changes have piled up for AOS, TC, TM, SPP, Prox-1 specifications.

When we update these documents we need to ensure that all approvedWhen we update these documents we need to ensure that all approved updates occur at once.

• Conflict exists between NASA’s identified need to have a new FSH defined in the AOS Space Data Link Protocol to use for security and range safety data and the terming of this material as “not mature” by ESAand the terming of this material as “not mature” by ESA.

• SPP blue and green books do not belong to this WG. Apparently there are SPP pink sheets that no one can locate including the Secretariat. ESA has expressed concern that SPP pink sheets concerning APID definition needs to be expedited to blue To be coordinated with SISto be expedited to blue. To be coordinated with SIS

• Request from DTN WG to add 2 PIDs to Space Link Identifiers Blue book received at this meeting.

Planning :Planning :

• Continue to work with SDLS WG on defining where Security will be inserted into the CCSDS Space Data Link Protocols

• New task assigned by NGU WG to define the data link layer protocol for File Upload application profile – requires Charter update


31

File Upload application profile requires Charter update

SLS REPORTSLS-SLP WG (cnt’d)

Resolutions under preparation:

1. TM Space Data Link Protocol p- ‘OID’ Frame redefinition- CRC-16 implementation harmonization

2. AOS Space Data Link Protocol - ‘OID’ Frame redefinitionOID Frame redefinition- CRC-16 implementation harmonization

3. COP-1 & TC Space Data Link Protocol - Systematic retransmission

4 Proximity-1 Coding & Synchronization Sub-Layer (handled by C&S4. Proximity-1 Coding & Synchronization Sub-Layer (handled by C&S WG)

- CRC-32 implementation harmonization5. Encapsulation Service 6 S Li k Id tifi6. Space Link Identifiers 7. Space Packet Protocol Blue Book (to be handled by SIS)

- APID Definition- CRC-16 implementation harmonization


32

SLS REPORT

6. Next Generation Uplink WG

Goal:• Develop a Green Book for Next Generation Uplink (NGU) application

profiles.• Whenever needed and possible incorporate new requirements into

existing Blue books supported by the RF & Modulation Channelexisting Blue books supported by the RF & Modulation, Channel Coding & Synchronization, and Link Layer protocol WGs.

• If incorporation into existing Blue books is not possible, determine if a new Magenta or Blue book needs to be written.if a new Magenta or Blue book needs to be written.

• WG Status: Active X Idle ____

WG Summary Situation: Good progress.

status: OK CAUTION PROBLEMcomment: Good progress


33

SLS REPORT

NGU WG (cnt’d)

• File Upload Application ProfileNGU has handed down requirements to RF&MOD, C&S, and SLP to provide th bl b k ti f th Fil U l d li ti fil i f d tthe blue book sections for the File Upload application profile i.e., for data rates > 256 Kbps to 2 Msps. (extending existing TC standard)

• Action items assigned to RF&Mod, C&S, SLP chairmen during joint meetingg

• MSPARF&Mod to examine how to specify multiple access to spacecraft (MSPA) from one antenna on the uplink

• Ground sends commands up to 4 spacecraft on one frequency

• Spacecraft autonomous uplink acquisition

• Flexible transponder coherent turnaround ratio used for eachFlexible transponder coherent turnaround ratio used for each spacecraft to separately telemeter, range, and use Doppler.


34

SLS REPORT

NGU WG (cnt’d)

Major Findings for File Upload Profile:Need for stronger code (than BCH) (*)• Need for stronger code (than BCH) (*)

• No simultaneous ranging and telecommand

Major Findings for MSPA (up to a maximum of 4 S/C simultaneously )j g ( p y )• Need RF&Mod WG support • Need CSS area support

• CSS Forward CLTU service may be impacted since, with the ground servicing up to 4 S/C within a single beam of anground servicing up to 4 S/C within a single beam of an antenna, multiple POCCs may be supplying the telecommand data to uplink.

• Since the data may be files, ARQ may be returned from all 4 spacecraft affecting the CSS Return services.

(*) NASA is proposing LDPC, other agencies are recommending trade-off analysis (e g with Turbo Codes) NASA took action to provide


35

off analysis (e.g. with Turbo Codes). NASA took action to provide trade-off analysis report.

Oth M j Fi di

SLS REPORTNGU WG (cnt’d) Other Major FindingsDecoupling the frame layer from the coding sublayer for CCSDS Telecommand

• Migration path identified for ESA to keep the BCH code and

( )

• Migration path identified for ESA to keep the BCH code and simultaneously run the new code in the physical layer. This approach provides up to 8dB gain over the BCH.

• Only issue to resolve is time correlation. • Strong support by NASA Mars Program has been requested of CCSDS –• Strong support by NASA Mars Program has been requested of CCSDS –

in particular in light of international cross support at Mars for 2016 mission set and beyond.

• Note possibility for the coding sublayer and physical layer to be coupled

Application profiles have been prioritized by NGU for future requirements definition and assignment to other WGs. Priority of work is: 1) File upload (current), 2) Emergency Comm for unmanned missions, 3) Human Support

NGU to relook at CMLP study report to mine it for more potential requirements.


36

SLS REPORTNext Generation Uplink WG (cnt’d)

Problems and Issues:

• None

p ( )

Planning : File Upload

• NASA to provide a timeline for when the high rate file upload application fil i d dprofile is needed.

• Green book descriptive information needs to be gathered for the file upload profile

• Once the File upload profile is completed, the next profile should be worked on by NGU

Resolutions :

• None at this time.


37

SLS REPORT

7. Multispectral & Hyperspectral Data Compression (MHDC) WG

Goals:Goals:1. Review performance and hardware complexity of proposed

predictors for lossless compression.

2 S l t l l i h f t d di ti2. Select lossless compression approach for standardization.

Working Group Status: Active X Idle ____

Working Group Summary Situation:g p y

Selected the NASA proposed predictor for standardization. Draft white book to be delivered to WG prior to next meeting.


t OK


comment: OK progress

SLS REPORT

MHDC WG (con’t)

WG Summary progress:• Reviewed hardware implementation complexity and losslessReviewed hardware implementation complexity and lossless

compression performance results for proposed predictors under a fixed entropy coder.

• Reviewed selection criteria.• WG ultimately reached consensus that both predictors have low

complexity and that compression performance differences, particularly on multispectral images, weighed in favor of the JPL proposed predictor.

• Reviewed proposed corrigenda to correct minor problem with potentially ambiguous wording in CCSDS 122 Image Data Compression recommendationCompression recommendation.

• Reviewed new lossy compression rate-distortion performance results.


Problems and Issues:• None

SLS REPORT

MHDC WG (con’t)

Planning :• Lossless White Book – Spring 2010

• Lossless Red Book – Fall 2010

f f & S• Lossless Reference software & compliance data sets – Spring 2011

• Lossless Blue Book – Fall 2011

• Lossless Green Book – Fall 2011Lossless Green Book Fall 2011

• Milestone planning for lossy compression – Pending

Resolutions :

N


• None.

8. Space Data Link Security WG (cross-area SEA/SLS)SLS REPORT

8. Space Data Link Security WG (cross area SEA/SLS)Goals:• Develop standard protocol for security at the data link layer. This

includes authentication and/or encryption both uplink and downlink. This protocol will be independent from crypto algorithm and compatible with CCSDS TM/TC/AOS data link protocols.

WG Status: Active X (5 agencies, 15 participants) Idle ____

WG Summary Situation:

• User requirements fully reviewed & finalized (URD)User requirements fully reviewed & finalized (URD)

• Issues linked to the design of the protocol identified, discussed and decided upon (otherwise action items pending).

S f l i f RID NASA d d ft hit b k Will• Successful review of RIDs on NASA proposed draft white book. Will become SDLS white book after RIDs dispositions incorporation.



comment: good progress(URD finalized + white-1 agreed)

SLS REPORT

Space Data Link Security WGPlanning :• White book v1 for core protocol : December 2009

• Red-1 for core protocol : July 2010

• Interoperability testing of core protocol : July 2010 – Nov 2010

• Red-2 for core protocol : December 2010

• Blue book for core protocol : April 2011Blue book for core protocol : April 2011

• Green book for core protocol : Oct 2011

Resolutions :Resolutions :• None

Action:


• See WG action items list

9 PLACOM SIG

SLS REPORT

9. PLACOM SIG

Goal:

• Survey and report on agencies needs and planning for lunar and martianSurvey and report on agencies needs and planning for lunar and martian local communications/navigation infrastructure (surface coms/nav and surface-orbit coms/nav)

• Establish a preliminary coarse inventory of communications/navigationrequirements (URD)

• Identify the way forward, e.g. proposal for the creation of a WG, type of bookneeded (recommended standard, recommended practice, …)

SIG Status: Active X Idle ____

SIG Summary Situation:

status: OK CAUTION PROBLEMstatus: OK CAUTION PROBLEM



SLS REPORT

PLACOM SIG

SIG Summary progress:

• Reviewed Intergovernmental Agreement for Lunar/Martian Spectrum Coordination

R i d fi t i t f NASA CNES d ESA i t• Reviewed first inputs from NASA, CNES and ESA on requirements for lunar and Mars in-situ communicationsConsolidation of requirements planned for next meeting


SLS REPORT

10. SLS-OCM: Optical Coding & Modulations (SIG)

• Goal: Make a proposal for the creation of a WG.p p

• SIG Status : In progress

• SIG Summary Situation:


comment: Charter consolidationcomment: - Charter consolidation- White paper started


SLS REPORT

SLS-OCM SIG

SIG Summary progress:

• Better identification of targeted scenarios, includingNeed for cross support• Need for cross-support

• distinction between deep-space, Moon, Lagrange points• clarification of up/downlinks

• More detailed description of user requirements for applications, withMore detailed description of user requirements for applications, with quantitative examples. To be included…• Data rates, availability • Timeline of needs• Benefits of optics w.r.t. RF

• Action on DLR to propose a new version of the charter on the CWE.

• White paper initiated as support of charter.

• Completion of White Paper planned for Fall 2010


SLS REPORT

RESOLUTIONS TO CESG / CMC

Ready for submission to CESG/CMC For Agency ReviewReady for submission to CESG/CMC For Agency Review

COP-1 Pink Sheets

TC Space Data Link Protocol Pink Sheets

SCCC Red Book


SLS REPORT

E. SUMMARY: MAJOR ACCOMPLISHMENTS IN LAST REPORTING PERIOD1. RFM WG

Red Rec Modulation for Data Relays ready for Red after editorial reviewreview

2. RNG WGGB release Dec’09

3. C&S WGTM Sync & Ch. Coding pink sheets (with LDPC) ready for agency reviewreviewSCCC red book ready for agency reviewTC Sync & Ch. Coding pink sheets ready Fall’09

4. LEC BOFClosed. New project in C&S WG charter

5 SLP WG5. SLP WGTC SDLP pink sheets ready for agency reviewCOP-1 pink sheets ready for agency review

6. NGU WG2 application profiles consolidated

7 MHDC WG7. MHDC WGGood progress

8. SDLS WGGood progress

9. PlaCom SIGGood progress


Good progress10. OCM SIG

Good progress

SLS REPORT

QUESTIONS ?


SLS REPORT

ANNEX

SCCC Standardization IPR Question ClarifiedSCCC Standardization – IPR Question Clarified

ESA Position


SCCC Standardization – IPR Question Clarified

SLS REPORT

ESA Position



SLS REPORT

ESA Position


CROSS SUPPORT SERVICESCROSS SUPPORT SERVICES(CSS) AREA(CSS) AREA( )( )

E ik B kl (AD)Erik Barkley (AD)Yves Doat (DAD)



Cross Support Services Area ReportCross Support Services Area Report

1. Service Management WG


2. Cross Support Transfer Service WG

3. Cross Support Service Architecture WG

4. Super BOF (“SOA for Space”)





Opening Plenary

Crs SptArch

Crs Spt Tsfr Svc

Svc Mgmt

Super BOF

File Splinter Session

IA‐IPR‐SM Joint Mtg

Intermed Plenary

Closing PlenaryPlenary Arch Tsfr Svc Mgmt BOF Session Mtg Plenary Plenary

ASI

BNSC 1 1 1 1 1 1 1 1

CNES 3 2 1 2 2 2 2

CNSACNSA

CSA 1

DLR 3 2 1 1 1 1 1 3

ESA 6 1 3 3 4 5 3 4 6

FSA 1 1 1

INPE 1

JAXA 1 1 2 1 1 2

NASA 3 2 2 3 10 2 5 2 3

Total 17 5 11 11 20 11 12 10 18

Duration (Days) 0.25 1.50 4.50 3.00 0.50 0.50 0.25 0.25 0.25

cesg-5704 November 200928 April 2009

Agencies 6 4 6 6 7 5 5 6 7



1. Service Management WG


Goals: Develop Specifications for cross support management for TT+C services


W ki G S Si i Cl i d b i ( l kWorking Group Summary Situation: Cleaning up debris (close‐out work re Concept and Prototype Report); Determining re‐factored SM approach

Service Management Recommendation: Blue Book released August 2009!

Concept Book: Minor updates needed

Interoperable Prototype Test Report: Very minor updates needed


X (Current Deliverables)

X (Manpower is light for new WG concept


concept development exercises)

S i M t WG Pl i


Activity Date

Service Management WG Planning

Prototype Inter‐operation completion, CCSDS Record (Yellow Book)

November 2009

Concept Book (Green Book) November 2009

New WG Planning

Concept Paper for New WG March 2010

Draft Charter for New WG April 2010


2. Cross Support Transfer Services (CSTS) WG

Cross Support Services Area ReportCross Support Services Area Reportpp ( )

Goals: • Define inter‐agency ground domain transfer service framework• Define recommendations for specific transfer services based on the

f kframework


Working Group Summary Situation:Working Group Summary Situation:Framework + Concept Books: Ready to be sent to Secretariat;Services: Monitoring nearly Red‐1, Tracking service White Book in progress; SLE Pink Sheets: Books ready for publication (Blue Book)F AOS CLTU: R d f bli ti (O )F‐AOS‐CLTU: Ready for publication (Orange)Prototypes: Framework inter‐operation test started; Monitoring Service advanced

planningRequested New Books: CSTS Reference Model (Magenta – Charter Update), File

T f (Ch t U d t M t Bl ) M it D t Di ti (Bl )Transfer (Charter Update – Magenta + Blue), Monitor Data Dictionary (Blue), RAD (Blue)status: OK CAUTION PROBLEM

X (Framework, MD‐CSTS TD CSTS RUFT

X (File Transfer, RAD CSTS


CSTS,TD‐CSTS, RUFT, MD‐CSTS Prototype, SLE)

RAD‐CSTS,TD‐CSTS Prototype, RUFT Prototype)


CSTS WG Planning

ProjectT S

Iss, PrototypeU

Prototype Provider

Fall MeetingTo Secr. User Provider

Framework 921.1-R

Now 0.21 NASA ESA Reviewed

Concept Now 0.14 N/A N/A ReviewedConcept 920.0-G

Now 0.14 N/A N/A Reviewed

Guidelines 921.2-R

End 09 0.05 N/A N/A Reviewed

M it i E d 09 0 07 NASA CNES R i dMonitoring 922.1-R

End 09 0.07 NASA CNES Reviewed

Tracking 922.2-R

May 10 0.02 TBD TBD Addressed

RUFT Oct 10 TBD TBD AddressedE.F-CLTU (Orange)

Oct 09 0.2 N/A N/A Addressed


File Tx TBD TBD TBD TBD Addressed


3. Cross Support Services Architecture (CSSA) WGGoals: • Develop, produce best practices recommendation for cross support services

architecture

• Produce a recommended standard for cross support service catalog

• Produce a recommended standard for service agreement

WG St t A tiWG Status: Active

WG Summary Situation:

A hit t I 2 d d f WB i d 3 d d f iArchitecture: In progress; 2nd draft WB reviewed; 3rd draft in progress

Service Catalog: 1st draft WB in progress

Service Agreement: In progress; 2nd draft WB reviewed; 3rd draft in progress

status: OK CAUTION PROBLEMX

Current WBsXSOA For Space impacts not yet


p yanalyzed; IOAG SISG ADD effort not planned for


CSSA WG Planning

Activity DateActivity Date

Cross Support Architecture (MB) R-1, January 20102010

Service Catalog (BB) R-1, June 2010

Service Agreements (BB) R-1, June 2010


D C A M ti


• Joint CSS‐CSTS/MOIMS‐NAV Meeting• TD CSTS concept reviewed

D. Cross Area Meetings

• TD‐CSTS concept reviewed• TD‐CSTS draft recommendation to be updated accordingly

• Joint SE, MOIMS, CSS, SOIS (SUPER BOF)Joint SE, MOIMS, CSS, SOIS (SUPER BOF)• (More slides on this coming up)

• Joint MOIMS–IPR, SE‐IA/CSS‐SM Meeting• (More slides on this coming up)


D. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD


• SMWG• Service Management Recommendation ‐‐‐ Blue Book ReleasedService Management Recommendation Blue Book Released

• CSTS• Framework Specification ‐‐‐ Red book 1 Ready for Agency review• Framework Concept Green Book Ready for final Agency review• Framework Concept ‐‐‐ Green Book Ready for final Agency review• SLE Books ‐‐‐ Blue‐2, Blue‐3 Ready for publication


Super BOF BackgroundSuper BOF Background

• E-mail From A. Hooke to CESG: (CSS AD emphasis )

Date: Fri 02 Oct 2009To: CESGcc: CMCSubject: Proposed way-forward for a "Service Oriented Architecture (SOA) for Space Missions."

“…. . The IOAG also asks the CCSDS to study whether the current CCSDS work could be expanded to embrace the production of a “Service Oriented p pArchitecture (SOA) for Space Missions…

…In response to the IOAG resolution, it is proposed that the CESG will convene a BOF at the October meeting with a view towards chartering a Working Group to create some kind of “SOA for Space Mission Operations” – probably more ofto create some kind of SOA for Space Mission Operations – probably more of a “SOA-like” service architecture framework for CCSDS services on ground and in space. This would essentially be the top-level CCSDS framework for space mission operations into which all of the other CCSDS work would be referenced…

…If acceptable to the CESG then the CSS Area Director should convene the BOF during the upcoming CCSDS meeting at ESTEC. It has been suggested that in view of the importance of this activity, the BOF should meet on the morning of Tuesday 27 October…”

cesg-66

Super BOF Meeting SummarySuper BOF Meeting Summary

SOA for Space was only hinted at; need for CCSDS Model, guidance information at CCSDS-wide level was the primary output of the BOF

Goals for NEW WG as indicated at conclusion of Super-BOF:Goals for NEW WG as indicated at conclusion of Super BOF:1. Exhaustive list of services identifying cross-support services2. Cross-Support & Interoperability Use cases / Operational scenarios,3. overlap and gap analysis (identify redundant and missing services)4. Business cases (based on existing and in-work services),4. Business cases (based on existing and in work services),5. Architecture of existing and in-work services including an information model,6. Abstract service definitions: rational for a service, content of service

specifications, taxonomy7. CCSDS Reference architecture. Identify impact on existing architecture.

Discussed only briefly:•Formation of SOA for Space WG – really SOA for CCSDS – to address all IT i f t t i t CCSDS l l

y p g

IT infrastructure issues at CCSDS level• Produce recommendations on SOA for CCSDS• Re-programming of existing WG

• How long will does it take to produce the recommendation(s)

cesg-67

g p ( )• What do we do with current efforts?

Super BOF Plan of AttackSuper BOF Plan of Attack

CESG/CMC: Form BOF

BOF: Rapid Identifications

CESG: Vote on

BOF: Draft Concept Paper

CESG: Review

BOF: Final Concept PaperForm BOF

ASAP•Nominees 07 Nov 09

•BOF Ground Rules, Initiation 20 Nov 09

Identifications re Items 1 + 2•(List of Services)•(List of Scenarios)

•15 Dec 2009

on Identifications •Feedback to BOF

•10 Jan 2010

Concept Paper•Points 3 – 7, WG approach, WG Deliverables

•Identification of Key Trades, fitting SOA to CCSDS

Review Draft, Feedback to BOF•15 Feb 2009

Concept Paper• 28 Feb 2010

Nov 09•31 January 2010

L t’ ll thi th CCSDS R f A hit t BOF

cesg-68

Let’s call this the CCSDS Reference Architecture BOF

Additional Recommendations (Post Super BOF)Additional Recommendations (Post Super BOF)

• Initiate parallel activity (in addition to CCSDS Reference Architecture) with goal of producing concept paper for SOA aspect of CCSDSconcept paper for SOA aspect of CCSDS• Focused exclusively on information infrastructure

services• Aligned with current industry SOA approach• Identify deliverables relative to related CCSDS activities

on information architecture, registries/SANA, directories• Due date of 28 Feb 2010 (same as reference architecture

BOF concept paper)BOF concept paper)• CESG/CMC makes informed decision for WG initiation at

Spring meetings

G i f d N d t i l id th t• Going forward…Need to seriously consider that CCSDS reference architecture be visited in a structured formal manner at every CCSDS technical meetings (vs. MOUs)

cesg-69

meetings (vs. MOUs)

Super BOF Conclusion Super BOF Conclusion

• Agreement that overall CCSDS technical framework (reference architecture) in much need of (re-)definition

• That SOA for CCSDS itself was not directly addressed (but suggested to draft two concept papers in parallel)

• Need to seriously consider that CCSDS framework be visited in a structured formal manner at every CCSDS

h i l i (CESG di i )technical meeting (CESG standing action)

• Concern:• BOF members need both excellent domain knowledge and

available time

cesg-70

SPACE INTERNETWORKINGSPACE INTERNETWORKINGSPACE INTERNETWORKING SPACE INTERNETWORKING SERVICES (SIS)SERVICES (SIS)AREA REPORTAREA REPORT

Bob Durst (AD)Dai Stanton (DAD)


Space Internetworking Services Area ReportSpace Internetworking Services Area Report


1. Space Packet Protocol Working Group p g p

2. Asynchronous Message Service Working Group

3. IP Over CCSDS Working Group

4. Motion Imagery and Applications Working Group

5. Delay Tolerant Networking Working Group

6 Voice Working Group6. Voice Working Group



B. ATTENDANCE METRICS

Space Internetworking Systems (SIS)

IPO WG AMS WG Voice WG DTN WG MIA WG Plenaryy

Secretariat 1 1BNSC 1 1 1CNESCSA 1 1DLR 1 1ESA 1 4 1 3 1FSA 1 1 2 1 1FSA 1 1 2 1 1

JAXA 1USA 3 4 6 12 6 7Total 7 10 10 20 8 9

* / i t d tt d d

MeetingDuration .5 day 2 days 1 day 2 days 1 day +

cross area .5 day

Agency


*x/y x = registered; y = attended.AgencyDiversity 5 4 4 7 3 3



1. Space Packet Protocol WG

Goals: • Figure out how to go out of business…

Working Group Status:

• Only remaining SIS Work Item: Green book updates lagging


• It just keeps getting betterIt just keeps getting better.status: OK CAUTION PROBLEM

comment: Green Book updates lagging


2 A h M S i WG


2. Asynchronous Message Service WGGoals: • Review RIDs from final Agency review of specification, reach consensus on all RID

dispositions.p• Review Green Book and develop plan for completing and publishing it, possibly

moving interoperability test results to a separate Yellow Book.• Resolve to request publication of the AMS Blue Book.

Working Group Status:Working Group Status:• WG reached consensus on approval of dispositions for all agency review RIDs.

• RID #4 required additional text, and an additional Green Book section will be added.

• Stuart Fowell to provide additional PICS pro forma material.• No other remaining technical work on the AMS Draft Standard.

Working Group Summary Situation:status: OK CAUTION PROBLEM

comment: On schedule.



AMS WG Findings

• The WG agrees that the text of the AMS Draft Recommendation, revised per the consensus disposition of all agency review RIDs, is now final and is ready for publication as a Recommended

AMS WG Findings

is now final and is ready for publication as a Recommended Standard. The WG has asked the Area Director to issue a resolution to this effect at his convenience. (SIS AD: Done.)

• The WG agrees to move AMS interoperability test plan and results from the Green Book into a Yellow Book and proceed with publication of both books as soon as possible.p p

• The AMS WG once again reiterates its recommendation that, funding permitting, ESA/SciSys – JHU/APL interoperabilityfunding permitting, ESA/SciSys JHU/APL interoperability testing of the SOIS MTS-specified subset of AMS (and Meta-AMS) over SOIS packet service should begin as soon as feasible.


3. IP Over CCSDS WG


Goals: • Develop a CCSDS recommended best practice document for how

to transfer IP datagrams over the 4 CCSDS link layer protocolsto transfer IP datagrams over the 4 CCSDS link layer protocols.• New IP Forward Plan BoF – Develop IP in Space Internetworking

Magenta and Green books

Working Group Status:Working Group Status:• IP over CCSDS Red-3 including removal of IPV4 reviewed by WG• Substantial edits made during the SIS-IPO WG session; document

update planned for Dec 15, 2009C f G f• Consensus of WG is newly edited book needs to go out for Agency Review

• No discussion on New Plan Forward for IP BoF took place at this meeting due to lack of timeg




status: OK CAUTION PROBLEMcomment: Good

4. Motion Imagery and Applications (MIA) WG


Goals: • Final review of Green Book Draft• J i t ti ith SM&C IPO d SLP WG t f M t• Joint meetings with SM&C, IPO and SLP WGs as part of Magenta

Book development• Plan Magenta Book forward work

Working Group Status:Working Group Status:• Participants all actively participating in positive manner • Final draft green book review in WG completed• Not all planned Joint meetings happened – these are important for

Magenta Book progress

Working Group Summary Situation:t t OK CAUTION PROBLEMstatus: OK CAUTION PROBLEM

comment: Behind on Green Book


MIA WG (cnt’d)


( )

Problems and Issues:• No attendees from IPO and SLP WGs at planned joint MIA j

meeting• Inter-area interaction is critical to maintaining schedule

for Magenta book – unresolved problem with potential impactimpact


5 Delay Tolerant Networking WG


5. Delay Tolerant Networking WGGoals: • Review status of ongoing DTN work by agencies (testbeds / simulation

work, etc.).• Review and disposition IOAG / SISG inputs to Green Book.Review and disposition IOAG / SISG inputs to Green Book.• Review initial drafts of DTN protocol specifications.

Working Group Status:• Reviewed and dispositioned IOAG / SISG inputs to the Green Book.

Incorporation of the results from the meeting into the Green Book has been agreed to by NASA and ESA as constituting completeness of the Green Book. Expect completion of the Green Book by end of CY2009.

• CCSDS Framework Schedule• Need to update status for protocol specs – first draft comments on

were due 15 September 2009 (none received). Second draft specs to WG 15 November 2009.

• Green Book was supposed to be final 6/1/2009 – now expect 12/31/2009 as a result of late-breaking IOAG-SISG inputs

Working Group Summary Situation:status: OK CAUTION PROBLEM

comment: Agreement on Green


comment: g ee e t o G eeBook should lead to quick completion.

7. Voice WG


Goals:• Review suggested updates to Green BookReview suggested updates to Green Book• Set schedule for Magenta Book• Determine which CCSDS groups to monitor and participate with

as it may regard voice communications

WG Status: Good participationSet Dec 15 as the Green Book final draft completion dateConsensus on current and future directionConsensus on current and future direction

Terrestrial – immediate need (CC-to-CC, CC-to-remote) Lunar and LEO – 2014 timeframeDeep Space – timeframe TBD

WG Summary Situation: status: OK CAUTION PROBLEM

comment: Green Book


behind schedule.


• SIS-AMS: Joint meeting with SOIS to discuss SOIS-MTS mapping onto AMS Interoperability testing desired but


mapping onto AMS. Interoperability testing desired but unresourced.

• SIS-MIA: Joint meeting with SM&C (reported previously). g ( p p y)Meetings with SLS-SLP and SIS-IPO did not occur.

• SIS-DTN: DTN-on-ISS coordination meetingESA (Ki N d)• ESA (Kim Neergard)- METERON (Mars End-to-End Robotics Operations Network)

• JAXA (Kiyohisa Suzuki)



• Approve AMS Blue Book (soon)

Forthcoming Resolutions from SIS to CESG

• Approve Motion Imagery and Applications Green Book (est. December 2009)

• Approve Voice Green Book (est. December 2009)

• Charter CFDP Profiles WG (TBD)( )



E SUMMARY: MAJOR ACCOMPLISHMENTS F’09 MEETING

1. AMS: Technical work on Draft Recommended Standard is complete. Document is ready for final editing and publication as Blue Book

E. SUMMARY: MAJOR ACCOMPLISHMENTS, F 09 MEETING

Document is ready for final editing and publication as Blue Book.

2. Motion Imagery and Applications: Completed working group review of Draft Green Book; document will soon be ready for final editing ; y gand balloting as Green Book.

3. DTN: Achieved consensus on completeness criteria for Green Book.

4. Voice: Completed working group review of Draft Green Book; document will soon be ready for final editing and balloting as Green BookBook.


MISSION OPERATIONSMISSION OPERATIONSMISSION OPERATIONSMISSION OPERATIONSAND INFORMATION AND INFORMATION

MANAGEMENT SERVICES (MOIMS) MANAGEMENT SERVICES (MOIMS) AREAAREAAREAAREA

Nestor Peccia (AD)Roger Thompson (DAD)


A

Mission Operations and Information Mission Operations and Information Management Systems Area ReportManagement Systems Area Report

1. DAI Working Group


1. DAI Working Group

2. IPR Working Group

3 NAVWorking Group3. NAV Working Group

4. SM&C Working Group

5. RAC Working Group

6. PUS BOF





Plenary DAI IPR NAV RAC PUS SM&C PlenaryASI

MOIMS

ASIBNSC 2 1 1 1 1 2 1CNES 6 1 1 3 3CSA 1 1 1DLRDLR 1ESA 6 1 1 2 1 4 3FSA 3 2 2INPE 1 1JAXAEUMETSATUSA 8 5 7 4 3 2 5 4Total 27 7 10 7 4 4 19 14Total 27 7 10 7 4 4 19 14

MeetingDuration

0.5 1.5 1.5 4 1 0.5 4 0.5

Agency 7 3 4 3 2 3 7 6


AgencyDiversity

7 3 4 3 2 3 7 6



1. Data Archive Ingestion (DAI) WGC. SUMMARY TECHNICAL STATUS

PAISA list of issues with the draft Producer Archive Interface Standard (PAIS) White Book‐11 were reviewed and several were resolved at meeting. Drafting of RB to follow.reviewed and several were resolved at meeting. Drafting of RB to follow.

Improvement and Consistency of element names, Enumeration of Group Structures, mapping of TOs to Delete, Last TO, etc.

One PAIS implementation available based on earlier draft, will be updated in coming year to current draft; Second implementation to be started this year, SIP Builder uses resulting PAIS Structures Schedule (major deliverables only)Schedule (major deliverables only)

2010‐03‐15 PAIS RB will be submitted to CMC approval for Agency ReviewOAIS RM

Currently undergoing CCSDS Agency Review. ISO Review to follow.Schedule (major deliverables only)

2009‐12‐24 OAIS RM Blue Book 2 will be submitted for CMC ApprovalPAIMAS

WG reconfirmed with no changes. CESG requiring work (and non‐existant resources) to change color, change boilerplate, and likely another full review in ISO.Schedule (major deliverables only)


( j y)2011‐04‐30 PAIMAS Book scheduled into work program

cesg-8804 November 200922 October 2008

X

hi i ( )


1. 1. Data Archive Ingestion (DAI) WGIssue 1

OAIS RM Issue 2 should remain a CCSDS Standard (Blue Book)Issue 2Issue 2

DAI recommends single registry of all registered items, which is respected by and used by entire community (both CCSDS and ISO outside of CCSDS),

Issue 3CESG i i dh t d th th ll iCESG requiring adherence to new procedures rather than allowing a reconfirmation when no technical changes are required. This is a waste of scarce agency resources devoted to standards

development when no technical changes and no new benefits will be d i d f di hderived from expending those resources.

cesg-8904 November 200922 October 2008

2. Information Packaging and Registries (IPR) Working Group


g g g ( ) g p

Workshop GoalsFinalize XFDU Tutorial Green Book for submission to CESGDraft XML Schema Registry/Repository White Book and Reference ImplementationReview IA Registry/Repository Services Reference Model WB and resolve any issues on theReview IA Registry/Repository Services Reference Model WB and resolve any issues on the compatibility specialization of the Reference Model

XFDU Schedule:Green Book Issue 1 for Panel Review 1‐Dec‐2009XFDU Green Book submitted for CESG / CMC review and approval 1‐Jan‐2010

XML Schema Registries Schedule:XSD Registry WB and Prototypes Issue 2 for Panel Review 15‐Dec‐2009XML Schema Registry Repository RB/GB to Tom Gannett. 1‐March‐2010XML Schema Registry Repository RB/GB to Tom Gannett. 1 March 2010XML Schema Red Book Agency Review Begins 1‐April‐2010ESA Prototype 1‐Oct‐2010XFDU Interoperability Test Plan 15‐Oct‐2010Interoperability Test Report 15‐Dec‐2010Interoperability Test Report 15 Dec 2010



X

2 IPR C A I


2. IPR Cross Area IssuesThe IPR XML Schema Registry Repository RB will be dependant on the IA Registry Service Architecture WB and IPR documents so the review schedules of the two documents will require synchronizationq y

The detailed review of the proposed IA Registry Service Architecture WB identified several areas that needed significant modification to allow the XML Schema Registry Repository interfaces to be a formal specialization of the Registry Services Architecture interfaces Solutions to these issues were identified and agreedArchitecture interfaces. Solutions to these issues were identified and agreed

IPR Other Issues and ConcernsCCSDS has indicated the high priority of a full SOA architecture/model / activity. The skills of the IA/IPR members make it likely that most of the future efforts of IA/IPR will be focused on the SOA effort

The CCSDS XML Schema Registry http://sindbad.gsfc.nasa.gov/ hosted by NASA/CSC is available for use by any CCSDS memberNASA/CSC is available for use by any CCSDS member.

Installation package and source code is available


3. 3. Navigation (NAV) Working Group


ODMConfirmed resolution of issues from CESG Poll on ODM V2.0

NDM/XMLCompleted discussion/disposition of 32 RIDs from Agency Review 2Initiated preparation of prototyping test plan

Green BookCompleted discussion of Green Book Version 3 updatesConfirmed plan for Green Book Version 4 re‐write

fSpacecraft Perturbations Message Completed discussion of Spacecraft Perturbations Message White Book 1.0

FutureCompleted discussion of “Pointing Requests Message” Concept Paper (pending submission to AD/CESG for consideration)to AD/CESG for consideration)Completed discussion of a predicted events message abstractCompleted discussion of a few other less mature ideas (Attitude Sensor Message, Small Body Shape Model, Maneuver Message)

Status: OK CAUTION PROBLEM


x

3. Navigation (NAV) Working Group


CROSS‐AREA Meetings & Technical IssuesMonitor & Control: Met with SM&C group to discuss their Flight Dynamics Service.Cross Support Transfer Service: Met with CSTS group to discuss their CSTS‐TD SLE service.XSG SIG: No meeting.ISO TC20/SC14: Representative participated in meetings as available. Closer relationship and mutual standards development is desirable. Several

t iti i t d f N WG hi bl ith i tiopportunities exist; some new docs for Nav WG, some achievable with existing Nav WG standards, some better targeted at another CCSDS group. The leadership of TC20/SC13 and TC20/SC14 should consider the organizational structure and ways in which to facilitate closer cooperation and collaboration to avoid duplicate navigation related standardization by the two groups.

AdministrationUpdated Charter (added 1 goal... Spacecraft Perturbations Message)Updated Framework Project schedules as applicableIntroduced 2 new members to the Working Groupg p

Overall AssessmentMet all goals for the meeting


3. Navigation (NAV) Working Group


Resolution 1:The Navigation WG proposes that a new standard based on

the “Pointing Request Messages” Concept Paper be added to its Technical Programto its Technical Program.


4. Spacecraft M&C Working Group (1/3)


. Spacec a t &C o g G oup ( /3)Attendance: more than 17 people on average from 8 different space agencies

Super BOF+ The issues raised for a long time by the SM&C WG have been eventually brought at the right level+ The Super WG draft charter goes in the right direction‐ Concerns on the overall timeframe to achieve results‐ No decision made on immediate needs (e.g. overlaps)

Joint Meeting with Motion & Imagery Applications (MIA)g g y pp ( )Identified need for cooperation between the 2 groupsPossible joint prototype JSC‐MSFCPotential first [low risk] on‐board deployment

MO PrototypesMO PrototypesJSC‐DLR: Good progress. First exchanges planned for Jan 10. No RIDs identified on MAL. JSC/DLR committed to provide C++ Language API MBESA‐CNES: Good progress. Testbed and test specification are ready, test is being carried out (completion by end Feb 10). Some editorial RIDs on the MAL. Testbed could be used by CCSDS in the future as a tool to certify MO compliant implementationsCNES MO M&C over SP: Good progress. An update of the book is planned by Feb 10 using the feedbacks coming from the prototype

XTCE


2 MBs + 1 pink sheet ready for internal review



. Spacec a t &C o g G oup ( /3)

GMSECIdentified need to investigate commonalities with SM&C by NASA (JSC and GSFC). Initial reporting by next CCSDS workshop

Use of Commercial SOA FrameworksDeployment of MO services over a commercial SOA framework is possible, but requires a technology mapping for that frameworkOpen questions on “MO Compliance” in the case of private (no CCSDS BB) technology mappingp q p p ( ) gy pp g

Joint SM&C‐NAV MeetingMO Services to focus around the already standardised NAV data types

Joint SM&C‐SOIS‐PUS MeetinggShort term: update PUS in CCSDS (BB) with selected lesson learned changes, but keep backward compatibility (CCSDS PUS BOF)Long term: MO Services to leverage PUS concepts and experience (PUS BOF to merge into SM&C WG) and produce the M&C standards for the futureSOIS: no inconsistencies identified. Potential gap for emergency HW‐level commanding

PROBLEMCAUTIONOKstatus: PROBLEMCAUTIONOKstatus:


Xcomment: Xcomment: X



p g p ( )

Recommendations to MOIMS ADSuper‐follow the Super BOF!!!Monitor that GB issues are quickly resolvedRecommend that CCSDS makes SW libraries/demos implementing standard freely availableimplementing standard freely availableRecommend that CCSDS identifies means to host ancillary data (e.g. XML Schemas)


5. Digital Repository Audit and Certification (RAC) WG5. Digital Repository Audit and Certification (RAC) WG


g p y ( )g p y ( )

GoalObtain ISO approval of a standard that establishes the criteria that a repository must meet to be designated an ISO Trusted Digital Repository

Working Group Summary progress:Reviewed status of the documents on RAC Wiki in weekly telecons of 6‐12 people for 90 mins eachp p“Metrics...” document undergoing CCSDS review – awaiting ISO review to startReviewed and almost finalised Requirements for Bodies

Schedule (major deliverables only)Schedule (major deliverables only)“Requirements for Bodies Providing Audit and Certification of Digital Repositories” Red Book, ready for formal review: Nov 2009

It will be submitted for Agency Review.

status: CAUTION PROBLEMcomment: OK


5. Digital Repository Audit and Certification (RAC) WG5. Digital Repository Audit and Certification (RAC) WG


g p y ( )g p y ( )

Issue 1 Discussions held with ISO liaison about simultaneous CCSDS and ISO review This is necessary because we expect very many commentsreview. This is necessary because we expect very many comments from outside CCSDS and sequential reviews would get into a cycle of approvals at CCSDS and ISO level

RESOLUTION 1Submit WB “Requirements for Bodies..” document to CCSDS and ISO by December 2009 for Agency Review


6. Packet Utilization Standard (PUS) BOF6. Packet Utilization Standard (PUS) BOF


( )( )

Goal

Benefits of using the PUS & “why having a CCSDS PUS”

The key to the success of the PUS has been the highly‐prescriptive nature of the y g y p pService specification that can be easily tailored to suit the operational needs of individual missions

Applying the PUS brings benefits such as:

the production and reuse of common space system components for both on‐the production and reuse of common space system components for both onboard and ground systems

the early definition of high‐quality external interfaces within a geographically‐distributed space system development environment

it encourages the adoption of common operations concepts across manyit encourages the adoption of common operations concepts across many missions e.g. facilitating staff movement between missions

Because of the strong interdependencies between PUS and CCSDS documents/activities, issuing the PUS under the CCSDS umbrella is surely beneficial, especially to ensure within CCSDS a coherent set of standards with adequate scopeespecially to ensure within CCSDS, a coherent set of standards with adequate scope and interfaces.

Benefit would also accrue from the wider acceptance of the standard and especially for issues related to interoperability between Agencies.


6. Packet Utilization Standard (PUS) BOF6. Packet Utilization Standard (PUS) BOF


( )( )

MOIMS AD will start the formal procedure to require the creation of the PUS WG

Main activitiesAssess and agree the objective and scope of the new PUS working group with respectAssess and agree the objective and scope of the new PUS working group with respect to other existing working groups (SM&C, SOIS), in order to ensure non‐overlapping, overall consistency, etc.Review and assess the status of the existing PUS (ECSS‐E‐70‐41A).Review and assess the European “lessons learned” (including harmonization needReview and assess the European lessons learned (including harmonization need with existing CCSDS standards such as CFDP and Encapsulation Service, Space Packet Protocol).Compile “change requests” arising from these reviews, from the need to comply (or modify) with other existing CCSDS standards and from any additional operational concepts.Harmonize with SM&C, SOIS (and potentially others) working groups, the implementation of the collected change requests on the PUS, SM&C, SOIS, etc. documents. A h i d f h h b f d h i i PUS dAssess the magnitude of the changes to be performed on the existing PUS and produce a roadmap for the generation of the CCSDS PUS Blue Book and any supporting documents (e.g. Green, Magenta)Produce the PUS related books.




• DAI WG• PAIS RB to be issued for Agency Review in 6 months• OAIS RB CCSDS AGENCY Review ends in 2 weeks

E. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD (1)

• OAIS RB CCSDS AGENCY Review ends in 2 weeks• OAIS Should Remain BB• Reaffirmation without technical change should not incur book revision• Recommendation of single registry of items across CCSDS/ISO community

• IPR WG• XFDU GB to be issued for CESG review by Jan 2010• XML Schema Registry GB / RB to be issued for Agency Review by April 2010 • Dependency of above RB on IA WB requires synchronised review• Dependency of above RB on IA WB requires synchronised review• Diversion of resources to high priority SOA activities

• NAV WG• Navigation GB to be reissued March 2010• Navigation GB to be reissued March 2010• New “Pointing Request Message” Standard to be added to technical programme




• SM&C WG• MAL & RM issued for Agency review• GB Reviewed by CESG will be reissued when ADs

E. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD (2)

• GB Reviewed by CESG will be reissued when ADs agree to proposed changes

• Open Letter• New Super BOF needs to progress rapidly to avoid delay to current work• GB Issues need to be quickly resolvedGB Issues need to be quickly resolved

• RAC WG• Requirements for Bodies Providing Audit and Certification of Digital Repositories

RB 2 Ready for final Agency review (Nov 09)y g y ( )• Simultaneous CCSDS and ISO reviews required – need to initiate ISO review

• PUS BOF• Creation of WG to be requested by ADq y


SYSTEMS ENGINEERING AREA SYSTEMS ENGINEERING AREA (SEA)(SEA)(SEA)(SEA)

Peter Shames (AD)Takahiro Yamada (DAD)


A. CURRENT GROUPS WITHIN THE AREA

Systems Engineering Area ReportSystems Engineering Area Report

1. Information Architecture WG (& joint IPRWG meetings on registries)2. Security WG3. Delta‐DOR WG4. SANA WG5. Timecode WG (Pink Sheets)6. Time Synchronization & Correlation BoF (formative meeting)7. XML Standards and Guidelines SIG (no meeting, to be folded into SOA BoF)8. Space Link Security WG (joint w/ SLS, reported in SLS)

• SEA Responsibilities• Overall architecture for space mission communications, operations, and

cross‐support• Coordinate and collaborate with the other areas about architectural• Coordinate and collaborate with the other areas about architectural

choices and options • Support the CESG in evaluating consistency of all area programs of work

with the defined architecture


• Create such working groups and BoFs as are required to progress the work of CCSDS



SEAPlenary IA/IPR D-DOR WG Sec Time Corr SANA Plenaryy

BoFy

ASI

BNSC 1 1

CNES 1 1

CSA 1 1

DLR 1 1

ESA 1 4 2 4 1 1

JAXA 1 1 1

NASA 4 5 1 3 6 2 5

Total 7 12 4 9 8 3 7

M ti 0 5 2 5 3 2 0 5 0 5 0 5Meeting 0.5 2.5 3 2 0.5 0.5 0.5

Duration

Agency 3 5 3 4 3 2 3

Diversity




1.1. Information Architecture WGInformation Architecture WGGoals: • Develop a high level Information Architecture Reference Model• Define Registry / Repository Reference model & associated registry information model (w/ IPR WG)• WG wants to develop integrated Space Information Service (SOA) reference model and services (See

later comment)

Working Group Status:g p• Finalize Reference Architecture for Space Information Management (RASIM) V1 Green Book, should

be published this fall, really Magenta Book material• IAWG developed top down registry model & prototypes, info model & services interfaces, IPR WG

developed bottom up XML registry & prototypes to be coordinated in joint meetings, White Book in development derived from ebXML

• Extensive discussion on the Registry‐Repository Architecture White Book; preparations for the Red Book

• Discussion on the registry information model Green Book and XML schema registry White Book• Joint discussion between SMWG, IAWG and IPR on SOA and plans for development of a space

information services architecture

• Working Group Summary Situation:status: OK CAUTION PROBLEM



Joint IA / IPR working well

Good

22 Security WGSecurity WG


2.2. Security WGSecurity WG

Goals:• Develop security overview & threat assessment, and security architecture,

framework and related standardsframework and related standards

Working Group Status:• Progress

• Security Architecture Magenta Book being finalized for review• Algorithm document has lots of rationale/explanation that needs to be

“moved.” Planning for implementations since doc is now Blue.• Mission Planners Guide – 1 more round thru WG and then to Secretariat. • Key Management Green Book essentially completed. Decided to produce a KM

Blue Book for symmetric KM.y• Reviewed 1st draft of Security Glossary. • Network layer security – IPSec with Encapsulating Security Payload (ESP),

only relevant in near Earth (out to Lunar) operations domain.• Working well with Space Link Layer Security WG, reported in SLS



Good agency Good


Good agency support

Good

3.3. DeltaDelta‐‐DOR WGDOR WG


Goals: • Develop detailed requirements for delta differential one‐way ranging (Delta‐DOR)

service

• Coordinate work in other WGs (SIS/Ranging, CSS/CSTS, MOIMS/Nav, CSS/SM)

• Develop integrated vision of service and interoperability points

Working Group Status:• Magenta Book: completed first Agencies’ review. RIDs were discussed and resolved

during the meeting.

• Delta‐DOR Raw Data Exchange Format (DRDEF) Blue Book draft: discussed and remaining issues were resolved. Book to be submitted for Editorial Review in Feb/2010Feb/2010

• Raw Data Exchange document similar to TDM Blue Book (CCSDS 503.0‐B‐1)

• Schedule for the Green Book has been pushed into future due to workload on BB and MBG d l & 3 bi l l i bili lid i• Good progress on early & near term, 3 agency, bi‐lateral interoperability validation




Making very good progress

Very Good


4.4. SANA WGSANA WG

Goals: • Develop procedure for the Space Assigned Numbers Authority (SANA)Develop procedure for the Space Assigned Numbers Authority (SANA)

Working Group Status:• Draft Yellow Book procedure CCSDS 313.0‐Y‐0.1 all RIDs resolved, ready

for final CESG reviewfor final CESG review

• Includes delegation, “grandfathers”, initial conditions, and future procedures

• Request WGs to send new registry topics to SANA Chair nowq g y p

• Contract for SANA operator is being finalized, need SANA “home”

• Propose inclusion in SANA of updated CCSDS Glossary and Space Link Identifiers



M t @ ESTEC SANA t t t


Met @ ESTEC SANA to start working off queue


5.5. TimecodeTimecode WGWG

Goals: • Update timecode formats

• Explore need for time and synchronization standards

Working Group Status:• Revised Pink Sheets for Time Code reviewed & RIDs resolved• Revised Pink Sheets for Time Code reviewed & RIDs resolved

• WG ready to disband once Pink Sheets are published

• WG has done validation prototyping, finalizing interoperability report

W ki G S Sit tiWorking Group Summary Situation:

status: OK CAUTION PROBLEMstatus: OK CAUTION PROBLEM

Ready to complete Waiting on report



6.6. Time Correlation & Synchronization Time Correlation & Synchronization BoFBoF

Goals: • Develop outline for White Paper and requirements for time correlation

and synchronization standards

• Develop WG charter once need is demonstrated

Working Group Status:Working Group Status:• Met at ESTEC, three agencies and three NASA centers in attendance (total

of 9 attendees)

• Developed draft set of requirements and vision of possible standardsp q p

• Plan for monthly telecons to pursue maturation of the concepts

BoF Summary Situation:


Start‐up Requires agency support and follow


ppthrough

7.7. XML Standards & Guidelines SIGXML Standards & Guidelines SIG


Goals: • Develop a set of common standards and guidelines for XML use across CCSDS

• Coordinate work in other WGs (MOIMS/Nav, MOIMS/SM&C, CSS/SMWG, ( / , / , / ,SEA/IAWG)

• Product will be a CCSDS URN namespace and set of guidelines for all CCSDS WGs

Working Group Status:• URN delayed while IESG revises its procedures

• Will develop CCSDS internal namespace use rules YB assuming future CCSDS URN approval

• Intend to develop CCSDS XML Guidelines YB based on current best practice, hopefully draft by mid June 08, not done

• No meetings last three working sessions, work is to be folded into new SOA BoF

SIG Summary Situation:


Work stalled: No resources


Work stalled: No resources, Disband SIG



D. Cross Area Meetings• Joint IA/IPR Meeting

• Reviewed registry‐repository service architectures for compatibility• Discussed current general and XML specific prototyping efforts and opportunities for testing with other groups (SM SANA SM&C)opportunities for testing with other groups (SM, SANA, SM&C)

• Discussed relationship of registry‐repository standards to Space Information Services Architecture (SOA) reference model and related service architecture

• Developed a compatible and integrated view, shared by four agencies, but unable to agree to form a single new WG to tackle the effort

• Joint SM/IA/IPR Meeting• Discussed the outcome of the Super‐BOF and what the overall map of CCSDS services must cover

• Discussed what the Space Information Services Architecture (SOA) reference model and service architecture must cover and its relationship to the rest of the CCSDS services

• Sec WG / SDLS Meeting• Sec WG / SDLS Meeting• Joint meeting was productive and work is reported in SLS• Some open issues in the area of just how and where the security block is to be inserted in the space link frames, now three different options on the table

• Will require agency resources for interoperability testing


Will require agency resources for interoperability testing


D. Cross Area Meetings, contd

• Super BoF• Reviewed visions of what a “SOA for Space” might be, as presented by

D. Cross Area Meetings, contd

Reviewed visions of what a SOA for Space might be, as presented by CESG chair and MOIMS, SEA and CSS ADs

• Identified at least four different variants on how “SOA for Space” and “Services” were being interpreted across CCSDS

• Agreed to initiate a BoF to develop a charter for a CCSDS ReferenceAgreed to initiate a BoF to develop a charter for a CCSDS Reference Architecture (or Model) that would map all CCSDS services and their relationships (see CSS presentation for details)

• SEA view is that a Space Information Services Architecture (e.g. SOA for Space) is different than the CCSDS Reference Architecture:- Define a reference end-to-end space information service architecture for

interoperability and cross support - Common framework and elements- Both flight and ground data system operations

- Define standard components and services, including their specifications- Define secure deployment and federation models for information services- Define and leverage common methods for representing information models - Develop best practices for the design of standard data definitions, including

XML schemas data dictionaries and common registries

cesg-115

XML schemas, data dictionaries, and common registries

04 November 2009



• IA WG• RASIM Reference ModelGreen Book Ready for final CESG review


• General Registry‐Repository White Book in preparation (Feb 2010)• XML Registry‐Repository White Book in preparation (Mar 2010)• Information Services Architecture Concept Paper planned (Jan 2010)• Information Model Green Book in preparation (Apr 2010)p p ( p )

• Sec WG• Security Architecture Magenta Book being finalized (Dec 2009)• Security Algorithms Integrated Red Book in preparation (Jan 2010)• Security Algorithms Integrated Red Book in preparation (Jan 2010)• Key Management Green Book in preparation (Dec 2009)• Symmetric Key Management White Book in planning (BB), scope (Dec 2009)• Mission Planners Security Guide Green Book in preparation (Apr 2010)

N k L S i Whi P i l i (F b 2010)• Network Layer Security White Paper in planning (Feb 2010)• Security WG Overview Presentation for CCSDS WGs (Dec 2009)


Systems Engineering Area ReportSystems Engineering Area ReportE. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD,

• Delta DOR WG• D‐DOR Reference Model Red Book 2 (MB) Ready for final Agency review

(Feb 2010)

E. SUMMARY: MAJOR ACCOMPLISHMENTS AND CONCERNS IN LAST REPORTING PERIOD, contd

(Feb 2010)• D‐DOR Data Exchange White Book 1 (BB) being finalized for Agency

review (May 2010)• D‐DOR Overview Green Book 1 in preparation for area review

(May 2010)(May 2010)

• SANA WG• SANA Yellow Book Ready for final CESG review• SANA P d Y ll B k t b d l d (F b 2010)• SANA Procedures Yellow Book to be developed (Feb 2010)

• Time Code WG• Time Code Pink Sheets Ready for final CESG review• Time Code Test Report Yellow Book in preparation (Dec 2009)

• Time Synchronization & Correlation BoF• Time Sync & Correlation White Paper in discussion

cesg-117

Time Sync & Correlation White Paper in discussion• Time Sync & Correlation WG Charter in discussion

04 November 2009

CESG CESG FALL FALL 2009:2009:items brought to attentionitems brought to attention

of the CMCof the CMCof the CMCof the CMC


IOAGIOAG‐‐13 Communiqués13 CommuniquésIOAGIOAG‐‐13 Communiqués13 Communiqués

to CCSDSto CCSDS

cesg-119

01 October 2009

To: CCSDS Secretariat From: IOAG Secretariat

1.1. IOAG Communiqué of 01 IOAG Communiqué of 01 October 2009October 2009

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 toConcept 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

cesg-120

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.

DESCRIPTION OF SERVICES TO BE

CONSIDERED BY THE CMC FOR THE

CORRESPONDING RESOLUTION OF IOAG 13, WITH

INDICATION OF THE REQUIRED TARGET DATE 6 An end-to-end standard for IOAG recognizes the need to develop a set CONSIDERED BY THE CMC FOR THE

DEVELOPMENT OF FUTURE STANDARDS

IN THE DOMAIN OF CROSS SUPPORT

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

correlating space vehicle clocks and distributing time synchronization information

g pof standards for correlating space vehicle clocks and distributing time synchronization information. The IOAG resolves that this topic needs further engineering assessment and that various

i i i h ld b id ifi dparameters 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.

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.

A b d d l A l k h

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

7 A space-based data relay cross-support transfer service standardfor 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

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

, yp y,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 f r h n in rbit r

The IOAG resolves to request the CCSDS t d fin n int rf t nd rd f rrequested 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

A b f d d b f

for exchanging, e.g.; orbitergeometrical data slant range; off-pointing angle from antenna boresight; relative velocity of orbiter; orbiter elevation seen from the surface element; AOS &

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

cesg-121

engineering assessment. Availability of a standard before the end of CY2014 is not needed. LOS times; etc. for the contact planning and contact plan

generation. . Availability of a standard before the end of CY2014 is not needed.

1 Th CESG h f d BOF hi h h th t k f id tif i th h t d f k f

CESG Analysis of IOAGCESG Analysis of IOAG‐‐13 Communiqué [1]13 Communiqué [1]

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 service architecture• The CESG will transmit the MOIMS “Mission Operations Services Concept” Green Book to IOAG as soon as it

has been updated to be conformant with the scope of this proposed activity

2. The LDPC codes have been sent for Agency Red‐1 review

3. 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:

IOAG Service Catalog 3

CCSDS Mission Operations Service

Architecture

IOAG Service C t l 2

CCSDS Solar System

Internetwork

Architecture

IOAG Service CCSDS Cross Support

Catalog 2 Internetwork Architecture

cesg-122

Catalog 1Support Service

Architecture

4 With t t th CSTS S Li k M it i S i t d b th IOAG ( d CY 2011) thi

CESG Analysis of IOAGCESG Analysis of IOAG‐‐13 Communiqué [2]13 Communiqué [2]

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)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 semanticsmight 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)

cesg-123

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 proposed CCSDS service architecture group exists.

2.2. UntransmittedUntransmitted IOAG Communiqué re: Service Catalog 1 “gap fillers”IOAG Communiqué re: Service Catalog 1 “gap fillers”

IOAG Service CatalogIOAG Service Catalog--11• IOAG has adopted the notion of a phased set of services p pthat Agencies will be asked to cross support:• Catalog‐1: consolidation of space link services (now ‐2015)

• Catlog‐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 still voting on priorities to send to CCSDS

cesg-124

Ground Link

IOAG Service CatalogIOAG Service Catalog--1: Forward1: Forward

IOAG Service Group IOAG Service Types Space Link InterfaceStandards

Ground Link InterfaceStandards

• Radio Frequency and Modulation [RFM]

• SLE Forward CLTU Service [CLTU]

Forward CLTU ServiceModulation [RFM]

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

Service [CLTU]

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

• SLE Forward Space Packet Service [FSP]

very

Ser

vice

s Forward Space Packet Service• TC Space Data Link

Protocol [TC-DLP]• Communications Operation

Procedure-1 [TC-COP]• Radio Frequency and

Modulation [RFM]• SLE Forward AOS

Frame Service [FAOS]

war

d D

ata

Del

i

Forward AOS Frame Service

Modulation [RFM] • TM Synchronization and

Channel Coding [TM-S&C]

• AOS Space Data Link Protocol [AOS]

Frame Service [FAOS]

Forw

Forward File Service

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

[SPP]E l ti S i

• CSTS Forward File Service [CFFS], over

• CSTS Transfer File Service [CFXS]

cesg-125

• Encapsulation Service [ENC]

• CCSDS File Delivery Protocol [CFDP]

IOAG Service CatalogIOAG Service Catalog--1: Return1: ReturnIOAG Service Group IOAG Service Types Space Link Interface Ground Linkp IOAG Service Types Space Link Interface

StandardsGround Link

InterfaceStandards


• SLE Return All Frames [RAF]

Return All Frames ServiceModulation [RFM]

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

[RAF]

Those for “Return All Frames Service” plus:

• SLE Return Channel Frames [RCF]

iver

y S

ervi

ces

Return Channel Frames Service

p• TM Space Data Link

Protocol [TM-DLP]• AOS Space Data Link

Protocol [AOS]

[ ]

Return Operational Control Field • Those for “Return Channel • SLE Return

etur

n D

ata

Del

i Return Operational Control Field Service Frames Service” Operational Control

Field [ROCF]

Return Unframed Telemetry Service

• Those for “Return All Frames Service”

• CSTS Return Unframed Telemetry [RUTM]

Th f “R Ch l CSTS R FilRe

Return File Service

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

[SPP]• Encapsulation Service

[ENC]

• CSTS Return File Service [CRFS] over


cesg-126

[ENC]• CCSDS File Delivery

Protocol [CFDP]

IOAG Service CatalogIOAG Service Catalog--1: Radio Metric1: Radio Metric

IOAG Service Group IOAG Service Types

Space Link Interface

Ground Link Interfaceyp

Standards Standards

Validated Data Radio


• Pseudo-Noise (PN)

• CSTS Offline Radio Metric Service [CORS]

Serv

ices

Validated Data Radio Metric Service Ranging Systems

[PNR]over


• Those for “Validated • CSTS Real Time

Rad

io M

etri

c S

Raw Data Radio Metric Service

• Those for Validated Data Radio Metric Service”

• CSTS Real Time Radio Metric Service [CRTRM]


• CSTS D-DOR Data ServiceR

Delta DOR Service

Modulation [RFM]• Delta-Differential

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

Data Service [DDORS] over


cesg-127

[DDORO]

IOAG Service CatalogIOAG Service Catalog--1: Gap1: Gap AnalysisAnalysis

CSTS File Transfer ServiceCSTS Forward File ServiceCSTS Return File ServiceCS S Offli di i S iCSTS Offline Radio Metric ServiceCSTS Real Time Radio Metric ServiceCSTS Delta DOR ServiceCSTS Engineering Data Monitoring Service SLECSTS Engineering Data Monitoring Service SLE Forward AOS Frame Service SLE Return Unframed Telemetry Service

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

• CESG does not understand the intent or underlying architecture for “CSTS Forward File Service” or CSTS Return File Service and requests a meeting with the IOAG Service Catalog‐2 group to seek further clarification

cesg-128

Issues and ConcernsIssues and Concerns

from thefrom the

Fall 2009 CESG meetingFall 2009 CESG meeting

cesg-129

• CESG ld i t l bli ti f th d t d CCSDS P d M l

CESG General Issues/Concerns [1] CESG General Issues/Concerns [1]

• 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 theirRecommended 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

bl b h h ISO/CCSDS i h d l ill h ld hproblem 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?

cesg-130

• This is a very important operational function fore future international cross support and it needs a permanent and stable parent.

• CESG t th US t t ti i th SCCC h l d d b li


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

• 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. 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-131

• CESG t l d t th t CCSDS d ll hit t l f k i t


• CESG strongly advocates that CCSDS needs an overall architectural framework into which all of its work can be referenced in terms of services, and that it 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 y p p yCSS Area:

Team‐1: Services, Scenarios, Framework

WG

Team‐2: Service Definition Technology28 Feb 1028 Feb 10

WG ConceptWG

FormedMay 09

• 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?

h i fil “f i d f ” b i f h h j k h ld i h

cesg-132

• CESG Chair files a “friend of court” brief that – as the major stakeholder in the outcome –SM&C should be given this job

CESGCESG FALLFALL 20092009CESG CESG FALL FALL 20092009MEETING STATISTICSMEETING STATISTICS


Fall Fall 2009 Total Attendance2009 Total Attendance

140

Participants/Day

100

120

NOT YET AVAILABLE60

80

Part

icip

ants

NOT YET AVAILABLE

40

0

20

Day


Fall Fall 2009 Attendance By Sponsoring Agency2009 Attendance By Sponsoring Agency

40

45

30

35

NOT YET AVAILABLE20

25 NOT YET AVAILABLE

10

15

0

5

NASA ESA CNES DLR FSA JAXA BNSC ASI CSA INPE CSA


NASA ESA CNES DLR FSA JAXA BNSC ASI CSA INPE CSA

Fall Fall 2009 Daily Attendance By Area2009 Daily Attendance By Area

NOT YET AVAILABLE


Fall Fall 2009 Daily Room Utilization2009 Daily Room Utilization

Requested UsedRequested Used

Rooms/Day

12

14

NOT YET AVAILABLE8

10

pant

s

NOT YET AVAILABLE

4

6Part

icip

2

4


0

ccsds engineering group: report to the

Documents