<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:Georgia;
        panose-1:2 4 5 2 5 4 5 2 3 3;}
@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:11.0pt;
        font-family:"Calibri",sans-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;}
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;}
/* List Definitions */
@list l0
        {mso-list-id:1323509413;
        mso-list-template-ids:-1818850174;}
@list l0:level1 lfo3
        {mso-level-start-at:2;}
@list l0:level1 lfo4
        {mso-level-start-at:3;}
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:14.0pt;font-family:"Georgia",serif;color:#1F497D">CSSM Colleagues,<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">As promised at today's CSSM teleconference, below please find the forwarded email with regard to the functional resource model review. If you can, I encourage you
 to take a look at the functional resource model prior to the fall virtual meetings – it will be helpful to understand the model when discussing automated XML schema generation with regard to configuration profiles. If you wish to participate in this review
 please note that the review is scheduled to conclude on October 19.<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"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> Holger.Dreihahn@esa.int <Holger.Dreihahn@esa.int>
<br>
<b>Sent:</b> Wednesday, August 26, 2020 03:05<br>
<b>To:</b> Gian.Paolo.Calzolari@esa.int; Gilles.Moury@cnes.fr; Enrico.Vassallo@esa.int; Lee, Dennis K (US 332G) <dennis.k.lee@jpl.nasa.gov>; Massimo.Bertinelli@esa.int; Andrews, Kenneth S (US 332B) <kenneth.s.andrews@jpl.nasa.gov>; Kazz, Greg J (US 312B) <greg.j.kazz@jpl.nasa.gov>;
 matt.cosby@goonhilly.org; Burleigh, Scott C (US 312B) <scott.c.burleigh@jpl.nasa.gov>; tomaso.decola@dlr.de; dstanton@keltik.co.uk; Mario.Merri@esa.int; brigitte.behal@cnes.fr; Berry, David S (US 3920) <david.s.berry@jpl.nasa.gov>; Frank.Dreger@esa.int; Shames,
 Peter M (US 312B) <peter.m.shames@jpl.nasa.gov>; jonathan.j.wilmot@nasa.gov<br>
<b>Cc:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov>; css-csts@mailman.ccsds.org; wo_._he <wo_._he@t-online.de><br>
<b>Subject:</b> [EXTERNAL] [CCSDS] Review of Functional Resource Model<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">Dear CCSDS Colleague,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This is a kind request to participate with your Working Group(s) in the review of the Functional Resource Model created by the CSS/CSTS WG. The review is based on a word document hosted on CWE, review
 instructions and further explanations can be found inside the document:</span> <br>
<a href="https://urldefense.us/v3/__https:/cwe.ccsds.org/css/docs/CSS-CSTS/SANA/functional_resources_css_tier_1.docx?Web=1__;!!PvBDto6Hs4WbVuu7!cHL54Z5cVHoOLhMSL6_cApqeBSkQnSvRfwEFXi9do4cw1v-TSBhJFJ1po7SV8DegSgLCZKQsbw$"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-CSTS/SANA/functional_resources_css_tier_1.docx?Web=1</span></a>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Optionally also the Functional Resource Reference Model Magenta Book, accompanying the Functional Resource review can be reviewed by including comments and changes in a copy:</span>
<br>
<a href="https://urldefense.us/v3/__https:/cwe.ccsds.org/css/docs/CSS-CSTS/SANA/FunctionalResourcesRefModel_MagentaBook-W-04-200717.docx?Web=1__;!!PvBDto6Hs4WbVuu7!cHL54Z5cVHoOLhMSL6_cApqeBSkQnSvRfwEFXi9do4cw1v-TSBhJFJ1po7SV8DegSgI8Yqz8ZA$"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-CSTS/SANA/FunctionalResourcesRefModel_MagentaBook-W-04-200717.docx?Web=1</span></a>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The end of the review is 19th October 2020.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Your review of the Functional Resources will help ensure that inter-agency cross support is properly stated in technical terms and will be much appreciated.</span>
<br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Background</span></b>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The Functional Resource Model (FRM) defines, in abstract terms, the functions that a ground station performs to provide Tracking, Telemetry and Command (TT&C) services to a spacecraft. The goal is
 to arrive at a standard representation of TT&C services, thereby facilitating standards for inter-agency cross support. The functions are organized around logical strata including Aperture, Physical Channel, Synchronization and Channel Coding, SLS Radiometric
 Data Production, Data Transfer Services, SLS Data Delivery and Production and others.  The functions are defined via configuration parameters, monitored parameters, notifiable events, and associated control directives.  
</span><br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Suggested review of Functional Resources (FR) per Working Group (WG)</span></b>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A.      <b>Space Link Services
</b></span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1.       <b>RF Modulation WG
</b></span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">a)     Aperture FR Stratum</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1)      RF Aperture FR Set/ Antenna FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">b)      Physical Channel FR Stratum</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1)      CCSDS 401 Physical Channel Transmission FR Set</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">i.                     CCSDS 401 Space Link Carrier Transmission FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ii.                   Ranging Transmission FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2)      CCSDS 401 Physical Channel Reception FR Set</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">i.                     CCSDS 401 Space Link Carrier Reception FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ii.                   Range and Doppler Extraction FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2.       <b>Space Link Coding & Synchronization WG
</b></span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">a)     Synchronization and Channel Coding FR stratum</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1)      TC Synchronization and Channel Encoding FR Set/ TC PLOP, Synchronization and Channel Encoding FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2)      Fixed Length Frame Synchronization, Channel Encoding, and OID Generation FR Set/ Fixed Length Frame Synchronization, Channel Encoding, and OID Generation FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3)       Fixed Length Frame Synchronization and Channel Decoding FR Set/ Fixed Length Frame Synchronization and Channel Decoding FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3.       <b>Space Link Protocols WG</b>
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">a)     Space Link Protocol FR stratum</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1)      TC Space Link Protocol Transmission FR Set</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">i.                     TC Master Channel (MC) Multiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ii.                   TC Virtual Channel (VC) Multiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2)      AOS Space Link Protocol Transmission FR Set</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">i.                     AOS MC Multiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ii.                   AOS VC Multiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3)      Fixed Length Frame Unified Space Data Link Protocol Transmission FR Set</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">i.                     FLF USLP MC Multiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ii.                   FLF USLP VC) Multiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">4)      TM/AOS Space Link Protocol Reception FR Set</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">i.                     TM/AOS MC Demultiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">ii.                   TM/AOS VC Demultiplexing FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">B.      <b>Space Internetworking Services Area
</b></span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#4F4F4F">1.    
</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">CCSDS File Delivery Protocol Revisions WG</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#4F4F4F">a)    
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">SLS Data Delivery Production FR Stratum/ CFDP File Data Production FR Set/ CFDP Entity FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">C.      <b>MOIMS Area
</b></span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1.<b>       Navigation WG
</b></span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">a)       SLS Radiometric Data Production FR Stratum/ Real-Time Radiometric Data Collection FR Set/ TDM Segment Generation FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">b)      Offline Data Storage FR stratrum/ TDM Recording Buffer FR Set/ TDM Recording Buffer FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">c)       Data Transfer Services FR Stratum/Tracking Data CSTS FR Set/ Tracking Data CSTS Provider FR</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">D.     <b>CSS Area</b></span>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">                </span>
</b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. CSTS WG</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">             a)                Frame Data Sink</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">b)                Offline Frame Buffer</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">c)                F-CLTU</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">d)                FF-CSTS</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">e)                RAF</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">f)                RCF</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">g)                ROCF</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">h)                MD-CSTS</span>
<br>
<br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Some final notes</span></b>
<o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Only the Master Channel and VC Mux functions of the TC, AOS, TM, and Unified SLPs are covered by this initial FR set. FRs representing the upper functions in these protocol stacks will be covered
 in a (near?) future set of FRs</span> <o:p></o:p></li></ol>
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For USLP, only the Fixed Length Frame (FLF) USLP Transmission FRs are covered in this initial set. FRs representing the Variable Length Frame (VLF) USLP Transmission, VLF USLP Reception, and FLF
 USLP Reception will be covered in a (near?) future set of FRs</span> <o:p></o:p></li></ol>
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">While we are asking specific WGs to primarily review the FR Sets and FRs that are most associated with the products of their WGs, we welcome comment on all contents of the candidate FR registry and
 the FR Reference Model White Book.</span><o:p></o:p></li></ol>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Thank you for reading to the end.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best Regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </span><a href="https://urldefense.us/v3/__http:/www.esa.int/esoc__;!!PvBDto6Hs4WbVuu7!cHL54Z5cVHoOLhMSL6_cApqeBSkQnSvRfwEFXi9do4cw1v-TSBhJFJ1po7SV8DegSgJ8ydF1rw$"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></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>