<font size=2 face="sans-serif">Hi Scott, Mario,</font>
<br>
<br><font size=2 face="sans-serif">If I may add one more detail, which
may be of interest to Scott:</font>
<br>
<br><font size=2 face="sans-serif">In the context of the METERON project,
ESA has already implemented, deployed and operationally validated some
of the MO M&C services to publish a various set of TM parameters (which
were not Spacecraft related but for instance related to the health status
of a laptop and even the status of a button on particular software running
on that laptop on the ISS) using DTN BP at communication layer (we used
ION 2.3 and are currently updating to ION 3.2).</font>
<br>
<br><font size=2 face="sans-serif">We have also implemented a so called
BPPing Agent, which was deployed on each DTN node and periodically pinged
other nodes. The results of the BPPings were then published to all intersted
listeners (our M&C system instances) using again the related MO M&C
Parameter service.</font>
<br>
<br><font size=2 face="sans-serif">In practice, the mentioned M&C service
were used to publish and receive the TM parameters encoded in binary over
BP over Channel Protocol (the convergence layer below BP) from ISS to the
ground. The exact same implementation of these services (same code at run-time)
had published a second endpoint to provide the same functionality via a
different protocol (XML encoding over HTTP) on the ground.</font>
<br>
<br><font size=2 face="sans-serif">So basically two set of different consumers
have used the same services to retrieve the TM, using the communication
protocol of their choice. If you are interested, I can prepare a presentation
for the discussion session. I have added Sebastian in cc, who is our DTN
expert, in case of DTN specific questions.</font>
<br>
<br><font size=2 face="sans-serif">Kind Regards</font>
<br><font size=2 face="sans-serif">Mehran</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Mario.Merri@esa.int</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Scott, Keith
L." <kscott@mitre.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Barkley, Erik
J \(317H\)" <erik.j.barkley@jpl.nasa.gov>, moims-sc@mailman.ccsds.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">14/10/2014 11:21</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Moims-sc] Re:
Would SM&C have a few hours to discuss network
management?</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">moims-sc-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Arial">Hi Keith,</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
I have earmarked a 2h joint meeting with SIS-DTN in the agenda of SM&C
WG starting at 13:30 of Thu 13Nov. Is that OK?</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
Without pre-emptying the discussion, the MO SM&C Services provide a
coherent set of services to monitor and control *any* remote (controllable)
object, not necessarily only as spacecraft. The operations of these services
are defined in an abstract manner (via the MAL). For a specific deployment,
and here I am touching on your question on "how those parameters are
encoded and transported, the abstract services need to be mapped to a concrete
encoding/transport. This is achieved by a dedicated blue book at the level
of MAL.</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
The bottom line is that</font><font size=3> </font><font size=2 face="Arial"><br>
- one can use the MO M&C services to monitor and control any remote
object</font><font size=3> </font><font size=2 face="Arial"><br>
- one can select the most appropriate encoding/transport for its deployment
of these services.</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
I hope the above helps. How do you want to play the joint meeting? For
instance, would you like to send us in advance a set of questions that
you would like to be addressed?</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
Thanks</font><font size=3> <br>
</font><font size=2 face="Arial"><br>
__Mario</font><font size=3> <br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
From: </font><font size=1 face="sans-serif">"Scott,
Keith L." <kscott@mitre.org></font><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
To: </font><font size=1 face="sans-serif">"Mario.Merri@esa.int"
<Mario.Merri@esa.int>, "Barkley, Erik J (317H)" <erik.j.barkley@jpl.nasa.gov>,
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Cc: </font><font size=1 face="sans-serif">"roger.thompson@scisys.co.uk"
<roger.thompson@scisys.co.uk></font><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Date: </font><font size=1 face="sans-serif">13/10/2014
20:09</font><font size=3> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Subject: </font><font size=1 face="sans-serif">Would
SM&C have a few hours to discuss network management?</font><font size=3>
<br>
</font>
<hr noshade><font size=3><br>
<br>
</font><font size=4 face="Calibri"><br>
The SIS-DTN working group is about to start doing some work in the network
management for the BP layers of the stack. Would it be possible for
us to get a few hours together with SM&C to talk about the interaction
between the monitor and control services and what we (think we) need for
DTN network management? I’m thinking just an hour or two for the
two WGs to exchange their views of what’s going on would be really helpful
to us.</font><font size=3> </font><font size=4 face="Calibri"><br>
</font><font size=3> </font><font size=4 face="Calibri"><br>
>From my interpretation of the 522.1-R-3 book, the MO SM&C Services
provides a framework for (general-purpose) monitor and control, which is
tailored towards spacecraft. *<b>IF</b>* I understand correctly,
a way for e.g. Bundle Protocol network management could ‘plug in’ to
SM&C with a set of ‘drivers’ for the spacecraft to monitor / control
the various BP parameters of interest according to the various SM&C
services. [Is that a completely broken characterization?] There’s
then a question of how those parameters are encoded and transported.</font><font size=3>
</font><font size=4 face="Calibri"><br>
</font><font size=3> </font><font size=4 face="Calibri"><br>
Sometime Thursday (PM?) of the CCSDS meetings would be best for the SIS-DTN
WG, but we’re meeting Thursday and Friday and if that wouldn’t work,
I’ll find some other time.</font><font size=3> </font><font size=4 face="Calibri"><br>
</font><font size=3> </font><font size=4 face="Calibri"><br>
I know that Erik and the CSS groups are interested in talking with you
as well, and that would be a good time for them.</font><font size=3> </font><font size=4 face="Calibri"><br>
</font><font size=3> </font><font size=4 face="Calibri"><br>
</font><font size=3> </font><font size=4 face="Calibri"><br>
--keith</font><font size=3> </font><font size=4 face="Calibri"><br>
</font><font size=3> </font>
<br><tt><font size=3>This message and any attachments are intended for
the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
</font></tt><tt><font size=2>_______________________________________________<br>
Moims-sc mailing list<br>
Moims-sc@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/moims-sc"><tt><font size=2>http://mailman.ccsds.org/mailman/listinfo/moims-sc</font></tt></a><tt><font size=2><br>
</font></tt>
<br><PRE>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.
</PRE>