Object Identifiers CSTS Framework Annex C October 2013 Y.Doat - PowerPoint PPT Presentation

Object Identifiers CSTS Framework Annex C October 2013 Y.Doat (ESA) October 2013 1

Definitions • ISO Definitions: • Object identifier (OID) : A value (distinguishable from all other such values) which is associated with an information object. • Information object : A well-defined piece of information, definition, or specification which requires a name in order to identify its use in an instance of communication. • Framework: • Uses Object Identifiers to identify: - Framework components; - Services components; - Published Identifiers. • Object identifiers are organised in a tree. Y.Doat (ESA) October 2013 2

October 2013 Y.Doat (ESA) Space Link Extension modules (1) (3) attributes (2) framework operations (1) (3) Object Identifiers CSTS Tree proceduresExtensions (4) CSTS FwCrossSupport (1) Functionaities (5) identified organisation standard producing serviceGeneric organisation CCSDS Functionalities (6) (112) CSS (4) (4) (3) iso protoIdentifiers (1) services (2) serviceIdentifiers (2) crossSupportResources crossSupportFunctionalitiess (1) (2) agenciesFunctionalities (2) 3

Framework / Modules OIDs framework (1) Purpose : • Each ASN.1 Module is allocated proceduresExtensions an Object Identifier. Functionalities (6) Functionaities (5) FwCrossSupport serviceGeneric • 18 different modules operations attributes modules (1) (4) (2) (3) Usage : • The OIDs are purely used in the document and are not transferred over the wire. Examples : • CCSDS-CSTS-OBJECT-IDENTIFIERS: CSTS / 1 / 1 / 1 • CCSDS-CSTS-ASSOCIATION-CONTROL-TYPES: CSTS / 1 / 1 / 6 Y.Doat (ESA) October 2013 4

Framework / Attributes OIDs • Purpose : framework (1) Service Instance Identifier OIDs: • Spacecraft name, • antenna identification, proceduresExtensions Functionalities (6) Functionaities (5) FwCrossSupport serviceGeneric • transfer service profile identification, operations attributes modules (1) (4) (2) (3) • service instance number. • Usage : • BIND operation uses the Service Instance Identifier (built with OIDs and agreed strings). • OID List : • Spacecraft Name: scname: CSTS / 1 / 2 / 1 • Antenna Id.: antenna: CSTS / 1 / 2 / 2 • Transfer service profile id.: tsprofile: CSTS / 1 / 2 / 3 • Service instance number: serviceinstancenb: CSTS/1/2/4 Y.Doat (ESA) October 2013 5

Framework / Operations OIDs • Purpose : framework (1) • Framework operations OIDs, • Parameters extension of each operation. proceduresExtensions Functionalities (6) Functionaities (5) FwCrossSupport serviceGeneric operations attributes modules (1) (2) (3) (4) • Usage : • OIDs for all operations: invocation, return & acknowledgment. Operation OIDs are NOT transferred on the operation 1 wire. operationExt operationExt operationExt • Extension OIDs are transferred as syntax of the embedded PDV (required for decoding). operation n • Examples : operationExt operationExt • StartInvocation: operationExt CSTS / 1 / 3 / 9 • StartReturn: CSTS / 1 / 3 / 10 • startDiagnosticExt: CSTS / 1 / 3 / 10 / 1 Y.Doat (ESA) October 2013 6

Framework / Procedures OIDs • Purpose : framework (1) • Registration of procedures & operations derivation • Note: The procedure OID are not to proceduresExtensions Functionalities (6) Functionaities (5) be used as type in the invocations. FwCrossSupport serviceGeneric operations attributes modules • Usage : (1) (2) (3) (4) • Parameters Extension OIDs are transferred as syntax of the embedded PDV (required for decoding). procedure a • Examples : • Bind Positive Return Ext: derivedProcedure CSTS /1 /4 /1 /2 /1 inside the Framework • Seq.Ctrl Data Processing start extendedProcedure invocation ext.: Parameter CSTS /1 /4 /4 /1 /2 /2 /1 parameterExtension parameterExtension parameterExtension extendedProcedureP arameter parameterExtension parameterExtension parameterExtension Y.Doat (ESA) October 2013 7

Framework Functional Resources • Purpose : framework (1) • Functional Resources of the Framework • Configuration parameters, Events and proceduresExtensions Directives OIDs defined within the Framework Functionalities (6) Functionaities (5) FwCrossSupport serviceGeneric operations and accessible to the service user. attributes modules (1) (4) (2) (3) • Usage : • Procedure Type in the Procedure instance identifier transferred for all invocations, returns and acknowledges. • The OIDs are transferred with the Functional Resource Identifier of the CSTS making use of them. • Examples : • Notification procedure type: CSTS /1/5/10 • Data Processing Input queue size configuration: CSTS /1 /5 /5 /1 /1 • Buffer Data Delivery – End of data notification: CSTS /1 /5 /4 /2 /2 Y.Doat (ESA) October 2013 8

Framework Functional Resources The Framework Functional Resources have the same structure as the Cross-Support Functional Resources: ⇒ Can be accessed by GET and NOTIFY in the same way as Cross-Support Functional Resources; ⇒ A parameter is identified by its OID, its syntax makes use of a standard Framework type or defines its own extension; ⇒ A parameter/event/directive is transferred with the procedure instance identifier it belongs to. Y.Doat (ESA) October 2013 9

Service Generic Resources Purposes : • The serviceGenericFunctionalities identifiers branch lists those functionalities that are generic and accessible by all services using the framework . • Those identifiers cover the productions statuses and the events related to a change of configuration framework Usage: (1) • Parameters, Events and Directives shall be accessed with the object identifiers in that branch but shall proceduresExtensions Functionalities (6) Functionaities (5) FwCrossSupport serviceGeneric be associated with the Functional operations attributes modules (1) (4) (2) (3) Resource of the service using them. Y.Doat (ESA) October 2013 10

Framework Functional Resources Examples of types : • pBDPinputQueueSize makes use of the intUnsigned of TypeAndValue • pBDPdataTransferMode defines a complex type as an extension of TypeAndValue framework definition with its own syntax. • The syntax of pBDPdataTransferMode is identified by an OID built as pBDPdataTransferMode/0 Note : pBDPinputQueueSize and pBDPdataTransferMode are transferred with the procedure instance identifier of the Buffer Data Processing procedure. procBufferDataProcessing 6 3/112/4/4/1/1/5/6 pBDPparametersId 1 SEQUENCE { dataTransferMode INTEGER { undefined (0) , timely (1) , complete (2) } pBDPdataTransferMode 1 3/112/4/4/1/1/5/6/1/1 , maxTransferBufferSize IntPos , inputQueueSize IntPos , processingLatencyLimit IntUnsigned } extended of TypeAndValue, OID = 3/112/4/4/1/1/5/6/1/1/0 pBDPinputQueueSize intUnsigned of TypeAndValue 3 3/112/4/4/1/1/5/6/1/3 Y.Doat (ESA) pBDPeventsId 2 October 2013 11 pBDPdirectiveId 3

October 2013 Y.Doat (ESA) Space Link Extension modules (1) (3) attributes (2) framework operations (1) (3) Object Identifiers CSTS Tree proceduresExtensions (4) CSTS FwCrossSupport (1) Functionaities (5) identified organisation standard producing serviceGeneric organisation CCSDS Functionalities (6) (112) CSS (4) (4) (3) iso protoIdentifiers (1) services (2) serviceIdentifiers (2) crossSupportResources crossSupportFunctionalitiess (1) (2) agenciesFunctionalities (2) 12

Services Object Identifiers (1/2) Purpose : services (2) • Identification of all identifiers required for a service. • A new service makes use of Framework OIDs but does serviceIdentifiers protoIdentifiers not add OIDs to the Framework. (1) (2) Approach : • Any new service defines 4 sub-branches : { • Subsequent derived services (in turn defined Service "a" Service "a" with 4 sub-branches) (Service "a")DerivedService (1) • Extended service procedures (Service "a")DerivedService (1) • Service ASN.1 modules ("Derived service a")DerivedServices (1) ("Derived service a")DerivedService (1) . . . . . . ("Derived service a")ExtServiceParameter (2) Examples : ("Derived service a")ServiceProcedures (2) ("Derived service a")ServiceProcedures (3) • Service “a”: MonitoredData CSTS / 2 / 2 / 1 monitoredDataServiceProcedures CSTS/2/2/1/3 ("Derived service a") ServiceModules (4) ("Derived service a")ServiceModules (3) monitoredDataServiceModules CSTS/2/2/1/4 (Service "a") ExtServiceParameter (2) (Service "a")ServiceProcedures (2) • Service “b”: Radiometric CSTS / 2 / 2 / 2 (Service "a")ServiceProcedures (3) (Service "a")ServiceModules (3) (Service "a") ServiceModules (4) Y.Doat (ESA) October 2013 13