Status of CCSDS work Status of CCSDS work in response to IOAG in response to IOAG

ResolutionsResolutions

IOAG-11June18, 2007

Cebreros, Spain

Adrian Hooke (NASA) and Nestor Peccia (ESA)CCSDS Technical Liaisons

2

Consultative Committee for Space Data Systems (CCSDS)

ASI/Italy

BNSC/UK

CNES/France

CSA/Canada

DLR/Germany

ESA/Europe

FSA/Russia

INPE/Brazil

JAXA/Japan

NASA/USA

ASA/Austria

CAS/China

CAST/China

CRC/Canada

CRL/Japan

CSIR/S.Africa

CSIRO/Australia

CTA/Brazil

DSR/Denmark

EUMETSAT/Europe

EUTELSAT/Europe

FSST&CA/Belgium

HNSC/Greece

IKI/Russia

ISAS/Japan

ISRO/India

KARI/Korea

KFKI/Hungary

MOC/Israel

NCST/USA

NOAA/USA

NSPO/Taipei

SSC/Sweden

TsNIIMash/Russia

USGS/USA

3

CCSDS Technical Context: Six Focus Areas

Cross SupportServices

Spacecraft

OnboardInterfaceServices

SpaceInternetworking

Services

SpaceLink

Services

Mission Operationsand Information

Management Services

Systems Engineering

4

CCSDS Technical Context: Twenty Three Active Working Groups

-- Service Management-- Cross Support Transfer Services

-- CFDP Testing-- Cislunar Space Internet.-- Asynchronous Messaging-- IP-over-CCSDS Links

-- RF & Modulation -- Space Link Coding & Sync. -- Data Compression-- Space Link Protocols -- TC Channel Coding-- Ranging -- High Rate Uplink

-- Data Archive Ingestion-- Navigation -- Info. Pack. & Registries-- Spacecraft Mon. & Control

-- Systems Architecture-- Security-- Information Architecture-- Space Addressing and Naming

-- Onboard Subnet. Services -- Onboard Application Services

5

Current CCSDS Program of Work: Area Directors and Working Group Chairs

POSITION CHAIR DEPUTY CCSDS Eng. Steering Group A. Hooke/NASA N. Peccia/ESA SYSTEMS ENGINEERING AREA P. Shames/NASA T. Yamada/JAXA 1.1 Systems Architecture WG T. Yamada/JAXA E. Soerensen/ESA 1.2 Security WG H. Weiss/NASA G. Kenney/BNSC 1.3 Information Architecture WG D. Crichton/NASA 1.4 SANA WG K. Nichols/NASA (act) MOIMS AREA N. Peccia/ESA R. Thompson/BNSC 2.1 Data Archive Ingestion WG D. Sawyer/NASA C. Huc/CNES 2.2 Navigation WG D. Berry/NASA J. Fertig/ESA 2.3 Info. Pack. & Registries WG L. Reich/NASA S. Hughes/NASA 2.4 S/C Mon + Control WG M. Merri/ESA R. Thompson/BNSC CROSS SUPPORT SVCS. AREA E. Barkley/NASA Y. Doat/ESA 3.3 Cross Support Svce Mgmt. WG E. Barkley/NASA 3.6 Cross Supt Transfer Svcs. WG Y. Doat/ESA SPACECRAFT O/B I/F AREA P. Plancke/ESA C. Taylor/ESA 4.1 Subnetwork Services WG R. Schnurr/NASA C. Taylor/ESA 4.3 Application Support Svcs. WG S. Fowell/BNSC SPACE LINK SERVICES AREA J-L. Gerner/ESA G. Moury/CNES 5.1 RF & Modulation WG E. Vassallo/ESA 5.2 Space Link Code/Sync. WG G-P. Calzolari/ESA 5.3 Data Compression WG P-S. Yeh/NASA A. Kiely/NASA 5.4 Space Link Protocols WG G. Kazz/NASA 5.5 TC Channel Coding WG G-P. Calzolari/ESA 5.6 Ranging Working Group E. Vassallo/ESA 5.8 High Rate Uplink WG G. Kazz/NASA SPACE INTERNET. SVCS. AREA R. Durst/NASA D. Stanton/BNSC 6.1 CFDP Interop. Testing WG M. Ciccone/ESA 6.3 Space Packet Protocol WG Dai Stanton/BNSC 6.4 Cislunar Space Internet WG K. Scott/NASA 6.5 Asynchronous Messaging WG S. Burleigh/NASA 6.6 IP-over-CCSDS Links WG G. Kazz/NASA

6

(Res 8.5.1) REQUEST FOR A FRAMEWORK FOR CROSS-SUPPORT SERVICE ARCHITECTURE

(Res 8.5.1) REQUEST FOR A FRAMEWORK FOR A CROSS-SUPPORT SERVICES CATALOG

(Res 8.1.1) URGENT NEED FOR A SLE MANAGEMENT SERVICES RECOMMENDATION

(Res 8.4.1) ADVICE ON CROSS-SUPPORT TRANSFER SERVICES WORKING GROUP CHARTER

(Res 8.3.1) ADVICE FOR SIMPLIFICATION OF RF & MOD. RECOMMENDATIONS

(Res 8.7.1) REQUEST FOR A HIGH RATE COMMANDING RECOMMENDATION

(Res 8.8.1) REQUEST FOR A DELTA DOR RECOMMENDATION

(Res 8.2.1) CCSDS STRATEGIC PLAN: SUGGESTED MODIFICATIONS

IOAG-08 RESOLUTIONS

Discussed on

Tuesday’s agenda

Adrian Hooke

Nestor Peccia

7

(8.1.1 and 8.4.1)CCSDS Cross Support Services Area

CSS Area Overview

Service Management Working Group (SMWG)

Leadership

Chair: Erik Barkley, JPL/NASA

Deputy Chair: John Pietras, GST/GSFC/NASA

Deliverables

Service Management Concept Book (Green Book)

Service Management Recommendation (Blue Book)

XML Schema (Virtual Annex to Blue Book)

Prototype Inter-operations, Validation

ESA <--> JPL/NASA

JAXA <--> JPL/NASA

Best Practices Book (Magenta Book)

Cross Support Transfer Service Working Group (CSTSWG)

Leadership

Chair: Yves Doat, ESA

Deputy Chair: (Vacant)

Deliverables

Generic Core Toolkit Concept Book (Green Book)

Generic Core Toolkit Book Recommendation (Blue Book)

Ground Domain Transfer Services (Based on Toolkit)

Return Unframed Telemetry (Blue Book)

Ranging, Radiometric (Blue Book)

Service Production Monitoring (Blue Book)

Prototype Inter-Operations, Validation

ESA <--> JPL/NASA

8

Activity Date

Conceptual Analysis for inclusion of management of Ranging and Radiometric services

June 07

Draft Operations Concept Book (Green Book) June 07

Intermediate Meeting (Red-2 Production Check; Ranging/Radiometric Inclusion Decision)

June 07

Red-2 (Submission to Secretariat’s Office) Dec 07XML Schema Update (Red-2 Compliance) Jan 08Prototype Interoperations (Red-1 Compliant) Now – Dec 07

(8.1.1) Service Management Working Group (SMWG):Major Activities

Erik: could you make this a schedule chart?

9

Service Management Recommendation Red-2

1st Priority

Current projection for submission of Red-2 to secretariat is now December 2007 (was September 2007)

•~35% of overall work required for Red-2 completed

-Excluding ranging, radiometric service management

•Production mostly being done by NASA•Overall resources marginal

W3C XmlSchema 2nd Priority

OK; Schema updates to be sequenced after Red-2 updates

At least two independently developed interoperable prototypes

2nd Priority

Prototype activities are underway •JPL: prototype ready to support inter-operations as of April 2007•ESA: current status indicates interoperations starting ~September•JAXA: current status indicates interoperations starting ~September

Concept Book 3rd Priority

Current projection is that basic Green Book will be available in time for Red-2 Review

•Very slim production resources from BNSC•Insufficent resources for producing advance use cases in document

Best Practices Book 4th Priority

No resources available

(8.1.1) Service Management Working Group (SMWG):Summary Status

10

Significant Changes for Red-2 Status Comments

Support for "Standing Orders" and Generic Scheduling (PropseServicePackage Operation)

Updated conceptual analysis; ~50% of updates needed performed

Modifications to be reviewed and agreed at Interim meeting

Management of Ranging and Radiometric Services

Some preliminary analysis work performed

Analysis done so far is with respect to NASA/DSN sequential tone ranging; Need inputs form other agencies to help define what standardization needs to cover (e.g, ESA PN ranging, etc.); decision for attempt to include in Red-2 pending interim meeting results

Management of Off-line transfer services

~80% of updates needed performed

Modifications to be reviewed and agreed at Interim meeting

Service Package State Diagrams ~50% of work performed To be reviewed at June interm meetingGreater ability to specify default information("Higher-Level" Configuration Profile)

~80% of updates needed performed

Modifications to be reviewed and agreed at Interim meeting

Definition of Support Levels No work done yet

Capability to override configuration parameters on service package basis

~80% of updates needed performed

Modifications to be reviewed and agreed at Interim meeting

Trajectory Submission Process revision

No work done yet

Allow for event sequence information to be expressed bilaterally (Event Sequence Remodelling)

No work done yet

Splitting Up the Recommendation Minor work performed Lower priority relative to completing udates; insufficient resources

Key: In Progress; On Schedule In Progress; Behind Schedule No progress expected at this time Not In Progress; effort abandoned

(8.1.1) Service Management Working Group (SMWG):Detailed Status

11

• Work is in progress in the SLS RFM WG.

• CCSDS (401) recommendations 2.4.17A and 2.4.17B are both being reworked.

• Simultaneously, an update of the Green Book (413) is in progress to reflect the changes in 401.

(8.3.1) RF & Modulation Simplifications

Jean-Luc: could you please add schedule information?

12

(8.7.1) High Rate Uplink

• HRU Working Group met in Colorado Spring in January 2007 but could not identify substantive mission requirements:• NASA presented HRU related “requirements” from Project Constellation. From a CCSDS perspective, these look more like solutions.• Each Agency needs to present its mission scenarios associated with high rate uplinks• NASA claims it has these scenarios but cannot yet share them with other space agencies until management approval is given.• ESA will investigate whether preliminary scenarios are available from the AURORA programme.• A set of CCSDS high rate uplink related requirements has yet to be defined. • The deadline given to the WG of End of Year 2007 for a blue book is deemed very hard to achieve given these constraints.

• HRU-WG requested more definitive requirements from IOAG in April 2007:

Greg: anything to add??

13

• The revised Delta-DOR Operations White Book is at a level of maturity, such that it could be issued for review at CESG level.

• Book will be finally issued as GB; 2nd Half 2007

(8.8.1) Delta DOR

I/F Data Priority Availability Covered by Allocated to1 DOR Tones High Medium Term Partially covered by existing standard

(CCSDS 401 (2.5.6B)B-2)It will be discussed in the next BB update

SLS Ranging WG

2 Raw Data Low Long term Not covered tbd BOF3 Service to tranfer

dataHigh Long term Partially in CSS. Transfer implies

Raw data, ODM, Reduced DataCSS Area

4 ODM High Available NAV ODM Standard (BB) MOIMS NAV WG5 Reduced Data High Medium Term

Available end 07NAV TDM Standard to be checked MOIMS NAV WG

6 Quasar Catalogue (Radio Signals)

Low Long term JPL Quasar catalogue available tbd BOF

Antenna 1 StorageRx

Ground Station 1

Antenna 2 StorageRx

Ground Station 2

Quasar

Correlator

ODM

Reduced Data

Operational Control Centre

1

2

3

4

5

26

14

• The main comments of the IOAG were as follows:1. it should be more than just a vision. A driver is the

development of a long term architecture for cross support services

2. lack in connections to the forward-looking future of the various space agencies

3. lack in planning for standards infusion

4. lack in enganging members for the infusion of each new recommendation

5. how area objectives and goals are ascertained

• Strategic and Operating Plans have to be read together. Both have to be reworked (not only considering IOAG comments, but internal CCSDS discussions)

(8.2.1) CCSDS Strategic Plan

15

• Strategic Plan should be updated according to comment 1

• Comment 2 should be discussed with IOAG. Sometimes the forward looking future of the Agencies is vague or concentrates in one domain (e.g. exploration but not EO)

• Strategic Plan should be updated with Comment 3. Input to be provided regularly (1 year?) by IOAG

• Comment 4 is an illusion. Take as example the CFDP. No strategic Plan will help in the infusion of a new recommendation within an Agency. Paper does not help.

• Strategic and Operating Plans should be updated with Comment 5 (after discussion with IOAG)

(8.2.1) CCSDS Strategic Plan

16

BackupBackup

InformationInformation

17

IOAG 8.1.1 (Resolution aboutCCSDS Service Management Standardization) (1/2)

Resolution Key Points Area Director’s Comments1) One of the highest priorities in terms of expectations by the Member Agencies

Agree•Resource assignments continue to be marginal, not in line with high priority expectations

2) Should avoid detailed parameter definitions

Disagree•Fine for defining general operations guidelines, best practices tutorial•Unrealistic if IOAG is interested in a recommendation affording automation, operational cost reduction•CCSDS SMWG is not inventing parameters

•Parameter derived from real-world tracking operation

-Details, complexity represents nothing more than what is already occurring in real world tracking networks-May appear formidable as real-world parameters are extracted/abstracted and presented all in one document

•Unrealistic given the complex demands of flight projects on tracking networks

•E.g., contingency tracking scenarios, different types of modulation schemes, spacecraft executing autonomous sequences affecting spacelink management, etc.

18

Resolution Key Points Area Director’s Comments

3) Multi-Agency SLE Service Management testbed activity

Agree

4) Select a set of "core capabilities" from thecurrent Red Book-1 which will drive the initial implementations

Agree

5) Capabilities will be transmitted to CCSDS for comments and consideration in the Red Book-2.

Comments have yet to be receivedMay be too late for inclusion in Red-2

6) IOAG suggests that the CCSDS proceeds with the preparation of the Red Book-2

Agree (more on this later)

7) Recommends that no new service is added under this version of the Recommendation that could delay any further the production of the Blue Book

Neutral•Will agency really accept, be able to use a recommendation without ranging, radiometric service management?

IOAG 8.1.1 (Resolution aboutCCSDS Service Management Standardization) (2/2)