<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)">
<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Georgia",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;}
--></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">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Hello Marcin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Here are some quick responses as to how I think this likely fits within the service management.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">I see the DOR tones as being part of the configuration profile.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">I see the DOR tones on/off times as part of the event sequence (which references the configuration profile). Also, from local conversation, it appears that name of
the raw observation files matters for processing by the correlators. That could also go in the configuration profile.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">I see the scan pattern as being part of the SMURF -- a question I have here is whether or not the scan pattern can be template-a-sized such that it is always referred
to by some sort of identifier. My sense from the DSN side is that this is not the case as the quasar(s) being utilized very depending upon the mission trajectory etc. I think it will be interesting to discuss further on this at the teleconference tomorrow
if you're available.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> SMWG <smwg-bounces@mailman.ccsds.org> <b>On Behalf Of
</b>Martin.Unal@esa.int<br>
<b>Sent:</b> Wednesday, May 27, 2020 01:26<br>
<b>To:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Cc:</b> CCSDS Service Mgmt WG <smwg@mailman.ccsds.org><br>
<b>Subject:</b> [EXTERNAL] Re: [cssm] Fw: DDOR configuration template<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hello<br>
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Here is a version 2 based on yesterday telecon discussion.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I have changed the configuration item names to</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy"> ddor_configuration</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">
and </span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">spacecraft_configuration</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy"><configuration_profile</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">service</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="deltaDor"</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><!-- DDOR configuration element defines which type of DDOR configurarion shall be used to configure the ground station --></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><!-- This can be used to select which type of tones to be used, how many DL band,...--></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><!-- The attribute and their value will probably be provider specific --></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy"><ddor_configuration</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">name</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="DDOR1"</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">/></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><!-- The spacecraft_configuration can be used to convey information relevant for the station configuration on a per DL basis (if needed)--></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><!-- To be open to future multi band DDOR, It is suggest to have an dlIndex--></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><!-- The attribute and their value will probably be provider specific --></span>
<br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy"><spacecraft_configuration</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">dlIndex</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="1"
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">band</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="Xband"
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">transmitter</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="1"</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">/></span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The main part to agree with the DDOR team concern the DDOR parameter. They are not really concerned by the configuration aspect. This is more an issue between the flight control team and the provider.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I am still not sure where you want to have it in a SMURF request.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Will it be in provider specific parameter ? In the configuration profile (902x05-Simple-conf-profile-Mission-Agrt) ?</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Regards<br>
________________________________________<br>
Martin UNAL<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 <br>
________________________________________</span><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>