[Css-csts] Intermediate results for "service" terminology for CSTS
Procedures Definition Recommendation
Yves.Doat at esa.int
Yves.Doat at esa.int
Wed Jul 25 03:30:11 EDT 2007
Dear John,
I read your proposed set of definitions and found them very useful (as usual
it took me quite some time to read the input and I apologise).
I have a few comments which I would like to share with you.
Cross-support service. In this definition you mention 'administrative
domain'. This term is not defined elsewhere. I assume that an
'administrative domain' refers to a 'Space Agency'.
Cross support transfer service - Note 1.
Considering we do not have a high level architecture with a corresponding
definition, I would limit this definition to ground-to-ground. In case the
term appears later on in a higher level, we could extend it without
impacting the concept.
Functional Group.
Do we need that definition any longer? The functional group would
correspond to the grouping of more than one service. Do we really need
this concept? What would we gain? My first reaction would be to remove
this definition. We should discuss it.
I found also in the draft book the following terms: Service Data Unit (was
called SLE-SDU) and Protocol Data Unit (was called SLE-PDU). They seem to be
reusable (without SLE). Would you agree?
The SLE books defined the "space link session" and the draft book refers to
"data acquisition session" that could be defined as follows: "A Data
Acquisition Session is a continuous period during which a service provision
provides the capability to a service user to access service production
information (e.g. status of data production, physical channel on a space
link).
I am sure new definitions will pop-up later on.
We will have to discuss the need to update the Reference Model.
Best regards
Yves DOAT
__________________________________________________
Head Ground Infrastructure Baseband Section (OPS-GIB)
ESA/ESOC Robert-Bosch Strasse 5
D-64293 Darmstadt, Germany
Tel.: +49 (6151) 90.2288 Fax:+49 (6151) 90.3046
Internet: http://www.esa.int/
__________________________________________________
John Pietras
<john.pietras at gst.
com> To
Sent by: css-csts at mailman.ccsds.org
css-csts-bounces at m cc
ailman.ccsds.org
Subject
[Css-csts] Intermediate results for
14/03/2007 21:30 "service" terminology for CSTS
Procedures Definition Recommendation
Members of the CSTSWG ---
At the January CSTSWG meeting, I took the action to try to develop a set
of reference model terms appropriate for use in Section 2 of the CSTS
Procedures Definition Specification. The new set of terminology is to
remove the SLE-only orientation of the current material, which was
mainly imported from the front-end material of existing SLE transfer
service specifications.
The attachment contains a set of terminology that I think is a proper
set for use in the CSTS Procedures Definition Specification. I have also
tried to reflect consideration for how this material will integrate into
the larger High-Level Cross Support Architecture (HLCSA) proposed by
IOAG, although I have not worked extensively on this aspect since the
IOAG model is still in its formative stages. The major effect of trying
to accommodate HLCSA concepts (as they have been so far explained to us)
is to explicitly call out "space link services" as a type of cross
support service, roughly equivalent to transfer services. In our current
Cross Support Reference Model, Part 1:SLE (hereinafter referred to as
the SLE-RM) the space link side is treated as a part of service
production. But the IOAG model calls out these types of services, and it
seems to be common practice in the operations community to think of
these services as being oriented with the links themselves, so
representing this perspective is useful (I believe). How these space
link services are specifically defined (e.g., are they associated with a
carrier, or the same antenna, etc.) is a matter for further definition.
However, for the purposes of CSTS Procedures, I think we can ignore the
specifics of the space link services.
As I said, I believe this to be a "proper" set of terms, but practical
considerations may keep us from using some of them, because of
differences of use and meaning with respect to the Cross Support
Concept, the SLE-SRM, and the SLE Service Management Service
Specification. We (CSSA as a whole) may decide that some of these new
terms are not good in any case and reject them; that they are good, but
should not be used in the CSTS Procedures Defn Specification because
they "rock the boat" with respect to the other CSSA documents; or that
the new terms are good targets to which we will eventually collectively
migrate. I did not want to pre-judge CSTSWG's and CSSA's decisions on
these matters, so I am putting forward all of the terms that I think
apply, and we can discuss the technical and practical aspects of using
them.
I am presenting this list of terms to get feedback from the members of
the WG. I hope that we will have some time in tomorrow's telecon to
discuss whether we think this is going in the proper direction or has
some serious flaws (or both). Once we have arrived at a set of terms
that are acceptable to the CSTSWG (as stated below or with agreed
modifications), I will incorporate them into a draft of Section 2 and
distribute them to the WG.
Please accept my apologies for not providing this top you sooner than
the day before the telecon.
I look forward to talking with you tomorrow.
Best regards,
John
John Pietras
Global Science & Technology, Inc. (GST)
7855 Walker Drive
Suite 200
Greenbelt, Maryland, USA
20770-3239
Direct: +1-240-542-1155
GST Main: +1-301-474-9696
Fax: +1-301-474-5970
(See attached file: TermsForCSTSProcSpec070314.doc)
_______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TermsForCSTSProcSpec070314.doc
Type: application/msword
Size: 47104 bytes
Desc: not available
Url : http://mailman.ccsds.org/pipermail/css-csts/attachments/20070725/6987b383/TermsForCSTSProcSpec070314-0001.doc
More information about the Css-csts
mailing list