<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;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">Colin et al, here is a description of scheduling windows (TSWs) as used in the Space Network today, which may help in understanding the use case.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is text in the SNUG that describes how users can either use the start times in their requests, or TSWs to make sure their services are scheduled within timeslots that make sense:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864;mso-style-textfill-fill-color:#203864;mso-style-textfill-fill-alpha:100.0%">A MOCC is responsible for ensuring its own customer platform-to-TDRS visibility prior to adding a schedule event.
The MOCC may do this directly by submitting schedule requests with start time tolerances that comply with customer platform-to-TDRS visibility requirements or indirectly by submitting TDRSS Scheduling Windows (TSWs) to the NCCDS and then submitting schedule
requests that specify that they are to fit within these TSWs. Use of TSWs makes it feasible to submit schedule requests that specify TDRS flexibility and with start time tolerances that exceed a single TDRS view.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The further description of how TSWs relate to the scheduling process is:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864;mso-style-textfill-fill-color:#203864;mso-style-textfill-fill-alpha:100.0%">Each TSW message contains TSWs applicable to a specified time period for a single customer-defined TSW set for
a single TDRS. The TSWs may be transmitted before, after, or at the same time as the schedule requests that depend on the TSWs. However, if a schedule request requires TSWs from a particular TSW set for a particular TDRS during a certain time period, it cannot
be processed if applicable TSWs have not been received.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864;mso-style-textfill-fill-color:#203864;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864;mso-style-textfill-fill-color:#203864;mso-style-textfill-fill-alpha:100.0%">Each TSW set contains the TSWs applicable to a particular combination of customer visibility constraints based
on factors such as antenna type, power, and frequency. Each customer may define as many TSW sets as needed, and may define new TSW sets at any time without negotiation with the NCCDS.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864;mso-style-textfill-fill-color:#203864;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864;mso-style-textfill-fill-color:#203864;mso-style-textfill-fill-alpha:100.0%">Each SSC
</span><i>(an “SSC” in the SN is equivalent to a configuration profile for us)</i>
<span style="color:#203864;mso-style-textfill-fill-color:#203864;mso-style-textfill-fill-alpha:100.0%">
either specifies the TSW set applicable to the scheduling of the service specified by that SSC, or specifies that TSWs are not applicable. A TSW set is a re-specifiable parameter.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If it is useful, I can provide a description of the fields in a TSW, but the short story relevant to Colin’s question about included/excluded times is that a TSW set consists of the included windows, and there is not a notion of excluded
windows. If not in the included windows, then a time is understood to be excluded.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>