<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:"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:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{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:1078791800;
mso-list-type:hybrid;
mso-list-template-ids:1595593442 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{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;}
@list l1
{mso-list-id:1162549859;
mso-list-template-ids:-105339186;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sharing with you some good feedback from the radio developers at JPL concerning the Vulcan Wireless proposal (which will be talked about at our Spring 2023 CCSDS meeting) to modify the proximity directives beyond the use of Mars missions.
The most likely home for them might be the USLP blue book. TBD. For your comment and review.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Greg<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="color:black">Date: </span></b><span style="color:black">Tuesday, February 21, 2023 at 8:39 AM<br>
<b>To: </b>"Kazz, Greg (US 312B)" <greg.j.kazz@jpl.nasa.gov><br>
<b>Subject: </b>Re: [EXTERNAL] RE: Augmenting directives to Proximity-1 <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">I do see some benefit in both sides – the simplicity of a fixed format, and the flexibility of a variable format. Some ideas to consider:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">If people are willing to look up a table of ModCod values to interpret, why not also a table of frequency/symbol-rate values? Then you might only need
2 bytes for “FreqRate” instead of 10 bytes for Frequency and Symbol Rate<o:p></o:p></span></li><ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">Wouldn’t the Symbol Rate be determined from the Frequency and the ModCod? Does the Symbol Rate need to be specified explicitly?<o:p></o:p></span></li></ol>
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">Just one fixed format does not allow for future-proofing with backwards compatibility. Maybe a compromise would be the ability to select among a defined
set of fixed formats. So a SPDUType byte right after the Control Word. One defined SPDUType might be as Stuart diagrammed below, another defined SPDUType might be like Stuart’s except without “Time Stamp, RX Link SNR, RX Decode Percentage, and Range Estimate”,
for missions without those abilities, etc.<o:p></o:p></span></li><ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">This has the risk/benefit that missions might roll their own and ignore the standard. Maybe a defined range of SPDUType values would be allowed to be
“mission specific” (and maybe further distinguished by the Source ID to avoid type value collisions)?<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">Would want to avoid defining so many different SPDUTypes that only vary by one field that you effectively create a variable-length format. Make the SPDUTypes
“far enough apart” that they aim at different mission classes.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">Stuart’s idea of Query/Response could be used for radios to agree on a supported SPDUType if needed. Would perhaps be best if the Control and the SPDUType
are in the same location in every type of SPDU, so even if two radios do not support any SPDUType in common, they can still discover that sad fact. (This is why I suggested the SPDUType be after the Control Word instead of before.)<o:p></o:p></span></li></ol>
</ol>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></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="color:black">From: </span></b><span style="color:black">Stuart Golden <sgolden@vulcanwireless.com><br>
<b>Date: </b>Thursday, February 2, 2023 at 3:46 PM<br>
<b>To: </b>"Kazz, Greg (US 312B)" <greg.j.kazz@jpl.nasa.gov><br>
<b>Cc: </b>"Davarian, Faramaz (US 9700)" <faramaz.davarian@jpl.nasa.gov>, "Shihabi, Mazen M (US 337K)" <mshihabi@jpl.nasa.gov>, Kevin Lynaugh <klynaugh@vulcanwireless.com>, "ahmed.m.fadl@NASA.gov" <ahmed.m.fadl@nasa.gov><br>
<b>Subject: </b>[EXTERNAL] RE: Augmenting directives to Proximity-1 </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Greg,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I understand what you are proposing and what you are going for. But, I am thinking of it differently. I have different design principles than what was suggested. My suggestion would be to create USLP 2.0 that
would deprecate the current USLP and all of the current space layers: (USLP, Prox, AOS, TC, TM,….), and would “not” be legacy compatible with previous space layers.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">USLP 2.0 would work with all of the existing sync & coding layers & physical layer documents: Prox, TC, TM, DVBS2,…. That is USLP 2.0 is compatible with all sync and coding lower layers.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The cost of variable size transfer frame headers and backwards compatibility at the space layer adds complexity and is not efficient. Also as seen with SSTL they are deviating enough from the standard which
means they are not providing compatibility either.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">A simple new format would be very beneficial, and can be used for RF to Optical.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">USLP 2.0 would define the PLTU which consists of a fixed frame transfer header and SPDU. Rather than having a bunch of different SPDUs, I would propose a single “large” fixed size SPDU that is used for telemetry
and all control.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I would choose the PLTU that contains the SPDU to be “large” but small enough to fit into a reasonable codeword size and the PLTU would be locked into the codeword such that the SPDU would not be split into
multiple codewords. For our implementation, we are using a 512 Bytes( 4096 bit) information codeword. I think this codeword size is small for modern communications, DVBS2 is much larger. But for this PLTU with SPDU, I would pick it in even smaller than the
512 Bytes. I would propose something like 128 Bytes.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Here is an example of what I would think the PLTU would look like:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Stuart</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><img width="871" height="669" style="width:9.0729in;height:6.9687in" id="Picture_x0020_1" src="cid:image001.png@01D94CF0.1181C6C0"></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Kazz, Greg (US 312B) <greg.j.kazz@jpl.nasa.gov>
<br>
<b>Sent:</b> Wednesday, February 1, 2023 3:28 PM<br>
<b>To:</b> Stuart Golden <sgolden@vulcanwireless.com><br>
<b>Cc:</b> Davarian, Faramaz (US 9700) <faramaz.davarian@jpl.nasa.gov><br>
<b>Subject:</b> Augmenting directives to Proximity-1 </span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hi Stuart,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">A subset of the CCSDS Space Link Protocol WG meet recently to discuss how we would augment the directive set in Prox-1, keeping it backward compatible with Mars but adding the needed functionality for Lunar Ops. It was attended by reps
from ESA such as Brice Dellandrea and others who are aware of what is happening on the European side of the interface.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">So, please let me know if you have any comments regarding this proposed addition.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks much,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Greg Kazz</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Principal Engineer</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Technical Group Supervisor,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">312B Project Protection, Project Software, and End to End Information System Engineering</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Jet Propulsion Laboratory</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">4800 Oak Grove Dr., M/S 301-490</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt">Pasadena, CA 91109</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt">1+(818)393 6529(voice)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">1</span><span lang="ES-MX" style="font-size:11.0pt">+(818)393 6871(fax)</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt">email: <a href="mailto:greg.j.kazz@jpl.nasa.gov">
greg.j.kazz@jpl.nasa.gov</a> </span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>