[Sls-slp] OID Frames with mandatory PN sequence: Unfinished Business

Kazz, Greg J (US 312B) greg.j.kazz at jpl.nasa.gov
Tue Jan 26 17:56:28 UTC 2021


Dear SLP WG members,

Happy New Year ! We all hope it will be a better one than the last one.

I’ve now updated all the affected SDLP’s (TM, AOS, USLP) with the agreed to mandatory PN sequence generator to be used in generating the random data pattern within the transfer frame data field of OID frames.
Luckily the changes has not impacted these books very much and is rather easily accommodated.
Please go to the following URL on the CWE that contain the 3 new files (each one containing the final prefix _gk):
https://tinyurl.com/yxn7gecs

This change affects the following sections in these SDLP books:
Section 4.1.4.6 which is now split into separate requirements to accommodate the mandatory PN sequence generator.
The note directly below associated with the project providing the idle pattern, has now been changed to provide the motivation for the random PN sequence.
Finally, in each book, the acronym, LFSR (Linear Feedback Shift Register) has been added to the Acronym Annex in the back.

I have included the power point presentations supplied by Massimo Bertinelli as a reminder of the changes proposed by RF&M and C&S WGs back in Dec 2019, which SLP WG concurred upon. We are simply catching up on that action now.

So given the short fuse associated with providing these documents for Agency Review, I request you review these changes and provide me with your feedback by Thursday, Jan 28.

Best regards,
Greg Kazz – Chair SLP WG

From: "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>
Date: Tuesday, January 26, 2021 at 7:41 AM
To: "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Cc: "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>, "Gilles.Moury at cnes.fr" <Gilles.Moury at cnes.fr>, Matthew Cosby <matt.cosby at goonhilly.org>
Subject: Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP

Hi Greg,

the 32-cell LFSR agreed upon was presented in the document attached (slide 12-13).
In the document the initialisation of the register was an open question (3 options given).
In the end, one option was chosen as outlined in the C&S-SPL  liaison presentation attached.
I hope this can help.
Please let me know in case you need more information.

Best regards,
Massimo





---------------------------------------------------
Massimo Bertinelli
Communication Systems Engineer
ESA/Estec

Tel. +31 (0)71 5653435
--------------------------------------------------



From:        "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
To:        "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>, "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>
Cc:        "Gilles.Moury at cnes.fr" <Gilles.Moury at cnes.fr>, "Matthew Cosby" <matt.cosby at goonhilly.org>
Date:        25/01/2021 22:56
Subject:        Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP
________________________________


OK. So it sounds like I need to add the same requirement into 3 SDLP books (TM, AOS, USLP)…something to the effect that the frame data field contents of OID transfer frames shall be generated by the use of the mandatory PN sequence by means of the 32-cell LFSR.



Question – Can someone send me the specification (and the viewgraph presentation) for this PN sequence generator (32-cell LFSR), so that I can reference it in those documents?



Thanks!

Greg



From: "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>
Date: Monday, January 25, 2021 at 12:58 PM
To: "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>
Cc: "Gilles.Moury at cnes.fr" <Gilles.Moury at cnes.fr>, "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>, Matthew Cosby <matt.cosby at goonhilly.org>
Subject: Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP



no change foreseen or needed in the coding book...we'll eventually introduce a longer randomiser, but the OID pattern is indipendent.
The C&S books simply refer to the protocol books for the pattern


---------------------------------------------------
Massimo Bertinelli
Communication Systems Engineer
ESA/Estec

Tel. +31 (0)71 5653435
--------------------------------------------------



From:        Gian Paolo Calzolari/esoc/ESA
To:        "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Cc:        "Matthew Cosby" <matt.cosby at goonhilly.org>, Massimo Bertinelli/estec/ESA at ESA, Gilles.Moury at cnes.fr
Date:        25/01/2021 17:34
Subject:        Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP

________________________________



Greg,
I am not sure there will be any pink sheets to coding book.
Up to Massimo to confirm.
Ciao

Gian Paolo

Sent from my iPhone

On 25. Jan 2021, at 17:19, Kazz, Greg J (US 312B) <greg.j.kazz at jpl.nasa.gov> wrote:

Gian Paolo,



This new requirement on making the use of the PN sequence mandatory for OID frames is not in any of the SDLP books yet.

If you can email me the relevant pink sheets to the coding books regarding this new requirement, then I can generate the additional pink sheet changes to TM, AOS, and USLP SDLPs. Thereafter I will need to send them out to the SLP WG for a quick review.



Regards,

Greg



From: "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>
Date: Monday, January 25, 2021 at 7:39 AM
To: "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Cc: Matthew Cosby <Matt.Cosby at Goonhilly.org>, "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>, "Gilles.Moury at cnes.fr" <Gilles.Moury at cnes.fr>
Subject: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP



Greg,
      is this already in any of the Space Data Link Protocols books?
If not & needed, any chance to update the books before starting the CESG/CMC Polls for Agency Review?

Thanks

Gian Paolo



From:        Massimo Bertinelli/estec/ESA
To:        "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Cc:        "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>, "Matthew Cosby" <Matt.Cosby at Goonhilly.org>
Date:        23-01-21 21:58
Subject:        Re: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP

________________________________


That's good news, thank you.
Sorry for losing track on this point, I should have kept better notes.

Best regards,
Massimo


---------------------------------------------------
Massimo Bertinelli
Communication Systems Engineer
ESA/Estec

Tel. +31 (0)71 5653435
--------------------------------------------------




From:        "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
To:        "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>
Cc:        "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>, "Matthew Cosby" <Matt.Cosby at Goonhilly.org>
Date:        23/01/2021 18:48
Subject:        FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP

________________________________



Hi Massimo,



If I recall correctly at the joint meeting in Dec. 2019, SLP WG concurred with you back in May 2019 on the use of the mandatory PN sequence by means of the 32-cell LFSR as you stated in your last email to me. The remaining undecided party at that time was NASA/GSFC, which later also agreed documented below in your email from Dec. 6. So as far as I can tell, the issue is resolved and can go now to agency review.



Best regards,

Greg



From: SLS-SLP <sls-slp-bounces at mailman.ccsds.org> on behalf of "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>
Date: Friday, December 6, 2019 at 12:16 AM
To: "Enrico.Vassallo at esa.int" <Enrico.Vassallo at esa.int>, "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>, Space Link Coding & Synchronization Working Group <sls-cc at mailman.ccsds.org>, "sls-slp at mailman.ccsds.org" <sls-slp at mailman.ccsds.org>
Subject: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP



This message has been archived.  View the original item <https://evserver1.jpl.nasa.gov/EnterpriseVault/ViewMessage.asp?VaultId=10036FD0C335539419F44551B26993E651110000evserver1&SavesetId=202006293430735~201912060816280000~Z~710AAF1FD87EBB11F6181E489D6055F1>

A brief update:

OID - the action on NASA/GSFC is closed. V. Sank confirmed the feasibility and the agreement (making the random pattern OID mandatory) is confirmed

USLP - the second action refers specifically to the concerns raised by Wolfgang Hell about "systematic retransmission" in section 4.2.10.8 of USLP with respect to 231.0
I'm sorry that my formulation in yesterday's notes was not clear.

Best regards,
Massimo

---------------------------------------------------
Massimo Bertinelli
Communication Systems Engineer
ESA/Estec

Tel. +31 (0)71 5653435
--------------------------------------------------



From:        Massimo.Bertinelli at esa.int
To:        brent.r.andres at nasa.gov, Enrico.Vassallo at esa.int, Gian.Paolo.Calzolari at esa.int, sls-cc at mailman.ccsds.org, sls-slp at mailman.ccsds.org
Date:        05/12/2019 18:33
Subject:        [SLS-CC] Joint C&S/SLP
Sent by:        "SLS-CC" <sls-cc-bounces at mailman.ccsds.org>
________________________________



Dear all,

a very brief summary of our discussion:

- OID
Most of the participants agreed to make the proposal (OID random pattern) mandatory.
Participants from NASA/GSFC asked for more time to confirm (or not) the decision
The proposal, once agreed, will be anyway subject to Agency Review
AI (V. Sank): report NASA/GSFC position by end of December 12

- TERMINOLOGY
G. Kazz/NASA presented a proposal to align the terminology (regarding re-transmission) of the protocol books (232.1-B-2 and 232.0-B-3) to that used in the coding
book (231.0-B)
G. P. Calzolari/AD stated that the change of terminology was not actually required, and proper referencing inside the protocol books would achieve the target.
This will translate in actions internal to the SLP WG and the issue, from the joint C&S/SLP point of view, is closed

- USLP
G. Kazz/NASA presented the (limited) changes required in 231.0-B (TC coding book) in order to reference 732.1 (USLP), stating how USLP already foresees this service
It was agreed background underlying the actual need for this change (possibly linked to Lunar missions) will be provide.
Besides, it was agreed to provide material (presentation/paper...) to show how the use of USLP would not be detrimental
to the TC service
AI (G. Kazz): provide rationale for the change
AI (G. Kazz): provide material about use of USLP with TC, showing compatibility


---------------------------------------------------
Massimo Bertinelli
Communication Systems Engineer
ESA/Estec

Tel. +31 (0)71 5653435
--------------------------------------------------

__________________



Dear all,

based on the results of the poll, we are going to have a first joint C&S/SLP discussion on the following topics on Thursday 5 December, starting at 4pm (CET).

- introduction of OID random pattern
- possible alignment of terminology in the TC books regarding retransmission
- additionally, SLP would like to discuss adding USLP to the TC coding book and assessing its impact (other books are mentioned in the presentation, but agreement on these ones has already been reached)



-- Do not delete or change any of the following text. --

Join Skype for Business Online Meeting

https://meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC<https://urldefense.us/v3/__https:/meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0lMQA4kh$>

Join by phone
Toll Number: +31202588798
Conference ID: 684255790

Forgot your Dial-In PIN:
https://mysettings.lync.com/pstnconferencing<https://urldefense.us/v3/__https:/mysettings.lync.com/pstnconferencing__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0s-GEkYO$>

Global call-in numbers
https://dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3<https://urldefense.us/v3/__https:/dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0pRdGn4H$>

or download:
https://esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf<https://urldefense.us/v3/__https:/esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0opSsdOO$>
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).

_______________________________________________
SLS-CC mailing list
SLS-CC at mailman.ccsds.org
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc<https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0l9pUSOc$>



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).

Attachments:





ATT00001.txt <https://evserver1.jpl.nasa.gov/EnterpriseVault/ViewMessage.asp?VaultId=10036FD0C335539419F44551B26993E651110000evserver1&SavesetId=202006293430735~201912060816280000~Z~710AAF1FD87EBB11F6181E489D6055F1&AttachmentId=1>

(0 KB)










 [attachment "@" deleted by Massimo Bertinelli/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).

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).

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-slp/attachments/20210126/7b405aae/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SLS_RFM_19_21_new2.pptx
Type: application/octet-stream
Size: 4699098 bytes
Desc: SLS_RFM_19_21_new2.pptx
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20210126/7b405aae/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CS liaison to SLP_Post_Darmstadt_2019_gk.pptx
Type: application/octet-stream
Size: 469599 bytes
Desc: CS liaison to SLP_Post_Darmstadt_2019_gk.pptx
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20210126/7b405aae/attachment-0003.obj>


More information about the SLS-SLP mailing list