[Css-csts] RE: DPP Prototype ASN.1 definitions

Wed Jan 22 11:38:24 EST 2014

Dear David,
in the following we provide the answers to the points you raised in your 
two e-mails. Our text is interspersed with your text.

Concerning the development of the Prototype for forward services, can you 
let us know what kind of service are you developing. I mean, have you 
built a dummy service on top of the CSTS Framework, or are you just using 
all structures ( operations, procedures, etc) as provided by the 
Framework? Can we address that in the upcoming Teleconference on 30th 
January?

Concerning the CSTS Spec. Framework book, there is an "editor" version 
from one  week ago, which contains several improvements with respect to 
the October version. However, we are still finalising it . We hope to be 
ready to present the (hopefully) final version at the Telecon. 

Kind regards,
Margherita

-------------------------------------------------------------
Margherita di Giulio
Ground Station Back-end Section (HSO-GIB)
European Space Agency ESA/ESOC
Robert-Bosch-Str. 5
D-64293 Darmstadt - Germany
Tel: +49-6151-902779
e-mail: Margherita.di.Giulio at esa.int

From:   "Zoller, David A. (MSFC-EO50)[HOSC SERVICES CONTRACT]" 
<david.a.zoller at nasa.gov>
To:     "css-csts at mailman.ccsds.org" <css-csts at mailman.ccsds.org>, 
Date:   17/01/2014 15:19
Subject:        [Css-csts] RE: DPP Prototype ASN.1 definitions
Sent by:        css-csts-bounces at mailman.ccsds.org

Dear CSTS WG Members,
Last night, I had additional thoughts on the TransferBuffer so I would 
like to add another set of bullets to the list:

·         TransferBuffer is only mentioned in the Behavior section (4.7.4) 
of Buffered Data Processing
o   Is the usage of the TransferBuffer allowed with Sequence-Controlled 
Data Processing?

The TransferBuffer is indeed only applicable for the Buffered Data 
processing Procedure in the context of forward procedures.

·         TransferBuffer is defined as a ?SEQUENCE OF 
ProcessDataInvocation?
o   Has a definition of ?SEQUENCE OF CstsFrameworkPdu? already been 
considered and rejected?
§  Is that even possible in ASN.1?
§  PDU type checking would be done by the Performer to ensure that they 
are all ProcessDataInvocations in this case

Technically this is possible because CstsFrameworkPdu is a choice of all 
FW operations. However, it is not intended here. The idea is clearly to 
ensure that a TransferBuffer carries only ProcessDataInvocations and not 
any operation.

Best regards,
DZ

David Zoller
COLSA Corporation
MSFC/HOSC - C107 
(Office: (256) 544-1820
*EMail: david.a.zoller at nasa.gov

From: Zoller, David A. (MSFC-EO50)[HOSC SERVICES CONTRACT] 
Sent: Thursday, January 16, 2014 2:27 PM
To: css-csts at mailman.ccsds.org
Subject: DPP Prototype ASN.1 definitions

Dear CSTS WG Members,
I have been updating the DPP Provider prototype with the latest ASN.1 
definitions that I could find which I pulled from the document: 
921x1r2[Draft_201310]_-_All_Services.docx. Please find below some comments 
on the ASN.1 definitions.

·         The ASN.1 uses Performer/Invoker while the document uses 
Provider/User
o   Is there a preferred terminology?
o   I am okay with using both as is ;-)

Clarified in previous e-mails  - no changes

·         BIND and UNBIND invocations use a parameter name of 
invocationHeader while all of the other messages use 
standardInvocationHeader
o   I think it would be better if they were all consistent

Yes, we shall align  the names . 

·         StandardInvocationHeader.procedureInstanceId.procedureType usage
o   I wish to instantiate the appropriate performer type based on the 
invoker?s specified ProcedureType
§  bufferedDataProcessing and sequenceControlledDataProcessing types are 
defined
§  It would be useful to be able to specify bufferedDataProcessingComplete 
and bufferedDataProcessingTimely types
o   Or will there be individual START formats for each of the types that I 
should key on?
o   Should these be part of the Framework baseline ASN.1 or would these be 
extensions for the prototype?

complete/timely transfer mode is a configuration parameter of this 
procedure, and is not provided via the START operation (see chapter 4.7.6) 
If both transfer modes are needed in a given  Service Package (i.e. a 
pass)  two different Service Instances shall be configured, one having the 
"transfer mode" configuration parameter set to "timely" and the other one 
set to "complete". Note that this is also aligned to the "return buffered 
data delivery" procedure. 

·         There were a few errors and warnings while processing the ASN.1
o   These have probably been corrected since the draft in October but let 
me know if anyone needs details

Yes, please provide the details. Thanks.

·         TransferBuffer with ProcessDataInvocations is not incorporated 
into the CstsFrameworkPdu structure yet
o   I am making use of the TransferBufferInvocation with 
TransferDataNotifications until the other is available

(The TransferBuffer is conceived as a data unit which consists of a number 
of individual PROCESS-DATA operations). Your observation is correct and we 
shall add it to the CstsFrameworkPdu

I recognize that this is a work in progress and I probably do not have the 
latest and greatest version. I am willing to help validate the DPP end of 
things as best I can if so desired.

Best regards,
David

David Zoller
COLSA Corporation
MSFC/HOSC - C107 
(Office: (256) 544-1820
*EMail: david.a.zoller at nasa.gov
 _______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts

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/css-csts/attachments/20140122/124da5dd/attachment.htm