[Css-csts] RE: Functional Resources for the Forward Space Packet Service - UPDATE

[John Pietras]

Wolfgang, CSTSWG and CSSMWG colleagues ---
Yesterday I accidentally posted a slightly old draft of the tech note Functional Resource Types or the Forward Space Packet Service. I've just removed that version and posted the most recent version (which I've labeled "0.02") at URL
http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Working%20Materials/Functional%20Resources/FSP_ServiceFunctionalResources_TechNote-TN-0.02.docx

There are two differences between the previous and current versions:

1.       The TC MC Multiplexing FR Type and the TC All Frames Generation FR Type have been combined into the TC MC Multiplexing and Error Control FR Type; and

2.       The FOP FR Type and the TC VC Generation FR Type have been combined into the FOP and TC VC Generation FR Type.

These combinations will reduce (slightly) the number of FR Types and consequently the number of FR instances that we will have to keep track of.

Best regards,
John
From: John Pietras
Sent: Wednesday, March 27, 2013 4:38 PM
To: Wolfgang.Hell at esa.int; CCSDS_CSTSWG (css-csts at mailman.ccsds.org)
Subject: Functional Resources for the Forward Space Packet Service

Wolfgang and CSTSWG colleagues ---
I have been working on an analysis of the functional resource types needed to support the IOAG SC #1 services. This activity has caused the set of functional resource types to evolve from the set used by Wolfgang in his Candidate Monitored Data set documented in the"20120925 CCSDS Candidate Monitored Data OID Representation" spreadsheet. In the IOAG SC #1 analysis, there are a number of production-related functional resource types associated with the FSP service that do not appear in the Candidate Monitored Data spreadsheet. These production FR types expose the different layers of the TC protocol stack (TC Synchronization and Channel Coding [2], TC Space Data Link Protocol [3], and COP-1 [4]) to support the various IOAG services. These new production FR Types can be shared with other IOAG services beyond the FSP service. The IOAG service exercise also resulted in the use of FR Type names that match the names of the corresponding functions and procedures used in the relevant Telecommand CCSDS Recommended Standards.

I've uploaded to the CWE a draft technical note that compares and contrasts the single Forward Space Packet Transfer Service Provider functional resource type identified in the Candidate Monitored Data spreadsheet with the multiple functional resource types that are associated with the Forward Space Packet service in the in-progress Functional Resources for Cross Support Services draft technical note. It is at URL
http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Working%20Materials/Functional%20Resources/FSP_ServiceFunctionalResources_TechNote-TN-0.01.docx

For each FR Type, the corresponding CCSDS Space Link Service function or procedure is identified, along with the Cross Support Reference Model functional group to which the FR Type belongs. For each of the new TC protocol stack FR Types, a set of candidate monitored parameters is proposed. My purpose in writing this technical note is to attempt to identify inconsistencies between the Candidate Monitored Data set - which will be the basis of the SANA registry of cross support functional resource types and their associated parameters, events and directives - and a model of functional resource types that is robust enough to support the set of cross support services that have been identified for standardization.

Note that this draft technical note does not address the new gettable parameters introduced in the draft Pink Sheet version of the SLE FSP Recommended Standard that was released on 22 March 2013. I think that once we arrive at an approach that addresses the modeling of production-related functional resource types we can address these new parameters to their respective FR types.

Best regards,
John


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