<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=utf-8">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
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:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:2002928635;
mso-list-template-ids:1826243376;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Thanks Gippo. Last I knew it was not yet final.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-p<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Wednesday, March 3, 2021 at 12:35 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>SEA-SA <sea-sa@mailman.ccsds.org>, Gilles Moury <Gilles.Moury@cnes.fr>, "Enrico.Vassallo@esa.int" <Enrico.Vassallo@esa.int>, Dennis K Lee <dennis.k.lee@jpl.nasa.gov>, "Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int>, Kenneth Andrews <kenneth.s.andrews@jpl.nasa.gov><br>
<b>Subject: </b>[EXTERNAL] CCSDS 431.1-B-1 Variable Coded Modulation Protocol // was Re: [Sea-sa] Background materials for today's SEA-SA SCCS-ARD discussion<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> Only one remark about CCSDS 431.1-B-1 Variable Coded Modulation Protocol.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In is not correct that "</span>The new Variable Coding and Modulation (VCM) spec that is now in progress<span style="font-size:10.0pt;font-family:"Arial",sans-serif">"; i.e. it is not draft anymore..</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In fact this book has been approved for publication and it is available (with publication date February 2021) at </span><a href="https://urldefense.us/v3/__https:/public.ccsds.org/Pubs/431x0b1.pdf__;!!PvBDto6Hs4WbVuu7!epWZuEGHxM8wvvIR4amfB8trhMtc-pZS8Qv-KNgricyFVDINo0Bb4P9S-2UrAd4wZTd_F17f$"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://public.ccsds.org/Pubs/431x0b1.pdf</span></a>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Just to be sure everybody can read the most updated documentation.</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>
<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">"Shames, Peter M\(US 312B\) via SEA-SA" <sea-sa@mailman.ccsds.org></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">"SEA-SA" <sea-sa@mailman.ccsds.org></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">02-03-21 23:37</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] Background materials for today's SEA-SA SCCS-ARD discussion</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" <sea-sa-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" 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">Dear SCCS-ARD sub-team,<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">During today’s SEA-SA SCCS-ARD discussion we spent quite a period of time discussing the challenges in create a reasonably compact, and also accurate, table that reflects the currently documented set of configurations that are made available
by the suite of space data link, coding, synchronization, modulation, RF (and optical), and physical layer signaling standards. There are many situations where there is no one, simple, statement, or even set of statements, that can be made. We have had to
resort to a tabular presentation, Table 6-8 in Sec 6 on protocols, to address this. A copy of this table is attached, along with the “cheat sheet” of notes that encode the cells in this table.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Any standards that are expected to come into being within the next 6-12 months, but that are not yet final, are highlighted in yellow. We hope these are final before we publish this document, but all of those dates are still rather uncertain.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Note that uplink is separate from downlink, that RF coding and modulation is separate from optical coding and modulation, and that SCCC and DVB-S2 (which both contain coding, modulation, and physical layer signaling in a single standard)
are separated from the “normal” CCSDS standards that break these into three separate layers. The new Variable Coding and Modulation (VCM) spec that is now in progress is also shown as a separate layer. This VCM spec is related to the “bottom” parts of the
DVB and SCCC specs, but it is different from them in distinct ways. <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">It became clear during discussion that most of those on the call were unfamiliar with the details and complexities represented in this table. Furthermore, most are unfamiliar with the complexities inherent in the “3-layer sandwich” that
SCCC and DVB present, and with how they compare with the “normal” CCSDS link layer, coding, synch, modulation, physical layer and RF stack. I have attached a presentation that some of us constructed in order to make sure that we understood what those relationships
are. It is named “SEA high rate comm issue 1Mar21” and is attached here. This is a statement of the recent issues and also a set of diagrams comparing these different protocol sets. It does not address optical comm.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">It should be noted that the “bottom” part of the DVB and SCCC specs includes a specialized set of physical layer signaling mechanisms. These are not present in normal CCSDS protocol stacks, where any choices that are made for different
coding, synchronization, and modulation combinations are made “by management”. That phrase “by management” means that the mission manages these choices manually, outside of the protocols themselves, that the protocol layers contain no “signals” as to which
choices were made, and that any changes to the coding and modulation must be agreed to and managed out of band, by pre-agreement. <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">In the DVB and SCCC, and in the new draft CCSDS VCM spec (CCSDS 431.1-b-1) which is attached here as a CESG draft spec, a physical layer signaling mechanism is introduced. VCM is defined as “<b>variable coded modulation, VCM</b>: A method
to adapt the transmission scheme to channel conditions following a predetermined schedule. ”. This includes two separate physical layer structures: 1) the “Pilot Symbols” and 2) the encoded and modulated data symbols. The CCSDS 431.1 spec describes two
different VCM “types”. Type 1 uses the DVB-S2 VCM pilot symbol and data symbol length approach, Type 2 uses the SCCC VCM pilot symbol and data symbol length approach. These pilot symbols are, in both cases, just short blocks of 7 bits, protected by a linear
code and BPSK modulation (see attached Table from Annex E). Five of these bits are used to identify one of the 32 possible sets of code and modulation pairs that are applied to the encoded and modulated symbols that follow the pilot. <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Where these DVB Type 1, SCCC Type 2, and CCSDS Type 1 or 2 schemes differ is in the length of the symbol strings and the sets of code/modulation pairs that are allowed. <o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
DVB-S2 has its own set shown in Table 3-4. It allows different code rates, from 1 / 4 (0.25) up to 9 / 10 (0.9), different input lengths from 2992 up to 58112 bits, different modulations (QPSK, 8-PSK, 16 & 32-APSK) and its own set of DVB-S2 codes that are
patented. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
SCCC has its own set shown in Table 3-3. It allows different code rates, from 0.36 up to 0.9, different input lengths from 5758 up to 43678 bits, the same set of modulations (QPSK, 8-PSK, 16 & 32-APSK) and its own set of SCCC codes that are patented.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The CCSDS VCM has its own set shown in Table 3-2. It allows different (CCSDS standard) code rates, from 1 / 6 (0.16) up to 223/255 (0.875), different (CCSDS standard) input lengths from 1748 up to 16384 bits, the same set of modulations plus BPSK (BPSK, QPSK,
8-PSK, 16 & 32-APSK) and the standard LDPC codes. <o:p></o:p></li></ul>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal">You can see that these are similar, and that the modulation set largely overlaps, but they are different. In all cases specialized equipment will be needed in the RF front ends to handle the pilot symbols and the continually changing coding
and modulation . The other difference is that the CCSDS VCM expects to signal a pre-planned set of code & modulation changes, but the SCCC and DVB-S2 also include adaptive coding and modulation (ACM), which uses signals sent back from the receiver to the
sender. To quote from SCCC, CCSDS 131x2b1d1, Sec 3.2.7: <o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#424282">NOTE –
</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#424282">Changes of the value of the information block size
</span><i><span style="font-size:12.0pt;color:#424282">K </span></i><span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#424282">are done by a system to adjust the modulation and coding schemes. This is achieved through, e.g., one of the
following approaches: the ground receiver provides the signal quality estimation (or prediction) through a feedback channel (e.g., via telecommand) or the change of modulation and coding schemes is pre-scheduled for each satellite pass based on geometrical
information (elevation angle). </span><o:p></o:p></p>
<p style="margin:0in">So the SCCC may use a feedback loop, but no specific protocol appears to be specified for this. The DVB-S2 standard, as adapted for CCSDS, makes essentially the same statement. The full ETSI DVB-S2 spec, however, defines an actual feedback
protocol that is, in my opinion, only of use over a near Earth (or at least a “local”) communications path where the RTLT is sufficiently short to allow requests for data rate changes to be responded to. This is not appropriate for use in deep space where
the RTLT may be measures in 10’s of minutes or tens of hours. They also bring substantial added complexity which, in the general case, may not be worth the added cost of engineering, testing, etc unless the mission is a) in a near Earth orbit, and b) can
make use of available commercial parts.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">As I suggested during the webex, I think we must treat the following groups of standards separately, because to do otherwise will overly complicate the core of the CCSDS standard suite, that I estimate meets 95% of the users.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span>The “CCSDS standard” suite of link layer, coding, synchronization, modulation, and RF standards<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span>A subsection on the Optical coding and modulation standards that slot in underneath the normal link layer protocols, along with a brief description<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span>A separate subsection on the VCM and the associated SCCC and DVB-S2 “omnibus” standards that replace the standard CCSDS coding, synchronization, modulation
and add physical layer signaling.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">If anyone has issues with this approach please bring them up now. I think this is the only sensible way to handle this issue of these very different approaches to the lower layer protocols.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Thanks, Peter<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> [attachment "SEA High Rate comm issue 1Mar21.pptx" deleted by Gian Paolo Calzolari/esoc/ESA] [attachment "431x1b0_CESG_Approval.pdf" deleted by Gian Paolo Calzolari/esoc/ESA] [attachment "CCSDS 431 VCM protocol layers.pdf" deleted by
Gian Paolo Calzolari/esoc/ESA] [attachment "CCSDS 431 VCM pilot pattern.pdf" deleted by Gian Paolo Calzolari/esoc/ESA] [attachment "CCSDS 431 DVB SCCC pilot approaches.pdf" deleted by Gian Paolo Calzolari/esoc/ESA] [attachment "SCCS-ARD Table 6-8 Notes 1Mar21.pdf"
deleted by Gian Paolo Calzolari/esoc/ESA] [attachment "SCCS-ARD Table 6-8 proto layer options.pdf" deleted by Gian Paolo Calzolari/esoc/ESA]
<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>SEA-SA@mailman.ccsds.org</tt><br>
</span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa__;!!PvBDto6Hs4WbVuu7!epWZuEGHxM8wvvIR4amfB8trhMtc-pZS8Qv-KNgricyFVDINo0Bb4P9S-2UrAd4wZX5KG67A$"><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 (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>