[Sls-slp] Call for Use Cases of Space Packet Protocol

[Shames, Peter M (312B)]

Folks,

What we have proposed in the SPP revision is to create a SANA registry for local, agency, or even multi-agency packet secondary headers.  This could include PUS, MAL packet mapping, Jonathan's LOP-G headers, and others.  There is a proposal for a simple registry structure in the draft SPP doc that would allow all of these to be registered.  I suggest that you look at this and propose any needed metadata for the registry.  You could try and engage in some sort of "normalization" effort for the field names, structures, and contents, or at least try and do some sort of evaluation of the kinds of data and the different ways they are named and represented.  I'll bet you will find that they are all over the map.

By the way, the SOIS Dictionary of Terms (DoT) may prove to be useful as a source of standardized terms.

Lastly, as I recall the Constellation DEM did not adhere to the SPP at all.  I may be mis-remembering.

Cheers, Peter


From: SLS-SLP <sls-slp-bounces at mailman.ccsds.org> on behalf of Jonathan Wilmot via SLS-SLP <sls-slp at mailman.ccsds.org>
Reply-To: "Wilmot, Jonathan J. (GSFC-5820)" <Jonathan.J.Wilmot at NASA.gov>
Date: Thursday, February 28, 2019 at 7:03 AM
To: Scott Burleigh <Scott.C.Burleigh at jpl.nasa.gov>, "Greenberg, Edward" <Edward.Greenberg at jpl.nasa.gov>, "sls-slp at mailman.ccsds.org" <sls-slp at mailman.ccsds.org>
Cc: Peter Shames <Peter.M.Shames at jpl.nasa.gov>, Lee Pitts <robert.l.pitts at nasa.gov>
Subject: Re: [Sls-slp] Call for Use Cases of Space Packet Protocol

Ed, Scott,

   The CCSDS Space Packet is being used at NASA, ESA and CAST as end user application command and telemetry message. It contains information in the primary and secondary headers to allow end user applications to identify the data content and format, and also allow mission architecture specific lower layers to transport user application data within a subnetworks or across networks.

   As part of this discussion I would like to re-submit a proposal to create a secondary header that could be included as an optional header in the SPP Blue book or registered in SANA as a standard SPP secondary header type. (ECSS-PUS headers should also be registered)

Note:  The LOP-G program,  and other missions at  JSC, GSFC, and ARC,  are  currently using the format in the attached proposal.  This is an opportunity for CCSDS to  improve mission interoperability by supporting the SPP uses cases that missions require.

  Kind Regards,

      Jonathan

Jonathan Wilmot
NASA/GSFC
CCSDS SOIS Area Director

On 4/22/2018 12:16 PM, Burleigh, Scott C (312B) wrote:
Ed, I think of the Space Packet as being the thing that the old Constellation project called a Data Exchange Message (DEM).  I think it performs the same function in the stack, and I suspect that it could easily carry all the same metadata that the DEM was supposed to carry.

Scott

From: Greenberg, Edward (312B)
Sent: Sunday, April 22, 2018 7:37 AM
To: sls-slp at mailman.ccsds.org<mailto:sls-slp at mailman.ccsds.org>; Jonathan.J.Wilmot at NASA.gov<mailto:Jonathan.J.Wilmot at NASA.gov>
Cc: Lee Pitts <robert.l.pitts at nasa.gov><mailto:robert.l.pitts at nasa.gov>
Subject: Call for Use Cases of Space Packet Protocol

There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example:
·         ESA has PUS
·         Space Station has its own secondary header
·         Orion is looking for a secondary header
Originally the Space Packet was an envelope for data transferred over single link (includes tunneling), now the packet is being looked at for network data transfer, local onboard data transfer (including measurement broadcasting).
It is possible that the role of the packet might change with the use of DTN bundles.
Just to take the broadest view: We currently have two forms of packets, should there be more or should even these be examined to determine if they should be blended  into a new packet design.
Can we get each of you to send in your present and possibly desired Use Cases for our beloved Space Packet so that we could determine its future.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20190228/5966fabc/attachment.html>