[Css-csts] WebEx meeting changed: CSTS Telecon #2

Fri Sep 7 07:56:48 UTC 2018

Hi Miyano-san,
The Concept book and Guidelines are in a very advanced shape and close to 
publication. For the Magenta books, eventually  documenting the CSTS API, 
I have some question marks in my mind:

For SLE the goal was to have interchangeable software components 
implementing standardized APIs , but to the best of my knowledge component 
exchange has not been exercised (except for proof of concept)
Which programming language would you suggest for APIs? SLE uses C++. 
Currently ESA is developing a CSTS SFW implementation in Java 8. However, 
clearly without standardized APIs.
Which benefit do you see in standardizing the APIs?
Which role do you see for UML / SysML from the view point of the a 
standardization body like the CCSDS / CSTS WG? Is it rather documentation 
or also standardization?

I am happy to discuss that in more detail, in Berlin we should find the 
time to do that.

Best regards,
Holger

Holger Dreihahn
European Spacecraft Operations Centre | European Space Agency | S-431
+49 6151 90 2233 | http://www.esa.int/esoc

From:   YOSHIKAZU MIYANO <miyano.yoshikazu at jaxa.jp>
To:     css-csts at mailman.ccsds.org
Date:   05/09/2018 11:11
Subject:        Re: [Css-csts] WebEx meeting changed: CSTS Telecon #2
Sent by:        "CSS-CSTS" <css-csts-bounces at mailman.ccsds.org>

Holger-san,

Thank you for having a slot. 30 minute(10:45 - 11:15) is enough including
discussion, because developing gateway will take several years and 
discussion
will not be concluded just in one workshop.
  Before meeting in Berlin, I will send several page slides including
following discussion points to mailing list.
a) Documentation Priorities
Which documents is highly prioritized after current drafts (Concept 
Book, Guideline,
TD-CSTS, FF-CSTS) are documented ?  When will API books be documented if 
they are
prioritized?
b) MBSE/MBD
If developing gateway is approved within JAXA, I will manage the 
development by Model Based
Development in order for agencies to check the projects of UML/SysML 
tools.  Wiithout
disagreement,  JAXA will design the gateway using Enterprise Architect 
by SparxSystems, which is mostly used in Japan Manufacturing Industry

Regards,

Miyano

On 2018/09/05 14:55, Holger.Dreihahn at esa.int wrote:
> Hi Miyano-san,
> Nice to hear from you. Of course you can have a slot on Tuesday morning
> for a presentation, I suggest to use the session after the coffee break 
in
> the morning to lunch (10:45 - 12:30). That leaves some room for a
> discussion afterwards. Looking at your summary, there might be indeed 
some
> things to discuss.
>
> Regards,
> Holger
>
> Holger Dreihahn
> European Spacecraft Operations Centre | European Space Agency | S-431
> +49 6151 90 2233 | http://www.esa.int/esoc
>
>
>
> From:   YOSHIKAZU MIYANO <miyano.yoshikazu at jaxa.jp>
> To:     css-csts at mailman.ccsds.org
> Date:   05/09/2018 06:10
> Subject:        Re: [Css-csts] WebEx meeting changed: CSTS Telecon #2
> Sent by:        "CSS-CSTS" <css-csts-bounces at mailman.ccsds.org>
>
>
>
> Holger-san,
>
> I will join tomorrow's telecon as soon as another telecon will be
> finished.
>
> Regarding CSTS meeting in Berlin, it possible for me to have
> 10 minute presentation related to MD-CSTS implementation in the morning 
of
> Tuesday?
> I wish to have presentation based on following summary, but I hesitate
> to do because MD-CSTS and SFW BB were published last year.
>
> Summary:
> JAXA does not decide whether MD-CSTS should be implemented especially 
from
> Service
> Provider Side. However, Service User Side in JAXA currently studies how 
to
> implement
>   MD-CSTS gateway to have interoperability with other agencies.
> Apart from interoperability with legacy systems within JAXA, I recognize
> the following
> issues to decide.
> 1) FR SANA Registry
> The following FR, example described in MD-CSTS BB, should be approved
> from "provisional".
> – Antenna;
> – Forward Space Link Carrier Transmission;
> – Forward TC PLOP, Sync, and Channel Encoding;
> – Forward CLTU Transfer Service Provider;
> – Return Space Link Carrier Reception;
> – Return TM Synchronization and Decoding;
> – Return All Frames Transfer Service Provider;
> – Monitored Data CSTS Provider; and
> – Monitored Data Collection.
> 2)Application Program Interface MB books
> Equivalent books of SLE API MB should be documented in order to be
> interoperable
> between agencies.  I wish to confirm whether tech notes such as FR
> reference model exists
> and whether documents of prototyping in MD-CSTS BB can be applied to 
parts
> of API books.
>
> Regards,
>
> Miyano
>
>
>
>

_______________________________________________
CSS-CSTS mailing list
CSS-CSTS at mailman.ccsds.org
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts

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/css-csts/attachments/20180907/367fdeba/attachment.html>