[Css-csts] MD-CSTS W-0.8 on CWE

Thu Aug 27 08:49:50 EDT 2009

Dear John,

Please find here below a few comments or questions on your 2 following documents : "version 0.8 of the MD-CSTS White Book" and  "Baseline Functional Resources for the CCSDS Monitored Data Cross Support Transfer Service" :  

version 0.8 of the MD-CSTS White Book :

1- Section 2.5.2 Service Provision, end of Page 2-7 : "In performing the Notification procedure of the MD-CSTS,..."  We should find "Information Query" instead of "Notification" .

2- Section 2.6 Operational scenario, middle of page 2-10 : "The MD-CSTS provider invokes the TRANSFER-DATA operation to report the values of the two-second-interval monitored parameters : Each invocation of the TRANSFER-DATA operation for this instance of the Cyclic Report procedure transfer the following data :"
Reading this last sentence, I can understand that we need a TRANSFER DATA operation for each transfer of data.  What do you think of :  "One invocation of  the TRANSFER-DATA operation for this instance of the Cyclic Report procedure transfers periodically the following data :"

3- Same thing 5 lines below for the ten-second-interval monitored parameters.

4- Section 5.2.2 (relative distinguished name of a parameter) : the definition and syntax for a relative distinguished name of a parameter has already been given in 4.6.2

5- Section 5.3.2 (relative distinguished name of a notifiable event) : the definition and syntax for a relative distinguished name of a notifiable event has already been given in 4.7.2

Baseline Functional Resources for the CCSDS Monitored Data Cross Support Transfer Service :

1- introduction : "The CCSDS will define a standard set of functional resources and monitored parameters... " Do you mean CCSDS or MD-CSTS ?
Same thing 10 lines below : "This baseline set can serve as a starting point for the development of the CCSDS common monitored parameters catalog,..." 
CCSDS or MD-CSTS ?

2- Section 4, Figure 2 : Baseline Functional Groups and Their Associated Functional Resources : In the box "forward TC VC Data insertion Functional group"  we should find the box "FSP TS Provider" instead of "FCLTU TS Provider"
3- Section 4, Figure 3 : Baseline Functional Resources and Their Associated Functional Resources : On the forward link, the box "FCLTU TS Provider" is duplicated. The box "FSP TS provider" is missing.

4- Table A-6. Event Types for the Forward Space Link Symbol Stream Functional Resource : Why 'production interrupted' and 'production configured' are not they present in this table ?

5- Table A1-3. Monitored Parameter Types for the Return Space Link Subcarrier Functional Resource : should be "Table A-13"

6- Section A14.8 :"The standard notifiable event types 'production configured', 'production interrupted', production halted', 'production operational', transfer service bound', transfer service active', and 'transfer service unbound' are associated with all SLE transfer service provider functional resources".  The 2 events 'production configured' and 'production operational' don't exist in the SLE return functional group.

Best regards.

François

-----Message d'origine-----
De : css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org] De la part de John Pietras
Envoyé : lundi 10 août 2009 17:37
À : css-csts at mailman.ccsds.org
Objet : [Css-csts] MD-CSTS W-0.8 on CWE

CSTSWG colleagues ---

I have uploaded to the CWE version 0.8 of the MD-CSTS White Book at URL http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/MonitoredDataCSTS/MonitoredDataCSTS_W-0.8.doc

or http://tinyurl.com/MD-CSTS-W-0-8

The new version reflects the review comments received on V0.7 at the Colorado Springs meeting. Specific changes include:

-   Removal of functional group specifics from section 2, replaced with functional resource terminology.

-   Deletion of functional resource annexes A-E

-   Changed "distinguished name" to "relative distinguished name"

-   Modified the Operational Scenario to deal with functional resources.

-   Modified the service composition table to reflect the version identification decisions.

-   Combined the lists of cyclically-reported and queriable monitored parameters in section 4.

-   Reference and external (TBD) standard for monitored parameters and event notifications, instead of the Annexes that previously held this information.

PLEASE NOTE that while this version reflects the notion of functional resources and their use in the naming of monitored parameters and notifiable events, this version DOES NOT incorporate the shorthand method for subscribing to those parameters in the START and GET operations. As described in my email of 7/24, using the shorthand method (in which only the parameter type is used in the subscription, but the full collection of instances of that type are reported) is not possible to perform without extending the associated procedures of the CSTS Framework. I had proposed the shorthand notation as a way of addressing potential issues in providing services to highly flexible missions with large numbers of possible monitored parameters, only a subset of which might be active for a given Service Package. However, since this shorthand method is still under analysis and discussion, I decided that it would be a good idea to post a version of the MD-CSTS specification that uses purely adopted procedures so that we will have that as a new baseline to work from. 

Best regards,

John 

John Pietras

GST, Inc. 

7855 Walker Drive, Suite 200

Greenbelt, MD 20770

240-542-1155

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20090827/2ce38c66/attachment-0001.htm