1. 1 Y.Doat (ESA) April 2012 Object Identifiers Object Identifiers CSTS Framework Annex C April 2012

2. 2 Y.Doat (ESA) April 2012 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.

3. 3 Y.Doat (ESA) April 2012 Object Identifiers CSTS Tree

4. 4 Y.Doat (ESA) April 2012 Framework / Modules OIDs Usage: The OIDs are purely used in the document and are not transferred over the wire. Examples: CCSDS-CSTS-OBJECT-IDENTIFIERS … / 1 / 1 / 1 CCSDS-CSTS-ASSOCIATION-CONTROL-TYPES … / 1/ 1 / 5 Purpose: Each ASN.1 Module is allocated an Object Identifier.

5. 5 Y.Doat (ESA) April 2012 Framework / Attributes OIDs Usage: BIND operation uses the Service Instance Identifier (built with OIDs and agreed strings). OID List: Spacecraft Name: scname... / 1 / 2 / 1 Antenna Id.: antenna... / 1 / 2 / 2 Transfer service profile id.: tsprofile... / 1 / 2 / 3 Service instance number: serviceinstancenb... /1/2/4 Purpose: Service Instance Identifier OIDs: Spacecraft name, antenna identification, transfer service profile identification, service instance number.

6. 6 Y.Doat (ESA) April 2012 Framework / Operations OIDs Purpose: Framework operations OIDs, Parameters extension of each operation. Usage: OIDs for all operations invocation, return & acknowledgment. Operation OIDs are NOT transferred on the wire. Extension OIDs are transferred as syntax of the embedded PDV (required for decoding). Examples: StartInvocation:... / 1 / 3 / 9 StartReturn:... / 1 / 3 / 10 startDiagnosticExt... / 1 / 3 / 10 / 1

7. 7 Y.Doat (ESA) April 2012 Framework / Procedures OIDs Purpose: Procedure type OID, Derived procedure type OIDs, Procedures parameters extension OIDs Usage: Procedure Type in the Procedure instance identifier transferred for all invocations, returns and acknowledges. Extension OIDs are transferred as syntax of the embedded PDV (required for decoding). Examples: Association Control:... / 1 / 4 / 9 Notification:... / 1 / 4 / 7 Notif. derived proc.:... / 1 / 4 / 7 /1 Buff.data.delivery start invocation ext.:... / 1 / 4 / 3 /1

8. 8 Y.Doat (ESA) April 2012 Framework / Events OIDs Purpose: Identification of notification types defined within the Framework. Usage: Transferred with the Notification Type of the NOTIFICATION invocation. OID List (defined events): productionConfigured... / 1 / 5 / 1 productionInterrupted... / 1 / 5 / 2 productionHalted... / 1 / 5 / 3 productionOperational... / 1 / 5 / 4

9. 9 Y.Doat (ESA) April 2012 Object Identifiers CSTS Tree

10. 10 Y.Doat (ESA) April 2012 Services Object Identifiers (1/2) Purpose: Identification of all identifiers required for a service. A new service makes use of Framework OIDs but does not add OIDs to the Framework. Approach: Any new service defines 3 sub-branches: Subsequent derived services (in turn defined with 3 sub-branches) Extended service procedures Service modules Examples : Service “a”: MonitoredData… / 2 / 2 / 1 monitoredDataExtServiceParameters …/2/2/1/3 monitoredDataServiceProcedures …/2/2/1/4 Service “b”: Radiometric…/ 2 / 2 / 2

11. 11 Y.Doat (ESA) April 2012 Usage of the 3 sub-branches: (Service “a”)DerivedServices sub-branch: The branch will be used to register services derived from Service “a”. For each derived service, 3 sub- branches will be created. (Service “a”)ServiceProcedures: Service procedures OIDs are listed under that sub-branch; Each sub-branch contains the OIDs for the extended parameters, events... (Service “a”)ServiceModules: ASN.1 service modules identification. Services Object Identifiers (2/2)

12. 12 Y.Doat (ESA) April 2012 Object Identifiers CSTS Tree

13. 13 Y.Doat (ESA) April 2012 Published Identifiers OIDs Definition: a unique identifier that allows identification of a parameter, a directive or an event. This unique identifier is allocated by the Space Assigned Number Authority (SANA). Those identifiers are defined and registered independently from any CSTS procedure and/or services. The identifiers (parameters, events and directives) are grouped per functional resource type. Usage: The defined OIDs are transferred whenever required: GET and NOTIFY as part of Functional Resource Identifier.

14. 14 Y.Doat (ESA) April 2012 Published Identifiers OIDs A Functional Resource Id is made of: Functional Resource Instance Functional Resource Type; Parameter/Event/Directive Name; } 1 OID for the 2 parameters Management: Parameter: SANA; Event: SANA (TBC: Framework events-> move to P.I) ; Directives: SANA (TBC: move Framework directives to P.I.) ; Functional Resource Instance: SM Issues: List of parameters cannot be F.R.Id based. Repeat Framework Events to each SLE/CSTS F.R

15. 15 Y.Doat (ESA) April 2012