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

▶
object identifiers
SMART_READER_LITE
LIVE PREVIEW

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

Oct 02, 2023 495 likes •712 views

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

slide-1
SLIDE 1

1 Y.Doat (ESA) October 2013

Object Identifiers

CSTS Framework Annex C

October 2013

slide-2
SLIDE 2

2 Y.Doat (ESA) October 2013

Definitions

  • ISO Definitions:
  • Object identifier (OID): A value (distinguishable from all
  • ther such values) which is associated with an information
  • bject.
  • 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.
slide-3
SLIDE 3

3 Y.Doat (ESA) October 2013

CSTS (1) modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) services (2) protoIdentifiers (1) serviceIdentifiers (2) crossSupportResources (2) iso identified organisation (3) standard producing

  • rganisation

(112) CCSDS (4) Space Link Extension (3) crossSupportFunctionalitiess (1) agenciesFunctionalities (2) FwCrossSupport Functionaities (5) CSS (4) serviceGeneric Functionalities (6)

Object Identifiers CSTS Tree

slide-4
SLIDE 4

4 Y.Doat (ESA) October 2013

Framework / Modules OIDs

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

Purpose:

  • Each ASN.1 Module is allocated

an Object Identifier.

  • 18 different modules

modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) FwCrossSupport Functionaities (5) serviceGeneric Functionalities (6)

slide-5
SLIDE 5

5 Y.Doat (ESA) October 2013

Framework / Attributes OIDs

  • 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
  • Purpose:

Service Instance Identifier OIDs:

  • Spacecraft name,
  • antenna identification,
  • transfer service profile identification,
  • service instance number.

modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) FwCrossSupport Functionaities (5) serviceGeneric Functionalities (6)

slide-6
SLIDE 6

6 Y.Doat (ESA) October 2013

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:

CSTS / 1 / 3 / 9

  • StartReturn:

CSTS / 1 / 3 / 10

  • startDiagnosticExt: CSTS / 1 / 3 / 10 / 1

modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) FwCrossSupport Functionaities (5) serviceGeneric Functionalities (6)

  • perationExt
  • perationExt
  • perationExt
  • perationExt
  • perationExt
  • perationExt
  • peration n
  • peration 1
slide-7
SLIDE 7

7 Y.Doat (ESA) October 2013

Framework / Procedures OIDs

  • Purpose:
  • Registration of procedures &
  • perations derivation
  • Note: The procedure OID are not to

be used as type in the invocations.

  • Usage:
  • Parameters Extension OIDs are

transferred as syntax of the embedded PDV (required for decoding).

  • Examples:
  • Bind Positive Return Ext:

CSTS /1 /4 /1 /2 /1

  • Seq.Ctrl Data Processing start

invocation ext.: CSTS /1 /4 /4 /1 /2 /2 /1

modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) FwCrossSupport Functionaities (5) serviceGeneric Functionalities (6) parameterExtension parameterExtension parameterExtension extendedProcedure Parameter derivedProcedure inside the Framework procedure a extendedProcedureP arameter parameterExtension parameterExtension parameterExtension

slide-8
SLIDE 8

8 Y.Doat (ESA) October 2013

Framework Functional Resources

  • Purpose:
  • Functional Resources of the Framework
  • Configuration parameters, Events and

Directives OIDs defined within the Framework and accessible to the service user.

  • 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

modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) FwCrossSupport Functionaities (5) serviceGeneric Functionalities (6)

slide-9
SLIDE 9

9 Y.Doat (ESA) October 2013

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.

slide-10
SLIDE 10

10 Y.Doat (ESA) October 2013

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

modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) FwCrossSupport Functionaities (5) serviceGeneric Functionalities (6)

Usage:

  • Parameters, Events and Directives

shall be accessed with the object identifiers in that branch but shall be associated with the Functional Resource of the service using them.

slide-11
SLIDE 11

11 Y.Doat (ESA) October 2013

Framework Functional Resources

Examples of types:

  • pBDPinputQueueSizemakes 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 pBDPdataTransferMode SEQUENCE { dataTransferMode INTEGER { undefined (0) , timely (1) , complete (2) } , maxTransferBufferSize IntPos , inputQueueSize IntPos , processingLatencyLimit IntUnsigned } extended of TypeAndValue, OID = 3/112/4/4/1/1/5/6/1/1/0 1 3/112/4/4/1/1/5/6/1/1 pBDPinputQueueSize intUnsigned of TypeAndValue 3 3/112/4/4/1/1/5/6/1/3 pBDPeventsId 2 pBDPdirectiveId 3

slide-12
SLIDE 12

12 Y.Doat (ESA) October 2013

CSTS (1) modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) services (2) protoIdentifiers (1) serviceIdentifiers (2) crossSupportResources (2) iso identified organisation (3) standard producing

  • rganisation

(112) CCSDS (4) Space Link Extension (3) crossSupportFunctionalitiess (1) agenciesFunctionalities (2) FwCrossSupport Functionaities (5) CSS (4) serviceGeneric Functionalities (6)

Object Identifiers CSTS Tree

slide-13
SLIDE 13

13 Y.Doat (ESA) October 2013

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 4 sub-branches:
  • Subsequent derived services (in turn defined

with 4 sub-branches)

  • Extended service procedures
  • Service ASN.1 modules

Examples:

  • Service “a”: MonitoredData CSTS / 2 / 2 / 1

monitoredDataServiceProcedures CSTS/2/2/1/3 monitoredDataServiceModules CSTS/2/2/1/4

  • Service “b”: Radiometric

CSTS / 2 / 2 / 2

services (2) protoIdentifiers (1) serviceIdentifiers (2) Service "a" (Service "a")DerivedService (1) ("Derived service a")DerivedService (1) ("Derived service a")ServiceProcedures (2) ("Derived service a")ServiceModules (3) (Service "a")ServiceProcedures (2)

. . .

{

(Service "a")ServiceModules (3)

Service "a" (Service "a")DerivedService (1) ("Derived service a")DerivedServices (1) ("Derived service a")ServiceProcedures (3) ("Derived service a") ServiceModules (4) (Service "a")ServiceProcedures (3) (Service "a") ServiceModules (4)

. . .

("Derived service a")ExtServiceParameter (2) (Service "a") ExtServiceParameter (2)

slide-14
SLIDE 14

14 Y.Doat (ESA) October 2013

  • 4 sub-branches:
  • (Service “a”)DerivedServices sub-branch:
  • Used to register services derived from

Service “a”.

  • For each derived service, 3 sub-branches

will be created.

  • (Service “a”) ExtServiceParameter
  • Used to register service extensions
  • (Service “a”)ServiceProcedures:
  • Service procedures OIDs are listed under

that branch;

  • Each branch contains the OIDs for the

extended parameters

  • (Service “a”)ServiceModules:
  • ASN.1 service modules identification.

Services Object Identifiers (2/2)

services (2) protoIdentifiers (1) serviceIdentifiers (2) Service "a" (Service "a")DerivedService (1) ("Derived service a")DerivedService (1) ("Derived service a")ServiceProcedures (2) ("Derived service a")ServiceModules (3) (Service "a")ServiceProcedures (2)

. . .

{

(Service "a")ServiceModules (3)

Service "a" (Service "a")DerivedService (1) ("Derived service a")DerivedServices (1) ("Derived service a")ServiceProcedures (3) ("Derived service a") ServiceModules (4) (Service "a")ServiceProcedures (3) (Service "a") ServiceModules (4)

. . .

("Derived service a")ExtServiceParameter (2) (Service "a") ExtServiceParameter (2)

slide-15
SLIDE 15

15 Y.Doat (ESA) October 2013

CSTS (1) modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) services (2) protoIdentifiers (1) serviceIdentifiers (2) crossSupportResources (2) iso identified organisation (3) standard producing

  • rganisation

(112) CCSDS (4) Space Link Extension (3) crossSupportFunctionalitiess (1) agenciesFunctionalities (2) FwCrossSupport Functionaities (5) CSS (4) serviceGeneric Functionalities (6)

Object Identifiers CSTS Tree

slide-16
SLIDE 16

16 Y.Doat (ESA) October 2013

Cross Support Resources

  • Parameter identifier: unique identifier that identifies an atomic resource

that belongs to a Functional Resource or belongs to the configuration associated to the production or provision of the service.

  • Event Identifier: unique identifier of an event defined for service provision
  • r service production
  • Directive identifier: unique identifier of a directive defined for service

provision or service production

  • A unique identifier that allows identification of a parameter, a directive or

an event è allocated by the Space Assigned Number Authority (SANA).

  • The identifiers (parameters, events and directives) are grouped per

functional resource type.

slide-17
SLIDE 17

17 Y.Doat (ESA) October 2013

Cross Support Resources

  • The identifiers (parameters, events and directives) are grouped per

functional resource type.

  • Functional Resource Type: a logical function or related set of functions

that characterizes a unique instance of service provider or production capability. Functional Resource Identifier = Functional Resource Type + Instance

  • Cross Support Resource: Set of Functional Resources that relates to

cross support activities.

  • Usage:
  • The defined OIDs are transferred whenever required: GET and

NOTIFY as part of Functional Resource Identifier.

slide-18
SLIDE 18

18 Y.Doat (ESA) October 2013

Cross-Support Functionalities OIDs

crossSupportFunctionalities (1) functionalResourceType 'a' parametersId (1) functionalResourceType 'n' eventsId (2) directivesId (3)

Functional Resource Parameter F.RType. (P/E/D) Completed OID FCLTU Service Provider parametersId Production status Uplink status SI state Number of CLTUs received Number of CLTUs processed Number of CLTUs radiated Number of CLTUs rejected Acquisition sequence length* Bit lock (CLCW) required* Clcw global VCID* Clcw physical channel* Delivery mode* Expected cltu identification Expected event invocation identification Maximum cltu length* Minimum delay time* Notification mode* Plop 1 idle sequence length* Plop in effect* Protocol abort mode* Reporting cycle* Return timeout period* RF available required* eventsId directiveId 6 3/112/4/4/3/6 1

! "#!!$#%#%#"#&#!#! $ "#!!$#%#%#"#&#!#$ " "#!!$#%#%#"#&#!#" % "#!!$#%#%#"#&#!#% ' "#!!$#%#%#"#&#!#' & "#!!$#%#%#"#&#!#& ( "#!!$#%#%#"#&#!#( ) "#!!$#%#%#"#&#!#) * "#!!$#%#%#"#&#!#* !+ "#!!$#%#%#"#&#!#!+ !! "#!!$#%#%#"#&#!#!! !$ "#!!$#%#%#"#&#!#!$ !" "#!!$#%#%#"#&#!#!" !% "#!!$#%#%#"#&#!#!% !' "#!!$#%#%#"#&#!#!' !& "#!!$#%#%#"#&#!#!& !( "#!!$#%#%#"#&#!#!( !) "#!!$#%#%#"#&#!#!) !* "#!!$#%#%#"#&#!#!* $+ "#!!$#%#%#"#&#!#$+ $! "#!!$#%#%#"#&#!#$! $$ "#!!$#%#%#"#&#!#$$ $" "#!!$#%#%#"#&#!#$"

2 3

slide-19
SLIDE 19

19 Y.Doat (ESA) October 2013

Agencies Functionalities OIDs

A Functional Resource Id is made of:

  • Functional Resource Instance
  • Functional Resource Type;

Parameter/Event/Directive Id are allocated per Functional Resource Type. Management:

  • Parameter, Event, Directive: SANA;
  • Functional Resource Instance: SM.

Usage:

  • A parameter, an event or a directive are

transferred together with their Functional Resource type and instance.

  • An Agency may use this branch to define

its private services.

Agency 'x' functionalResourceType 'a' parametersId (1) functionalResourceType 'n' eventsId (2) directivesId (3) agenciesFunctionalities (2) Agency 'y'

slide-20
SLIDE 20

20 Y.Doat (ESA) October 2013

CSTS (1) modules (1) attributes (2)

  • perations

(3) proceduresExtensions (4) framework (1) services (2) protoIdentifiers (1) serviceIdentifiers (2) crossSupportResources (2) iso identified organisation (3) standard producing

  • rganisation

(112) CCSDS (4) Space Link Extension (3) crossSupportFunctionalitiess (1) agenciesFunctionalities (2) FwCrossSupport Functionaities (5) CSS (4) serviceGeneric Functionalities (6)