ISO 23103:2020 pdf download.Space link extension – Cross support transfer service-Specification framework.
The purpose of this Recommended Standard is to define the various logical components, also known within this Recommended Standard as procedures that are required for specifying (‘ross Support Transfer Services (CSTSes).
1.2 SCOPE
1.2.1 ISO 23103 defines, in an abstract manner, a CSTS in terms of:
a) the procedures necessary to provide the service;
b) the states of the service;
c) the behavior of each procedure;
d) the states of the procedures;
e) the operations necessary to constitute the procedures; and
1.3 APPLICABILITY
1.3.1 APPLICABILITY OF THIS RECOMMENDED STANDARD
ISO 23103 provides a basis for the specification and development of Cross Support Services that are intended to be used for developing real systems that implement such services.
Implementation of a service based on the CSTS procedures defined in this Recommended Standard in a real system additionally requires the availability of a communications service to convey invocations and responses of the CSTS operations between the service user and the service provider.
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
f) annex B provides a formal specification of the production status;
g) annex C provides a formal specification of what a qualified parameter is;
h) annex D provides a formal specification of the Object Identifiers and the management of their allocation:
1) annex E defines the composition of Functional Resource Names, Parameter Names, Event Names, Parameter Lists, and Event Lists using Published Identifiers of the appropriate types;
j) annex F provides a formal specification of data types for Protocol Data Units (PDUs) for common operations using Abstract Syntax Notation One (ASN. 1);
An operation is a task that the invoker requests the performer to execute and as such presents the basic interaction pattern between the service user and the service provider. The invocation of an operation may include parameters that specify further details of the task to be performed.
Operations are further classified by the number of interactions required to complete the operation:
a) An unconfirmed operation is invoked by the invoker and performed by the performer, but there is no report on the outcome of the operation.
b) For a confirmed operation the performer provides a report (the ‘return’) to the invoker on success or failure of the operation. Operation returns comprise an indication of success (result has the value ‘positive’) or failure (result has the value ‘negative’) and, in case of failure, a diagnostic that further specifies the reason for the failure. Confirmed operations are further classified as:
1) two-phase operations, for which the performer returns a single report to the.ISO-23103-2020