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

Wed Jan 29 13:53:19 EST 2014

Dear CSTS WG members,
Please find below another set of items for clarification and issue resolution. These are in reference to the October 2013 draft and may be resolved in the later version. These do not need to be rushed for answer by tomorrow's teleconference.
Best regards,
David

·         4.6.2.2 Concept

·         4.6.3.3.8  Notification of Production Status Changes

o   4.6.2.2 - The service provider will notify the service user of successful completion of processing only it explicitly requested

o   4.6.2.2 - The service provider will always notify the service user of failure of processing

o   4.6.3.3.8  - The service provider shall notify the service user when the production status changes to 'operational' or 'halted'

o   4.6.3.3.8  - The service provider shall notify the service user when the production status changes to 'interrupted' only if and when a data unit is impacted

o   Is my understanding correct?:

1)      This is independent of the Notification procedure and does not require the service user to have issued a "START Notification"

a.       NOTE: Currently in the prototype, production status change notification is through the instantiated  Data Processing procedure so the service user will not get these events until after a "START Data Processing" invocation

2)      The current production status is not relayed to the service user - only a change in status

3)      If a Data Unit which requests a process-completion-report is interrupted then only a Production Status Change (Interrupted) event should be sent to the service user and never a completion report

4)      The Notify Invocation has three ASN.1 ObjectIDs that must be filled in as follows:

a.       For production status change events:

·         NotifyInvocation.standardInvocationHeader.procedureInstanceId.procedureType

o    Set to bufferedDataProcessing or sequenceControlledDataProcessing

·         NotifyInvocation.notificationType.eventName.functionalResourceName.functionalResourceType

o    Set to productionStatus

·         NotifyInvocation.notificationType.eventName.paramOrEventId

o    Set to productionHalted, productionOperational, productionInterrupted

o    productionConfigured will never be sent in this context

b.      For processing completed events:

·         NotifyInvocation.standardInvocationHeader.procedureInstanceId.procedureType

o    Set to bufferedDataProcessing or sequenceControlledDataProcessing

·         NotifyInvocation.notificationType.eventName.functionalResourceName.functionalResourceType

o    Set to ??

·         NotifyInvocation.notificationType.eventName.paramOrEventId

o    Set to dataProcessingCompleted

c.       Both types of events will extend NotifyInvocation.extensionParameter using DataProcessingNotifyInvocExt

·         E3.1 SERVICE-INSTANCE-ID

o   Two instances of a typographical error: "servicecInstanceNumberId" should be "serviceInstanceNumberId"

·         E3.8  PROCEDURE - DATA PROCESSING PDUS

o   DataProcessingNotifyInvocExt, BufferedDataProcessingNotifyInvocExt are defined in the document but do not show up in the ASN.1 compiler generated source code.

o   BufferedDataProcessingNotifyInvocExt does not extend the base DataProcessingNotifyInvocExt and so is not needed

o   CCSDS-CSTS-SEQUENCE-CONTROLLED-DATA-PROCESSING-PDUS re-defines DataProcessingNotifyInvocExt instead of an extension SequContrDataProcessingNotifyInvocExt

·         E3.10  PROCEDURE - SEQUENCE-CONTROLLED DATA PROCESSING PDUS

o   Variable names are not aligned:

§  ProcessDataPosReturnExt uses "dataSequenceCounter" and "extensionParameter"

§  ProcessDataNegReturnExt uses "sequenceCounter"         and "extension"

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20140129/9cc19c74/attachment-0001.htm