<span style=" font-size:10pt;font-family:sans-serif">Peter,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
just a quick clarification.</span>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">In
a few places where it is stated: </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red;font-family:Calibri"><b>>>>
Please consider the SCCC reply above for 401.0-B</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">as
the statement </span><span style=" font-size:12pt"> “</span><span style=" font-size:12pt;color:red"><b>>>>
SCCC in NOT intended for use over 415.1 links. In fact, that book is not
mentioned in SCCC.</b></span><span style=" font-size:10pt;font-family:sans-serif">"
refers to 415.1 and not to 401.0-B, the correct reference is the following
one</span></p>
<br><span style=" font-size:10pt;font-family:sans-serif">----------------------</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red"><b>>>>
Indeed 401.0-B ( </b></span><a href="https://urldefense.us/v3/__https:/public.ccsds.org/Pubs/401x0b31.pdf__;!!PvBDto6Hs4WbVuu7!efnnGUGob28wvg7EItHJSV1crsjHcx6eUUB7Tj84uTdExGvhIl9lcemPsL5rx4hl3oReM1oG$"><span style=" font-size:12pt;color:blue"><b><u>https://public.ccsds.org/Pubs/401x0b31.pdf</u></b></span></a><span style=" font-size:12pt;color:red"><b>
) 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.</b></span></p>
<br><span style=" font-size:10pt;font-family:sans-serif">----------------------</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">You may want to
review your other assertions below according to this.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I guess this will
help everybody and specially the SLS readers.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Best regards</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<br>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int>, "EXTERNAL-Pietras, John V (US
332C-Affiliate)" <john.pietras@gst.com></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Dudal
Clement" <Clement.Dudal@cnes.fr>, "Andrea.Modenini@esa.int"
<Andrea.Modenini@esa.int>, "Lee, Dennis K (US 332G)" <dennis.k.lee@jpl.nasa.gov>,
"Hamkins, Jon (US 3300)" <jon.hamkins@jpl.nasa.gov>, "Gilles.Moury@cnes.fr"
<Gilles.Moury@cnes.fr>, "Andrews, Kenneth S (US 332B)"
<kenneth.s.andrews@jpl.nasa.gov>, "Enrico.Vassallo@esa.int"
<Enrico.Vassallo@esa.int>, "sea-sa@mailman.ccsds.org" <sea-sa@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">07-04-21
01:47</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[EXTERNAL] [Sea-sa] SLS reply: Notes on VCM, DVB-S2, and SCCC</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Gippo,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks
for the replies. It is helpful to keep up this collegial dialogue
as we try and sort out the complexities. John may have some comments
of his own, and I have some materials from our SEA-SA meeting of yesterday
that I will share with all of you once I send this brief note off.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">In
a few places you stated:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red;font-family:Calibri"><b>>>>
Please consider the SCCC reply above for 401.0-B</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">I
am puzzled by some of these references. If you mean only to point
to the statement “</span><span style=" font-size:12pt;color:red"><b>>>>
SCCC in NOT intended for use over 415.1 links. In fact, that book is not
mentioned in SCCC.” </b></span><span style=" font-size:12pt">then this
reference makes sense. We understand that the 415.1 spec is rather
a “stand-alone” standard. It is not clear that we even need
to include it in this document unless there is a strong requirement to
do so.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">For
the others: </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red;font-family:Calibri"><b>>>>
Please consider the SCCC reply above for 401.0-B. </b></span><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">I
think that this “reply for 401.0-B” is only relevant to the 415.1 part
of this, and not to the rest of this statement relating to the relationships
between the SCCC and the physical sub-layer aspects of the 401.0 spec.
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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. </span><span style=" font-size:12pt;color:red"><b>>>>
Please consider the SCCC reply above for 401.0-B. </b></span><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Here
too, I believe that the 415.1 part of this is accurate, but that this leave
unanswered the question about the relationships between DVB and the physical
sub-layer aspects of the 401.0 spec. . The 401.0 spec,
as you are aware, is a thicket of “if this, then that, but not that”
kinds of statements. And it has finely parsed clauses about specific
frequency bands, modulations, data rates, ranging (or not), and directionality.
And SCCC (and DVB) both include 401.0 modulations and somehow subsume
them inside the frame of pilot symbols. It’s not clear from either
the SCCC or DVB specs just which of the possible physical sub-layer and
directionality parts of the 401.0 spec are applicable. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Can
you and your SLS Area team help to clarify these questions?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">In
the context of the 431.0 spec, and its relationship to SCCC and DVB, this
occurs:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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? </span><span style=" font-size:12pt;color:red"><b>>>>
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..</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">I
agree that the 431.0 spec puts all three of the related VCM options under
one umbrella, and that this helps the reader to understand the similarities,
and differences, among these protocols stacks. And it appears to
be the case that a use of SCCC or DVB will, because of the structure of
this document, be compliant with the 431.0 spec. That said, it is
also true that an implementation of SCCC will not be compliant with DVB,
nor will an implementation of DVB be compliant with SCCC, nor, for that
matter, with the one using the CCSDS TM code options. There is not
really “one common VCM approach” in CCSDS, there are three, with some
complex overlaps and interconnections that this book helps to clarify,
but cannot dispel.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">We
do hope to add just enough clarifying material in the SCCS-ARD to make
this as clear as we can. And we will need you help to ensure that
this is as clear as it can be. Please look at the next set of materials
I will send and let us know what you think.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>SEA-SA <sea-sa-bounces@mailman.ccsds.org> on behalf of Gian Paolo
Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Tuesday, April 6, 2021 at 3:43 PM<b><br>
To: </b>John Pietras <john.pietras@gst.com><b><br>
Cc: </b>Dudal Clement <Clement.Dudal@cnes.fr>, "Andrea.Modenini@esa.int"
<Andrea.Modenini@esa.int>, Dennis K Lee <dennis.k.lee@jpl.nasa.gov>,
Jon Hamkins <jon.hamkins@jpl.nasa.gov>, Gilles Moury <Gilles.Moury@cnes.fr>,
Kenneth Andrews <kenneth.s.andrews@jpl.nasa.gov>, "Enrico.Vassallo@esa.int"
<Enrico.Vassallo@esa.int>, SEA-SA <sea-sa@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] [Sea-sa] SLS reply: Notes on VCM, DVB-S2, and SCCC</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">John,</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
after some coordination with other SLS
representatives, please find here below mixed in your text (</span><span style=" font-size:10pt;color:red;font-family:Arial"><b>marked
in bold red and starting with >>></b></span><span style=" font-size:10pt;font-family:Arial">).</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Further clarifications may follow.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Best regards</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Gian Paolo</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
PS Please consider that Monday 6 April was a Public Holiday in most of
Europe.</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"John
Pietras" <john.pietras@gst.com></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"sea-sa@mailman.ccsds.org"
<sea-sa@mailman.ccsds.org></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">31-03-21
17:53</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">[Sea-sa]
Notes on VCM, DVB-S2, and SCCC</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Sent by: </span><span style=" font-size:9pt;font-family:Arial">"SEA-SA"
<sea-sa-bounces@mailman.ccsds.org></span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">SEA-SAWG
colleagues ---</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red"><b>>>>
SLS do appreciate do appreciate your concern to correctly represent this.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">A.
SCCC (CCSDS 131.2-B-1, March 2012)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">The
SCCC protocol stack diagram (figure 2-1) indicates the it covers
the CCSDS Sync and Channel Coding Sublayer and the Physical Layer:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_1_0F1081180F107D08002242C6C12586B0 style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">An
introductory paragraph that precedes this diagram states “The Synchronization
and Channel Coding Sublayer provides methods of</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">1)
QPSK (specified by cross reference to the appropriate definition
in CCSDS 401.0):</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">2)
8PSK</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">3)
16APSK</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">4)
32APSK</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">5)
64APSK</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">and
coding rates.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red"><b>>>>
Indeed 401.0-B ( </b></span><a href="https://urldefense.us/v3/__https:/public.ccsds.org/Pubs/401x0b31.pdf__;!!PvBDto6Hs4WbVuu7!efnnGUGob28wvg7EItHJSV1crsjHcx6eUUB7Tj84uTdExGvhIl9lcemPsL5rx4hl3oReM1oG$"><span style=" font-size:12pt;color:blue"><b><u>https://public.ccsds.org/Pubs/401x0b31.pdf</u></b></span></a><span style=" font-size:12pt;color:red"><b>
) 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.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red"><b>>>>
SCCC in NOT intended for use over 415.1 links. In fact, that book is not
mentioned in SCCC.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">Some
other observations:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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. </span><span style=" font-size:12pt;color:red"><b>>>>
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.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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. </span><span style=" font-size:12pt;color:red"><b>>>>
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. </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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.
</span><span style=" font-size:12pt;color:red"><b>>>> Andrea
Modeninini as book Editor is preparing the relevant draft and will take
of this editorial improvement.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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”. </span><span style=" font-size:12pt;color:red"><b>>>>
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.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">B.
CCSDS/DVB-S2 (CCSDS 131.3-B-1, March 2013)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_1_0F1727FC0F172590002242C6C12586B0 style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">[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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">NOTE
– ETSI standards are available for free download at </span><a href="https://urldefense.us/v3/__http:/www.etsi.org/__;!!PvBDto6Hs4WbVuu7!efnnGUGob28wvg7EItHJSV1crsjHcx6eUUB7Tj84uTdExGvhIl9lcemPsL5rx4hl3tw3DeUY$"><span style=" font-size:12pt;color:blue"><u>http://www.etsi.org</u></span></a><span style=" font-size:12pt">.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">-
DVB-S2: ETSI EN 302 307 V1.3.1 (2013-03),</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">-
DVB-S2, Part1, DVB-S2: ETSI EN 302 307-1 V1.4.1
(2014-11), and </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">-
DVB-S2, Part2, DVB-S2 Extensions: ETSI EN 302
307-2 V1.2.1 (2020-08). </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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.
</span><span style=" font-size:12pt;color:red"><b>>>> 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.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red"><b>>>>
Please consider the SCCC reply above for 401.0-B. </b></span><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">C.
VCM Protocol (CCSDS 431.1-B-1, February 2021)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">Figure
2-1 of the VCM Protocol Blue Book is:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_1_0F1778B80F17764C002242C6C12586B0 style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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. </span><span style=" font-size:12pt;color:red"><b>>>>
C&S WG may consider using a uniform term. Andrea & Ken may consider
thois point of discussion.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">Regarding
the VCM Protocol itself, the blue book specifies three sets of “modes”:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">-
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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">-
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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">-
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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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? </span><span style=" font-size:12pt;color:red"><b>>>>
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..</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red"><b>>>>
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.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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> </b></span><span style=" font-size:12pt;color:red"><b>>>>
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 .</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"><b> </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">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. </span><span style=" font-size:12pt;color:red"><b>>>>
Please consider the SCCC reply above for 401.0-B. </b></span><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">John</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Courier New">_______________________________________________<br>
SEA-SA mailing list<br>
SEA-SA@mailman.ccsds.org</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa__;!!PvBDto6Hs4WbVuu7!efnnGUGob28wvg7EItHJSV1crsjHcx6eUUB7Tj84uTdExGvhIl9lcemPsL5rx4hl3jFKy3BZ$"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (dpo@esa.int).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>