[SLS-CC] [EXTERNAL] Re: VCM technical corrigendum wording (AI_21_01)
Andrea Modenini (external)
Andrea.Modenini at esa.int
Mon Jul 26 07:57:51 UTC 2021
Dear Peter,
sorry for the late reply, I have been hold by other activities, and I am
also in a personal leave.
Regarding the stack, in our opinion the VCM Blue Book defines also the
physical layer function, since it fully specifies the modulations and
constellations to be implemented.
In this respect, the RFM Blue Book 401 rather provides a set of
requirements to be fulfilled when transmitting at Radio Frequency, but not
a function.
Hence, our preference as WG is to insert the sentences as indicated in my
previous email, but to not modify the stack.
Please let us know your opinion, so that we could possible proceed with
the WG resolution.
Regards
HE Space Operations for ESA - European Space Agency
Ph.D. Andrea Modenini
Communication Systems & Technologies Engineer
TT&C and PDT Systems & Techniques Section (TEC-EST)
RF Systems Division
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
andrea.modenini at esa.int | www.esa.int
T +31 71 56 53439, M +31 6 484 56 527
From: "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov>
To: "Andrea Modenini (external)" <Andrea.Modenini at esa.int>, "Space
Link Coding & Synchronization Working Group" <sls-cc at mailman.ccsds.org>
Date: 07-07-21 21:05
Subject: Re: [EXTERNAL] Re: [SLS-CC] VCM technical corrigendum
wording (AI_21_01)
Dear Andrea & S&CC WG members,
I fully support the idea of aligning all three of the “VCM suite” coding
and synch standards. As we have tried to make clear in the updates we are
making to the SCCS-ARD, our analysis shows that all three of these
approaches are very nearly identical technically, with only what appear
to be modest differences in how they are designed. I do not wish to get
into the whole discussion of how we arrived at this situation, only to
point out that this is where we are, and that this is how we view the
technical details.
In the attached slides I have included, as pgs 2 & 3, the way that we are
approaching the description of what we are calling the “VCM Suite” and how
we plan to document these relative to the rest of the S&CC specs as well
as how they relate to the several link layer protocols. We reviewed these
diagrams during the “SCCS Coordination” meeting that involved SLS, SIS,
CSS, and SEA WG and Area leads. And we just discussed these during the
follow up SAWG meeting that Gilles was present at. We agreed to ask your
WG for feedback, so I am taking this opportunity to do this.
I have also included, on pg 1, a proposed markup of your text and Fig 2-1
from the 431.1 document. We think it will be clearer if this figure, and
the associated text, for the 431.1 (and the others in the VCM Suite) all
use the identical figure, and that this figure, and the related text,
clearly states that these standards only address the upper part
(modulation sub-layer) of the Physical Layer and not the lower sub-layer
where the 401.0 document addresses the RF frequency bands, bandwidth
limitations, etc.
Please review this feedback and see if you can agree to it. Also, it
would be very useful to us if your WG would review the VCM Suite diagrams
I have sent and make sure that they are technically correct.
Very best regards, Peter
From: SLS-CC <sls-cc-bounces at mailman.ccsds.org> on behalf of "Andrea
Modenini (external)" <Andrea.Modenini at esa.int>
Date: Wednesday, July 7, 2021 at 9:30 AM
To: Space Link Coding & Synchronization Working Group
<sls-cc at mailman.ccsds.org>
Subject: [EXTERNAL] Re: [SLS-CC] VCM technical corrigendum wording
(AI_21_01)
Dear all,
I did not receive any comment about the VCM BB from the WG.
However, considering the outcome of the DVB-S2 BB review we had today, I
have myself a comment.
We aligned the SCCC and DVB-S2 BBs for having a sentence that states the
need to consider CCSDS 401 BB.
On the same line, I would propose to modify Section 2 as provided below
(italic part highlights the addition).
You can find in attachment also the word file in tracking-changes mode for
your convenience.
Please let me know if there is any objection, or additional point to
consider, no later than 12th July EOB.
I will afterward request an Area Resolution for having the technical
corrigendum.
Kind Regards,
Andrea
-------------
This Recommended Standard covers functions in both the Synchronization and
Channel Coding Sublayer and the Physical Layer, the latter for what
concerns the modulation schemes. CCSDS 401.0-B [5] covers additional
features of the Physical Layer like frequency bands, polarizations, etc.
that are not described or referenced here.
HE Space Operations for ESA - European Space Agency
Ph.D. Andrea Modenini
Communication Systems & Technologies Engineer
TT&C and PDT Systems & Techniques Section (TEC-EST)
RF Systems Division
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
andrea.modenini at esa.int | www.esa.int
T +31 71 56 53439
From: Andrea Modenini/estec/ESA
To: "Space Link Coding & Synchronization Working Group"
<sls-cc at mailman.ccsds.org>
Date: 10-06-21 17:28
Subject: [SLS-CC] VCM technical corrigendum wording (AI_21_01)
Dear colleagues,
please find enclosed the proposed changes by Jon to the VCM BB discussed
during the joint C&S/RFM meeting. Please send your comments before 1st
July 2021 (if any) directly to John with CC Enrico and I, and C&S mailing
list.
Regards
Andrea
HE Space Operations for ESA - European Space Agency
Ph.D. Andrea Modenini
Communication Systems & Technologies Engineer
TT&C and PDT Systems & Techniques Section (TEC-EST)
RF Systems Division
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
andrea.modenini at esa.int | www.esa.int
T +31 71 56 53439
----- Forwarded by Andrea Modenini/estec/ESA on 10-06-21 17:25 -----
From: "Jon Hamkins" <Jon.Hamkins at jpl.caltech.edu>
To: "Andrea Modenini (external)" <Andrea.Modenini at esa.int>,
"Enrico.Vassallo at esa.int" <Enrico.Vassallo at esa.int>
Date: 09-06-21 18:48
Subject: VCM technical corrigendum wording (AI_21_01)
Andrea, Enrico,
Attached is a draft VCM technical corrigendum in response to AI_21_01 from
the C&S WG. I completed this in consultation with Ken Andrews and John
Pietras.
The main changes are in two places: Section 3.2.3 and Section 3.3.2.3 to
3.3.2.4. In summary, with the new wording the randomization is determined
by VCM type:
Type 1 (SCCC-like) VCM will randomize the Transfer Frames as the SCCC
standard does, using the TM randomizer.
Type 2 (DVB-S2-like) VCM will randomize the sliced encoder-inputs as the
DVB-S2 standard does, using the ETSI DVB-S2 baseband scrambler.
This will make the CCSDS VCM standard consistent with the 131.2-B-1 and
131.3-B-1 books (SCCC and DVB-S2), with respect to randomization.
These changes are not related to randomization that occurs after encoding.
The VCM protocol standard already applies post-encoding randomization, at
the physical layer.
Can you forward this message to the RFM and C&S mailing lists along with
your guidance on how/when to respond with comments? I believe we agreed to
resolve this action by email.
----Jon
--
Jon Hamkins
Chief Technologist, Communications, Tracking, and Radar Division
O 818-354-4764 (preferred) | M 626-658-6220 (does not work at home)
JPL | jpl.nasa.gov [attachment
"2021-05-27-VCM-431.1-technical-corrigendum-post-discussion-v3.doc"
deleted by Andrea Modenini/estec/ESA]
This message is intended only for the recipient(s) named above. It may
contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or
dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies
appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA
Data Protection Officer (dpo at esa.int).[attachment "2021-05-27 VCM 431.1
Fig 2-1.pptx" deleted by Andrea Modenini/estec/ESA]
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-cc/attachments/20210726/afc4c1e7/attachment-0001.htm>
More information about the SLS-CC
mailing list