[Css-csts] Sequence Counter in Transfer-Data-Invocation

[John Pietras]

Tim,

I think that the only thing that makse sense is that the sequence be
tied to the procedure instance. The TransferDataInvocation carrying a
telemetry frame (in BDD) serves a completely different purpose from the
TransferDataInvocation carrying periodic status info as part of a Cyclic
Report procedure instance. Even multiple instances of the same procedure
type are different frome each other because they are sending different
data at different periodicities, etc. 

 

Good catch! A RID needs to be submitted to make 3.9.2.4.2 increment with
respect  to the procedure instance.

 

John

 

From: css-csts-bounces at mailman.ccsds.org
[mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J.
(GSFC-5830)
Sent: Thursday, August 19, 2010 5:23 PM
To: css-csts at mailman.ccsds.org
Subject: [Css-csts] Sequence Counter in Transfer-Data-Invocation

 

Hello all,

 

If multiple concurrent procedures are all using the Transfer-Data
operation, what is the prescribed behavior of the sequence-counter field
within the Transfer-Data-Invocation?  Here are 2 possible behaviors:

 

Behavior #1:  Within each procedure-instance the sequence-counter starts
at 1 and increases monotonically.

 

Behavior #2:  The sequence-number of the first Transfer-Data-Invocation
is 1.  For each Transfer-Data-Invocation that follows, the
sequence-number shall increase monotonically (regardless of the source
procedure-instance).

 

Our intention is clear (see the note after 3.9.2.4.2).  But as the
implementer of the User side, I'm not sure whether to check for
continuity at the Procedure level (behavior #1) or the Operation level
(behavior #2).

 

Best regards,

Tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20100820/841c3459/attachment.htm