[Css-csts] Buffered Data Processing Procedure
Martin Götzelmann
martin.goetzelmann at vega.de
Mon Apr 16 15:17:42 EDT 2012
Der Members of the CSTS WG,
As promised I have summarised the main points of the discussion on the Buffered Data Processing Procedure today for your consideration.
1. Specify two modes (symmetrical to the BDD Procedure)
a. Complete mode
I. If the queue is full, the Service Provider stops reading data from the communication service creating backpressure to the user.
II. If the situation persists, the only means for the user is to PEER-ABORT (derived procedures may add more sophistication)
b. Timely mode
I. If the input queue is full the Service Provider discards the PD invocation
II. Specify a (managed1) parameter to specify whether the Provider shall discard the latest (just received DP invocation or the oldest (at the head of the queue)
III. Specify a (managed) parameter to specify whether the Provider shall issue a notification to the Service user identifying the data unit discarded (could cause bursts of notifications) or not
1) To be defined by a derived procedure or a service using this procedure and possibly delegated to service management
2. How do we handle the interrupted state?
a) Discard all data
I. Enter locked state and require that the user unlocks (by START/STOP or reset), i.e. include the locked state
II. Accept new data as soon as the Production status has recovered
b) Do not discard queued data and resume processing when the PS recovers.
3. Include a maximum queuing time after which a data unit is discarded?
a) Include as (managed) global parameter applicable to all data units
b) Specify as parameter of the PD operation
c) Notify the user that the data unit has been discarded?
Regards, Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20120416/2b760cad/attachment.html
More information about the Css-csts
mailing list