<font size=2 face="sans-serif">Dear ALL,</font>
<br><font size=2 face="sans-serif"> Here
following SLS comments to slides.</font>
<br>
<br><font size=2 face="sans-serif"><b>Page 2 BACKGROUND</b></font>
<br><font size=2 face="sans-serif"><u>Bullet 1</u>: the question is about
what are the allowed coding schemes and modulation.</font>
<br><font size=2 face="sans-serif"><u>Bullet 2</u>: There not a <perceived
gap>, there is a gap. There are no CCSDS Standards available for uplink
of AOS Frames. As far as SLS know, as of today the uplink of AOS Frames
is limited to ISS (via TDRSS) and here are no interoperability requirements
for ISS. </font>
<br><font size=2 face="sans-serif">The coding schemes used for uplink to
ISS are Convolutional, Reed-Solomon and their concatenation. Those schemes
are defined in 131.0-B but there is no CCSDS standard allowing their usage
for uplink. </font>
<br><font size=2 face="sans-serif">The modulation used for uplink to ISS
(via TDRS) are defined in the so called <SNIP Agreement> that is
only partially part of the 401.0-B standard from RFM WG. Of course the
modulations are not aware of the kind of frames transmitted.</font>
<br><font size=2 face="sans-serif"><u>CSS AD Notes bullet 1</u>; No discussion
that AOS was designed to be multi purpose, however the standardisation
available is limited to space-to-ground.</font>
<br><font size=2 face="sans-serif"><u>CSS AD Notes bullet 2</u>; Please
refer to 732.0-B-3 at </font><a href=https://public.ccsds.org/Pubs/732x0b3.pdf><font size=2 face="sans-serif">https://public.ccsds.org/Pubs/732x0b3.pdf</font></a>
<br><font size=2 face="sans-serif">Section 1.7 REFERENCES ittems
[3], [4] e [5] are:</font>
<br><font size=2 color=blue face="sans-serif">[3] TM Synchronization
and Channel Coding . Issue 2. Recommendation
for Space Data System Standards (Blue Book), CCSDS
131.0-B-2. Washington, D.C.: CCSDS, August 2011. </font>
<br><font size=2 color=blue face="sans-serif">[4] Flexible
Advanced Coding and Modulation Scheme
for High Rate Telemetry Applications. Issue
1. Recommendation for Space Data System Standards (Blue Book), CCSDS 131.2-B-1.
Washington, D.C.: CCSDS, March 2012. </font>
<br><font size=2 color=blue face="sans-serif">[5] CCSDS Space
Link Protocols over ETSI DVB-S2 Standard
. Issue 1. Recommendation for Space Data System Standards (Blue Book),
CCSDS 131.3-B-1. Washington, D.C.: CCSDS, March 2013. </font>
<br><font size=2 face="sans-serif">Section 2.1.1 states : </font><font size=2 color=blue face="sans-serif">For
the Synchronization and Channel Coding Sublayer,the set of TM Synchronization
and ChannelCoding Recommended Standards (references [3], [4], and [5])
must be used with the AOS Space Data Link Protocol</font><font size=2 face="sans-serif">.</font>
<br><font size=2 face="sans-serif">Section 2.4.1 states: </font><font size=2 color=blue face="sans-serif">
As described in 2.1.1, the set of TM Channel Coding and Synchronization
Recommended Standards (references [3], [4], and [5]) must be used with
the AOS Space Data Link Protocol as the TM Synchronization and Channel
Coding Sublayer specification</font><font size=2 face="sans-serif">. </font>
<br><font size=2 face="sans-serif">Those 3 standards are for transmission
space-to-ground.</font>
<br>
<br><font size=2 face="sans-serif"><b>Page 3: CONTEXT DIAGRAM</b></font>
<br><font size=2 face="Arial">The technical diagram is very and probably
correct (I did not check it carefully).</font>
<br><font size=2 face="Arial">However I doubt this slide is relevant for
CMC as they should be made aware of the problem while the diagram addresses
how CSSS Area want to develop a standard after ALL the relevant (available,
in progress, future) SLS Standards will be available.</font>
<br><font size=2 face="Arial">USLP Standard is in progress and with the
current formulation will be possible for USLP Frames to access the chain
for TC Coding. </font>
<br>
<br><font size=2 face="Arial">Other remark: who decides which subset of
coding schemes (see books </font><font size=2 face="sans-serif"> [3],
[4] e [5] </font><font size=2 face="Arial">in AOS Standard) are to be implemented
and which not?</font>
<br><font size=2 face="Arial">Tis is something C&S WG shall do (if
any Agency will propose to look into this issue).</font>
<br>
<br><font size=2 face="Arial"><b>Page 4 ANALYSIS</b></font>
<br><font size=2 face="Arial">Red path is not according to CCSDS Rules
and pertinent to SLS and not to CSS.</font>
<br><font size=2 face="Arial">Definition of new SLS Standards by modification
of CSS Book is simply not acceptable.</font>
<br>
<br><font size=2 face="Arial">The flow diagram misses the start point that
is the proposal from one or more CCSDS Agencies to add relevant standards
according to their user needs.</font>
<br><font size=2 face="sans-serif">Again, the point is that there is an
absence of specification and therefore the Agency/Agencies requesting such
capability in CCSDS shall identify the desired profiles for Coding and
Modulation and propose relevant work for the the experts in the C&S
and RFM WGs. Only after those standard (or Recommended Practices) are made
available it will be possible to modify the AOS Standard (most likely limited
to section 2.1.1 and 2.4).</font>
<br>
<br><font size=2 face="Arial"><b>Page 5 PRELIMINARY CONCLUSIONS</b></font>
<br><font size=2 face="sans-serif">As mentioned, 732.0-B can only be modified
after the relevant standard (or Recommended Practices) are available.</font>
<br><font size=2 face="sans-serif">No Space Data Link Protocols defines
the standards for Coding and/or modulation. </font>
<br>
<br>
<br><font size=2 face="sans-serif"><b>SLS Recommandations</b></font>
<ul>
<li><font size=2 face="sans-serif">Define what the problem is; i.e. it
looks there are no C&S and RFM standards to support uplink of AOS Frames</font>
<li><font size=2 face="sans-serif">Invite concerned agencies to identify
the C&S and RFM profiles they require to support uplink
of AOS Frames.</font>
<li><font size=2 face="sans-serif">Once such profiles are identified, it
can be verified what is missing and relevant Standards or Practices can
be defined by C&S and RFM if consensus and resources available</font></ul>
<br><font size=2 face="sans-serif">Note that, while it is sure that TM
Coding Books are not applicable to uplink, it may be that existing uplink
modulations already satisfy user needs.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Best regards</font>
<br>
<br>
<br><font size=2 face="sans-serif">Gian Paolo & Gilles</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Barkley, Erik
J (3970)" <erik.j.barkley@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"CESG -- CCSDS-Engineering
Steering Group (cesg@mailman.ccsds.org) (cesg@mailman.ccsds.org)"
<cesg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">30/05/2017 22:56</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[CESG] Response
to AI from CESG meeting re FF-CSTS and AOS uplink</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">CESG Colleagues,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Attached please find a preliminary analysis
re way forward for FF-CSTS and AOS uplink issue that was raised during
the San Antonio CESG meeting. Your inputs will be appreciated.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Best regards,</font>
<br><font size=2 face="Calibri">-Erik[attachment "d0-FF-CSTS-and-AOS-Uplink-30-May-2017.pdf"
deleted by Gian Paolo Calzolari/esoc/ESA] </font><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>