[CESG] FW: [EXTERNAL] SCID V2 X-Band depletion

[Shames, Peter M (US 9740)]

Dear Ignacio, SLS WG chairs, and CESG,

The issue of us running out of AOS SCID namespace, particularly in the crowded X-Band, was forecast for a few years now.  We bought some time by “putting a bandage” on the problem and allocating SCIDs in frequency bins, but even that has now been over-run and the SANA is actually having to turn away SCID requests because the namespace is all used up.  See attached email.

I know you are aware of this.
I know that there are several different options that are in discussion, some much more feasible than others.

I wish to urge you to bring this matter to closure during this meeting.  This has already affected our users and that is not good for our reputation as a forward looking organization.

I do have some comments about the options.  Some of the proposed options involve augmenting the SANA registries by adding entirely new fields, such as using the coding, modulation, and other low level S/C comm characteristics.  I wish to argue strongly against this approach, for the following reasons:


  1.  This would require major re-engineering of all of the SCID & Spacecraft registries, which is a major impact on the SANA and a source of delay.
  2.  More importantly, we do not have this information at hand, it is not part of the usual SCID submissions, so gathering it will be time consuming and difficult (based on our prior experiences with requests for other added information).  This will be a large source of delay.
  3.  Even more importantly, these parameters are typically not fixed and singular for any given spacecraft.  Many spacecraft design in and use more than one modulation and coding, some have large tables of different combinations for different apertures.   As a consequence, this approach will just not work as a discriminator.

We know that there will be “knock-on” impacts from the proposal to use the spare bits in the AOS header.  It will require changes in the radios and in the ground systems.  But it will actually give us an approach that will be relatively easy to implement in the SANA and in our procedures.  More importantly, it will give us an approach that will work to discriminate clearly, at the link layer protocol, among different spacecraft.

With any of these options it does appear that operational coordination will still be required, especially at the crowded polar regions, but none of these solutions will have any impact on that.

We all know that the longer term solution for this is to get missions to adopt USLP.  And we must keep pushing in that direction for any number of different reasons.  But we must solve this issue now, and as quickly as possible.

Best regards, Peter


Peter Shames
Consultative Committee for Space Data Systems (CCSDS)
Systems Engineering Area Director
Jet Propulsion Laboratory / Interplanetary Network Directorate
4800 Oak Grove Drive
MS 301-490
Pasadena, CA 91109

peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>
C: 818-687-7901
https://cwe.ccsds.org/sea/default.aspx<https://urldefense.us/v3/__https:/cwe.ccsds.org/sea/default.aspx__;!!PvBDto6Hs4WbVuu7!fgncIVD-iu0I_1xWlmq78lUqf1aK_WZzB2gUhx7cfOlLefMQluIGVhXTKIrzYkYoUsYraXcV$>




From: Space Assigned Number Authority <info at sanaregistry.org>
Date: Thursday, October 24, 2024 at 5:57 AM
To: Shames, Peter M (US 9740) <peter.m.shames at jpl.nasa.gov>
Cc: info at sanaregistry.org <info at sanaregistry.org>, Lux, Jim (US 3370) <james.p.lux at jpl.nasa.gov>, Shannon Rodriguez <shannon.rodriguez-1 at nasa.gov>
Subject: [EXTERNAL] SCID V2 X-Band depletion
Dear Peter and all,
In the past few weeks we got many SCID requests, among which most
required X-Band V2.
Due to the SCID depletion, we are not able to allocate most of the new
requests. Do you think a solution will be found during the upcoming CCSDS?

--
Best regards,
Julien Bernard
Space Assigned Numbers Authority
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20241024/62ed7d9e/attachment-0001.htm>