[Moims-sc] CESG overlaps

[Mario.Merri at esa.int]

Nestor,

sorry for the delay in the answer. Below my comments:

Monitor and Control Recommendations: Spacecraft vs TTC Network 
Here I believe there is an overlap which is currently unresolved.

My (simple) thinking is that SLE (or CSTS as they call it now) relates in 
the transfer of TM and TC between GS and CC pretty much at protocol level 
(i.e. w/o any understanding of the TM and TC data that is being 
transferred). Therefore these are transfer services (as they are in fact 
called).

As soon as you go higher in the stack and transfer meaningful data object, 
you get into the MO Service domain. In this context the MD-CSTS overlaps 
with the MO M&C Services. I also believe that the terminations of the 
Transfer Services and MD-CSTS are different: at least in the ESA case, the 
Transfer Services will terminate on one hand in the TMTCS and on the other 
side in the NIS. For the MD-CSTS ESA will have to develop a TM parameter 
provider at the ground station side while on the CC side the parameters 
will be monitored by the MCS. This is the same interface that would be 
required for MO M&C Services (which will eventually be the same used to 
M&C the S/C). Also, this shows that the interfaces for Transfer Services 
and MD-CSTS are completely different and there is little justification to 
keep them with the Transfer Services. The same holds true for TD-CSTS.

Clearly, CCSDS could have specific service definitions for MD and TD, but 
this will be largely inelegant and not a well engineered solution.

File transfer
The SM&C will only provide 1) a service to manage the transfer of files 
(that will use whatever underlined FT mechanism, e.g. CFDP, FTP, SFTP) and 
2) operations in relevant services to make use of files (for instance, the 
SW Management MO Service will include an operation "load SW patch from 
file".)

I believe there is no overlap here.

Archictures vs reference models
CSSA documents should include the MO Services in their architecture. 
Possibly no overlap, but these docs could be the tools to identify/resolve 
overlaps and provide a unified architecture to CCSDS space systems. This 
is not the case now.

TLM, CMD, RNG services
For TLM and CMD, any MO service that needs to communicate with the S/C 
will put the MAL messages in CCSDS TM/TC packets and these will travel 
to/from the S/C as defined by the missions, i.e. via SLE if so decided. 
Therefore, there will not be any specific MAL->SLE binding.

I believe there is no overlap here. 

For Ranging, we go back into the application level services (so potential 
overlapping), but I have not investigated in depth the matter.

Regards,

__Mario



From:   Nestor.Peccia at esa.int
To:     moims-sc at mailman.ccsds.org, 
Date:   29/08/2014 10:49
Subject:        [Moims-sc] CESG overlaps
Sent by:        moims-sc-bounces at mailman.ccsds.org



Dear all, 
The CESG has worked out (and minimised) the number of potential overlaps 
(see attached file) across Areas and WGs. 

Next CESG webex is on 2nd Sept 2014 from 5 till 7 pm.and the main Agenda 
point is the overlap discussion. 

I would appreciate if the SMC WG can send me any comments you might have 
on them 



ciao 
nestor 
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.
[attachment "d1-OverlapIdentifications-29-Aug-2014.xlsx" deleted by Mario 
Merri/esoc/ESA] _______________________________________________
Moims-sc mailing list
Moims-sc at mailman.ccsds.org
http://mailman.ccsds.org/mailman/listinfo/moims-sc


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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20140903/f7cdbdd9/attachment.html>