<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2058164770;
mso-list-type:hybrid;
mso-list-template-ids:-2004034506 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Gian Paolo,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks for the thoughtful response to my questions. I would like to clarify my references to CCSDS 415, which I intended to use as an example of something other
than CCSDS 401.0, more than as an explicit target RF & Mod standard.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Until CCSDS introduced VCM, it was simple and appropriate to align the CCSDS Sync and Channel Coding (S&CC) and RF & Mod Recommended Standards with the S&CC Sublayer
and Physical Layer (respectively) of the CCSDS layered model. The <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Conveniently, in the case of CCSDS 401, both the modulation
<b>and</b> RF aspects of the space Physical Layer <b>are</b> addressed, so that any protocol profile that places a non-VCM S&CC on top of 401 does indeed address everything, including the RF requirements needed to produce (as called in CCSDS 231.0) “Modulated
Radio Waveforms”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">However, in the case of VCM Type 1* (i.e., SCCC-style VCM), contrary to the depiction of the VCM protocols corresponding to the full CCSDS Physical Layer, the
recommendations do not address the RF aspects of the Physical Layer. As you confirmed below, CCSDS 401.0 is normatively cited
<b>only</b> with respect to the modulation definitions. CCSDS 131.2 and 431.1 are mute on RF requirements.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">[*I am uncertain about whether this claim also applies to VCM Type 2 (i.e., DVB-S2-style VCM). If the DVB-S2 specifications define all of the RF aspects and those
RF aspects are appropriate to civil space applications, then this is NOT an issue for Type 2 VCM. ]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">My use of 415 as a “straw man” alternative was perhaps not the best example. But what I was attempting to address is that, at least for Type 1 VCM, there is no
indication of the requirements or expectations regarding RF. I am not an “RF person”, so perhaps the answer is so obvious to any practitioner in the field that is not necessary to “state the obvious”. However, from my past protocol work I am used to writing
statements about requirements on “the underlying layer”, and from my SLE/CSTS work I am used to specifying the requirements on the underlying production process. It seems strange to me to just leave the RF aspects unaddressed (even by reference) in documents
that are nominally supposed to address them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Finally, here are two more observations that I forgot to include in my earlier email:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">CCSDS 131.2-B-1 (<i>Flexible Advanced Coding …</i> ) specifies that transfer frames be pseudo-randomized before the ASMs are attached to create CADUs.
CADUs are the appropriate term because pseudo-randomization is applied to the frames.
<br>
<br>
CCSDS 431.1-B-1 (VCM Protocol) splits the functionality into “SMTF Stream Generation” and “VCM Protocol”, but only the VCM Protocol is normatively addressed. SMTF Stream Generation is only discussed informatively (in section 3.1 – DISCUSSION), where it is described
as simply being the attachment of ASMs directly to the transfer frames to create appropriately-named SMTFs. In the case of Type 1 VCM using SCCC codes, this ignores the pseudo-randomization requirement of CCSDS 131.2-B-1. Is that randomization requirement
no longer in effect? If it is in effect, CCSDS 431.1-B-1 should be updated to address it. Would the randomization requirement apply to only Type 1 VCM using SCCC, or to Type 1 VCM using TM codes as well?
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The list of Managed Parameters in CCSDS 431.1 (VCM Protocol) specifies five managed parameters, CCSDS 131.2-B-1 (SCCC) specifies seven managed parameters,
and CCSDS 131.3-B-1 (CCSDS SLP over DVB-S2) specifies twelve managed parameters. If CCSDS 431.1 encompasses CCSDS 131.2-B-1 and CCSDS 131.3-B-1, it seems as though its list of managed parameters should include more parameters from those other “component” Blue
Books (e.g., Baseband pulse shaping roll-off factor and Scrambling code number?).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks again for your consideration of my questions and observations.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Gian.Paolo.Calzolari@esa.int [mailto:Gian.Paolo.Calzolari@esa.int]
<br>
<b>Sent:</b> Tuesday, April 6, 2021 6:43 PM<br>
<b>To:</b> John Pietras <john.pietras@gst.com><br>
<b>Cc:</b> sea-sa@mailman.ccsds.org; Jon Hamkins <jon.hamkins@jpl.nasa.gov>; Dudal Clement <Clement.Dudal@cnes.fr>; Lee, Dennis K (332G) <dennis.k.lee@jpl.nasa.gov>; Enrico.Vassallo@esa.int; Gilles.Moury@cnes.fr; Andrews, Kenneth S(332B) <Kenneth.S.Andrews@jpl.nasa.gov>;
Massimo.Bertinelli@esa.int; Andrea.Modenini@esa.int<br>
<b>Subject:</b> SLS reply: [Sea-sa] Notes on VCM, DVB-S2, and SCCC<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">John,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> after some coordination with other SLS representatives, please find here below mixed in your text (<b><span style="color:red">marked in bold red and starting with >>></span></b>).</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Further clarifications may follow.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">PS Please consider that Monday 6 April was a Public Holiday in most of Europe.</span>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"John Pietras" <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"<a href="mailto:sea-sa@mailman.ccsds.org">sea-sa@mailman.ccsds.org</a>" <<a href="mailto:sea-sa@mailman.ccsds.org">sea-sa@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">31-03-21 17:53</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">[Sea-sa] Notes on VCM, DVB-S2, and SCCC</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SEA-SA" <<a href="mailto:sea-sa-bounces@mailman.ccsds.org">sea-sa-bounces@mailman.ccsds.org</a>></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">SEA-SAWG colleagues ---</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">I’ve been wading through the
<i>Flexible Advanced Coding and Modulation Scheme for High Rate Telemetry Applications</i> Blue Book (CCSDS 131.2-B-1, March 2012, hereinafter referred to as SCCC [for Serial Concatenated Convolutional Code]),
<i>CCSDS Space Link Protocols Over ETSI DVB-S2 Standard</i> (CCSDS 131.3-B-1, March 2013, hereinafter simply referred to as CCSDS/DVB-S2), and
<i>Variable Code Modulation Protocol</i> (CCSDS 431.1-B-1, February 2021) and comments from reviewers of the ARD table 6-8, trying to understand the relationships among these various VCM schemes.
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">This email recaps my observations and the questions that my reading has raised. Ultimately my concern is to be able to represent this area correctly (albeit abstractly)
in the SCCS-ARD. I would very much appreciate any feedback about the correctness of my interpretations.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Calibri",sans-serif;color:red">>>> SLS do appreciate do appreciate your concern to correctly represent this.</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">A. SCCC (CCSDS 131.2-B-1, March 2012)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">The SCCC protocol stack diagram (figure 2-1) indicates the it covers the CCSDS Sync and Channel Coding Sublayer and the Physical Layer:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><img border="0" width="610" height="379" id="_x0000_i1026" src="cid:image001.gif@01D72B93.AD6986C0"><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">An introductory paragraph that precedes this diagram states “The Synchronization and Channel Coding Sublayer provides methods of</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">synchronization and channel coding for transferring Transfer Frames over a space link while the Physical Layer provides the RF and modulation methods for transferring
a stream of bits over a space link in a single direction.”</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">However, the SCCC specification addresses only some aspects of the Physical Layer - specification of the five modulation schemes to be used as part of SCCC:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">1) QPSK (specified by cross reference to the appropriate definition in CCSDS 401.0):</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">2) 8PSK</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">3) 16APSK</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">4) 32APSK</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">5) 64APSK</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">and coding rates.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">The “RF” aspects of the Physical Layer of a space link (frequency bands, polarization, etc., etc.) are not mentioned at all. So the protocol stack diagram is at least
partially misrepresentative. There should be another “RF Physical sublayer” under the
<i>Flexible Advanced Coding and Modulation Scheme for High Rate Telemetry Applications</i> “layer”. But this raises another issue – what CCSDS Blue Books (or what parts of what CCSDS Blue Books) would constitute such an RF Physical sublayer? CCSDS 401.0 is
referenced, but only with respect to the specification of QPSK modulation. Is it assumed that 401.0 supplies the underlying RF functions? CCSDS also has CCSDS 415.1 (<i>Data Transmission and PN Ranging for 2 GHz CDMA Link via Data Relay Satellite</i>) – is
SCCC viable for use over 415.1 links? [Note – the SCCS-ARD does not include CCSDS 415.1 because it is currently used only for the NASA TDRSS-based Space Network. But the authors of the SCCC book should not ignore the implications for use of SCCC over something
other than 401.0, and how to address such possible wider usage in the SCCC blue book.]</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Calibri",sans-serif;color:red">>>> Indeed 401.0-B (
</span></b><a href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.ccsds.org%2FPubs%2F401x0b31.pdf&data=04%7C01%7Cjohn.pietras%40gst.com%7Cb7448a0473974ee7623808d8f94d6683%7C17917f83951e48839dd6b11685623b38%7C1%7C0%7C637533458127636936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YRis4GezmVt1wc%2B%2BRfwT0o45lsOdiinZC8qu8W0TuZo%3D&reserved=0"><b><span style="font-family:"Calibri",sans-serif">https://public.ccsds.org/Pubs/401x0b31.pdf</span></b></a><b><span style="font-family:"Calibri",sans-serif;color:red">
) contains other regulations in addition to modulations. This is visible in section 1.4 DOCUMENT FORMAT. By convention those other conventions are never mentioned explicitly in the standards referring to 401.0-B. It is clear that modulations are not used ignoring
the rest of the regulations and this is considered implicit and it has never given implementation problems.</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Calibri",sans-serif;color:red">>>> SCCC in NOT intended for use over 415.1 links. In fact, that book is not mentioned in SCCC.</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Some other observations:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">a) The book – written in 2012 – normatively references only the TM and AOS space data link protocols. SCCC depends on the use of the Frame Error Control Field (as
defined in the TM and AOS SDLPs) to perform Frame Validation. SCCC is also expected to be used to carry fixed-length USLP frames, so USLP (at least the specification of the FECF in the USLP frame) is normative on the SCCC.
<b><span style="color:red">>>> SCCC is going to add USLP Frames and the normative references will be listed together with TM SDLP and AOS. Andrea Modeninini as book Editor is preparing the relevant draft.</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">b) In section 2.3 (Internal Organization), the document describes the Sending End (section 2.3.1) using diagrams of the individual functions involved and the “stream
format at different stages of process”. However, the description of the Receiving End (2.3.2) consists of “At the receiving end, the Synchronization and Channel Coding Sublayer accepts a continuous and contiguous stream of physical channel symbols, performs
functions selected for the mission, and delivers Transfer Frames to the Data Link Protocol Sublayer.” Besides saying nothing about how this is done, this description is inconsistent with the declared scope of SCCC as performing functions in in the Physical
Layer as well as the Synchronization and Channel Coding Sublayer. <b><span style="color:red">>>> In a few cases some remarks on the receiving side are mentioned when relevant, however, specification of receivers is not part of our standards. The output at
the sending side shall be unique while at the receiving side several algorithm can be used to correctty process the received stream. This is valid for decoding, demodulation, decompression, decrypt, etc. >>> However you are correct, the book will mention
that also the receiving side performs functions in in the Physical Layer and in the Synchronization and Channel Coding Sublayer.
</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">c) Section 7.1.1 states “Frame synchronization is necessary for subsequent processing of the Transfer Frames. Furthermore, it is necessary for synchronization of
the pseudo-random generator, <i>if used</i> (see section 8).} [italicization mine]. Section 8.1 states “The Pseudo-Randomizer defined in reference [1] is always required by SCCC”. The “if used” qualifier in 7.1.1 seems superfluous since 8.1 says that it must
be used, and could lead to misunderstanding that randomization might be optional. <b><span style="color:red">>>> Andrea Modeninini as book Editor is preparing the relevant draft and will take of this editorial improvement.</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">d) This is a nit-pick, but the acronyms “PSK”, “QPSK”, and “APSK” are never spelled out or listed in the acronym list. I already knew what “PSK” and “QPSK” stood
for, but had to Google “APSK” to get “amplitude and phase shift keying”. <b><span style="color:red">>>> Andrea Modeninini as book Editor is preparing the relevant draft and will take of this editorial improvement together with Tom Gannett for completing the
list of acronyms.</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">I see from the CCSDS Framework that an update to this document is underway. Perhaps these comments will be useful to the C&S WG.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">B. CCSDS/DVB-S2 (CCSDS 131.3-B-1, March 2013)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">The following figure is presented in the Blue Book to relate the functions defined in the CCSDS/DVB-S2 Blue Book to the OIS and CCSDS layered models:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><img border="0" width="474" height="322" id="_x0000_i1027" src="cid:image002.gif@01D72B93.AD6986C0"><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Other than the relatively-simple “CADU Stream Generation” sublayer, the great majority of the functionality of this book is specified by reference to the DVB-S2 specification
that was in effect as of the time of specification of this Recommended Standard, which is given in the normative References as</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">[1] <i>Digital Video Broadcasting (DVB); Second Generation Framing Structure, ChannelCoding and Modulation Systems for Broadcasting, Interactive Services, News Gathering
and other Broadband Satellite Applications</i>. ETSI EN 302 307 V1.2.1<i> </i>(2009-08). Sophia-Antipolis: ETSI, 2009.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">NOTE – ETSI standards are available for free download at
</span><a href="https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.etsi.org%2F&data=04%7C01%7Cjohn.pietras%40gst.com%7Cb7448a0473974ee7623808d8f94d6683%7C17917f83951e48839dd6b11685623b38%7C1%7C0%7C637533458127646928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=oqb1o%2B%2Bt6s6tGyfPS7cejjQbirekhC7ACYOhbu9426Q%3D&reserved=0"><span style="font-family:"Calibri",sans-serif">http://www.etsi.org</span></a><span style="font-family:"Calibri",sans-serif">.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">In attempting to use the link to obtain a copy of the document, I searched on the document number (ETSI EN 302 307 V1.2.1). There was no document with this number available,
but three with variations on the number: </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">- DVB-S2: ETSI EN 302 307 V1.3.1 (2013-03),</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">- DVB-S2, Part1, DVB-S2: ETSI EN 302 307-1 V1.4.1 (2014-11), and
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">- DVB-S2, Part2, DVB-S2 Extensions: ETSI EN 302 307-2 V1.2.1 (2020-08).
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">My interpretation is that the Part 1 (2014) and Part 2 (2020) versions are replacements for the 2008 and 2013 DVB-S2 (no parts) version and update (respectively), although
the documents don’t say that in so many words. Without a better understanding of the applicable technologies, I am unable to determine (or even guess) which Parts (1, 2, or both) are applicable to the use of DVB-S2 for the encoding and transmission of CCSDS
SDLP frames. <b><span style="color:red">>>> CNES has prepared an updated document that should start soon Agency Review. The CMC Approval versuon still refernces ETSI EN 302 307 V1.2.1. I think that the standard is really intended for use with V1.2.1 and not
with later versions.</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">I am unable to say for certain, but it also appears that neither the Part 1 nor the Part 2 specifications address complete set of RF requirements to a level similar to
that found in CCSDS 401.0. If my impression is correct in this respect, as with the SCCC book it is somewhat incorrect to imply that the DVB-S2 specifications address all aspects of the Physical Layer, as is implied by Figure 2-1 (copied above). Again, should
there be some “RF Physical sublayer” under the DVD-S2 transmission sublayer? And if so, are some subset of functions defined in CCSDS 401.0 assumed to satisfy the requirements for that RF Physical sublayer? What about DVB-S2 “over” CCSDS 415.1 links?</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Calibri",sans-serif;color:red">>>> Please consider the SCCC reply above for 401.0-B.
</span></b><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">C. VCM Protocol (CCSDS 431.1-B-1, February 2021)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Figure 2-1 of the VCM Protocol Blue Book is:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><img border="0" width="583" height="435" id="_x0000_i1028" src="cid:image003.gif@01D72B93.AD6986C0"><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Note that the “SMTF Stream Generation” function/sublayer is exactly the same as the “CADU Stream Generation” function/sublayer of the CCSDS/DVB-S2 Blue Book: “SMTF” is
the more-appropriate term for a transfer frame that is pre-pended with an ASM, whereas “CADU” in general allows the possibility of intermediate encoding being applied before the ASM. <b><span style="color:red">>>> C&S WG may consider using a uniform term.
Andrea & Ken may consider thois point of discussion.</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Regarding the VCM Protocol itself, the blue book specifies three sets of “modes”:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">- Modes that apply to CCSDS Turbo and LDPC encoding (a subset of, and as defined in, CCSDS 131.0-B). These are the “TM” codes;</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">- Modes that apply to SCCC encoding. These modes are “consistent with the existing specification of codes, modulations, and VCM protocol given in references [2]
[SCCC Blue Book] and [5] [CCSDS 401.0]”; and</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">- Modes that apply to CCSDS DVB-S2 encoding. These mode are “consistent with the existing specification of codes, modulations, and VCM protocol given in references
[3] [CCSDS/DVB-S2], [4] [the <i>2014 version</i> of DVB-S2: Part 2], and [5] [CCSDS 401.0]”.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Type 2 VCM has a set of modes that apply to CCSDS Turbo and LDPC coding schemes (as defined in CCSDS 131.0-B) and a different set of codes for DVB-S2. The difference
between Type 1 and </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">The VCM BB defines two VCM protocol “Types”: Type 1 and Type 2. The two Types differ in the values for the parameters H (the length of the PLFRAME header, S (the number
of codeword modulation symbols between pilot symbol blocks), and P (the number of modulation symbols present in each optional symbol block). Type 1 uses the H/S/P values that have already been defined in the SCCC Blue Book, and Type 2 uses the H/S/P values
that have already been defined in the CCSDS/DVB-S2 Blue Book and the ETSI DVB-S2: Part 2 standard.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">What the VCM Blue Book specifies
<i>uniquely</i> is the use of TM Turbo and LDPC encoding, which is defined for both VCM Type 1 and VCM Type 2. However, the material regarding SCCC encoding and DVB-S2 encoding appears to me to be simply a restatement of existing material that is already normatively
stated in the SCCC Blue Book, CCSDS/DVB-S2 Blue Book, and the ETSI DVB-S2: Part 2 standard. Is there is something that the VCM Protocol BB adds to the existing standards?
<b><span style="color:red">>>> The 431.1-B VCM standard does not alter the specification of the 131.2-B and 131.3-B VCM protocols. This means that a user of SCCC or DVB-S2 codes compliant with 131.2-B or 131.3-B will also comply with 431.1-B. The 431.1-B book
puts the VCM protocol under a common umbrella to help explain how to use TM codes with either of the SCCC or DVB-S2 approaches to VCM. This has the side benefit of showing that there really is one common VCM approach in CCSDS..</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">The fact that the VCM Protocol book restates and in a sense co-opts the SCCC and CCSDS/DVB-S2 Blue Books can lead to ambiguity.
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Calibri",sans-serif;color:red">>>> This situation is no different than the 401.0-B incorporating the definitions of the higher order modulations which are already described in 131.2-B
and 131.3-B. They are the same, so there is no ambiguity.</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">When one refers to “CCSDS VCM”, should that be interpreted as a blanket reference to “TM VCM”, SCCC VCM, and DVB-S2 VCM, or do we want to continue to cull out the different
flavors separately? For the purposes of the SCCS-ARD, we might want to just use “CCSDS VCM” to collectively refer to all flavors, with a single reference to CCSDS 431.1, and have a separate (simple, high-level) “discussion” of the components of that collective
protocol. That will certainly make the tables in the ARD simpler.<b> <span style="color:red">
>>> Agreed. There really is only one approach to VCM in CCSDS. OK for SCCS-ARD to just use “CCSDS VCM” to collectively refer to all flavors. However referincg may better include all the books for those willing to look at the details .</span></b></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Calibri",sans-serif"> </span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Finally, as with the SCCC and CCSDS/DVB-S2 blue books, the VCM Protocol Blue Book does not address the RF aspects of the Physical Layer. The same questions apply about
whether an RF Physical sublayer should be called out, whether and what aspects of CCSDS 401.0 meet the requirements for such a sublayer, and whether other space link physical layer specifications (such as CCSDS 415) can be used for VCM.
<b><span style="color:red">>>> Please consider the SCCC reply above for 401.0-B. </span>
</b> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Best regards,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">John</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SEA-SA mailing list</tt><br>
<tt><a href="mailto:SEA-SA@mailman.ccsds.org">SEA-SA@mailman.ccsds.org</a></tt><br>
</span><a href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsea-sa&data=04%7C01%7Cjohn.pietras%40gst.com%7Cb7448a0473974ee7623808d8f94d6683%7C17917f83951e48839dd6b11685623b38%7C1%7C0%7C637533458127646928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=29oNZ2bpK28DR0O44Td4ntyNnAoo6%2B1sRdzscp%2Bsmbw%3D&reserved=0"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa</span></tt></a><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>