ISO 18441:2013
(Main)Space data and information transfer systems — Space Link Extension — Application Program Interface for Transfer Services — Core Specification
Space data and information transfer systems — Space Link Extension — Application Program Interface for Transfer Services — Core Specification
ISO 18441:2013 defines a C++ Application Program Interface (API) for CCSDS Space Link Extension (SLE) Transfer Services, which is independent of any specific technology used for communications between an SLE service user and an SLE service provider. ISO 18441:2013 defines the Application Program Interface in terms of: the components that provide the services of the API; the functionality provided by each of the components; the interfaces provided by each of the components; and the externally visible behavior associated with the interfaces exported by the components. It does not specify: individual implementations or products; the internal design of the components; and the technology used for communications. ISO 18441:2013 defines those aspects of the Application Program Interface which are common for all SLE service types or for a subset of the SLE service types, e.g. all return link services or all forward link services. It also defines a framework for specification of service type-specific elements of the API. Service-specific aspects of the API are defined by supplemental Recommended Practice documents for SLE return link services and SLE forward link services. ISO 18441:2013 for the Application Program Interface responds to the requirements imposed on such an API by the CCSDS SLE transfer service Recommended Standards that were available when ISO 18441:2013 was released.
Systèmes de transfert des informations et données spatiales — Extension de liaisons spatiales — Interface du programme d'application pour les services de transfert — Spécification de base
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 18441
First edition
2013-06-01
Space data and information transfer
systems — Space Link Extension —
Application Program Interface for
Transfer Services — Core Specification
Systèmes de transfert des informations et données spatiales —
Extension de liaisons spatiales — Interface du programme d'application
pour les services de transfert — Spécification de base
Reference number
ISO 18441:2013(E)
©
ISO 2013
---------------------- Page: 1 ----------------------
ISO 18441:2013(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any
means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.
ISO copyright office
Case postale 56 CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2013 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 18441:2013(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of
ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2. www.iso.org/directives
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent
rights identified during the development of the document will be in the Introduction and/or on the ISO list of
patent declarations received. www.iso.org/patents
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
ISO 18441 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as
CCSDS 914.0-M-1, October 2008) and was adopted (without modifications except those stated in Clause 2 of
this International Standard) by Technical Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee
SC 13, Space data and information transfer systems.
© ISO 2013 – All rights reserved iii
---------------------- Page: 3 ----------------------
INTERNATIONAL STANDARD ISO 18441:2013(E)
Space data and information transfer systems — Space Link
Extension — Application Program Interface for Transfer
Services — Core Specification
1 Scope
This International Standard defines a C++ Application Program Interface (API) for CCSDS Space Link
Extension (SLE) Transfer Services, which is independent of any specific technology used for communications
between an SLE service user and an SLE service provider.
This International Standard defines the Application Program Interface in terms of:
a) the components that provide the services of the API;
b) the functionality provided by each of the components;
c) the interfaces provided by each of the components; and
d) the externally visible behavior associated with the interfaces exported by the components.
It does not specify:
a) individual implementations or products;
b) the internal design of the components; and
c) the technology used for communications.
This International Standard defines those aspects of the Application Program Interface which are common for
all SLE service types or for a subset of the SLE service types, e.g. all return link services or all forward link
services. It also defines a framework for specification of service type-specific elements of the API. Service-
specific aspects of the API are defined by supplemental Recommended Practice documents for SLE return
link services and SLE forward link services.
This International Standard for the Application Program Interface responds to the requirements imposed on
such an API by the CCSDS SLE transfer service Recommended Standards that were available when this
International Standard was released.
The scope and field of application are furthermore detailed in subclause 1.3 of the enclosed CCSDS
publication.
2 Requirements
Requirements are the technical recommendations made in the following publication (reproduced on the
following pages), which is adopted as an International Standard:
CCSDS 914.0-M-1, October 2008, Space Link Extension — Application Program Interface for Transfer
Services — Core Specification.
© ISO 2013 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO 18441:2013(E)
For the purposes of international standardization, the modifications outlined below shall apply to the specific
clauses and paragraphs of publication CCSDS 914.0-M-1.
Pages i to v
This part is information which is relevant to the CCSDS publication only.
Page 1-10 and 1-11
Add the following information to the reference indicated:
[1] Document CCSDS 301.0-B-3, January 2002, is equivalent to ISO 11104:2011.
[3] Document CCSDS 910.4-B-2, October 2005, is equivalent to ISO 15396:2007.
[4] Document CCSDS 911.1-B-2, December 2004, is equivalent to ISO 22669:2007.
[5] Document CCSDS 911.2-B-1, December 2004, is equivalent to ISO 22670:2006.
[6] Document CCSDS 911.5-B-2, December 2004, is equivalent to ISO 26143:2007.
[7] Document CCSDS 912.1-B-2, December 2004, is equivalent to ISO 22671:2011.
[8] Document CCSDS 912.3-B-1, December 2004, is equivalent to ISO 22672:2011.
[9] Document CCSDS 913.1-B-1, September 2008, is equivalent to ISO 18440:2013.
[10] Document CCSDS 915.1-M-1, October 2008, is equivalent to ISO 18442:2013.
[11] Document CCSDS 915.2-M-1, October 2008, is equivalent to ISO 18443:2013.
[12] Document CCSDS 915.5-M-1, October 2008, is equivalent to ISO 18444:2013.
[13] Document CCSDS 916.1-M-1, October 2008, is equivalent to ISO 18445:2013.
[14] Document CCSDS 916.3-M-1, October 2008, is equivalent to ISO 18446:2013.
3 Revision of publication CCSDS 914.0-M-1
It has been agreed with the Consultative Committee for Space Data Systems that Subcommittee
ISO/TC 20/SC 13 will be consulted in the event of any revision or amendment of publication CCSDS 914.0-
M-1. To this end, NASA will act as a liaison body between CCSDS and ISO.
2 © ISO 2013 – All rights reserved
---------------------- Page: 5 ----------------------
ISO 18441:2013(E)
Recommendation for Space Data System Practices
SPACE LINK EXTENSION—
APPLICATION PROGRAM
INTERFACE FOR TRANSFER
SERVICES—CORE
SPECIFICATION
RECOMMENDED PRACTICE
CCSDS 914.0-M-1
Magenta Book
October 2008
© ISO 2013 – All rights reserved
3
---------------------- Page: 6 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
AUTHORITY
Issue: Recommended Practice, Issue 1
Date: October 2008
Location: Washington, DC, USA
This document has been approved for publication by the Management Council of the
Consultative Committee for Space Data Systems (CCSDS) and represents the consensus
technical agreement of the participating CCSDS Member Agencies. The procedure for
review and authorization of CCSDS documents is detailed in the Procedures Manual for the
Consultative Committee for Space Data Systems, and the record of Agency participation in
the authorization of this document can be obtained from the CCSDS Secretariat at the
address below.
This document is published and maintained by:
CCSDS Secretariat
Space Communications and Navigation Office, 7L70
Space Operations Mission Directorate
NASA Headquarters
Washington, DC 20546-0001, USA
CCSDS 914.0-M-1 Page i October 2008
© ISO 2013 – All rights reserved
4
---------------------- Page: 7 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
STATEMENT OF INTENT
The Consultative Committee for Space Data Systems (CCSDS) is an organization officially
established by the management of its members. The Committee meets periodically to address
data systems problems that are common to all participants, and to formulate sound technical
solutions to these problems. Inasmuch as participation in the CCSDS is completely
voluntary, the results of Committee actions are termed Recommendations and are not in
themselves considered binding on any Agency.
CCSDS Recommendations take two forms: Recommended Standards that are prescriptive
and are the formal vehicles by which CCSDS Agencies create the standards that specify how
elements of their space mission support infrastructure shall operate and interoperate with
others; and Recommended Practices that are more descriptive in nature and are intended to
provide general guidance about how to approach a particular problem associated with space
mission support. This Recommended Practice is issued by, and represents the consensus of,
the CCSDS members. Endorsement of this Recommended Practice is entirely voluntary
and does not imply a commitment by any Agency or organization to implement its
recommendations in a prescriptive sense.
No later than five years from its date of issuance, this Recommended Practice will be
reviewed by the CCSDS to determine whether it should: (1) remain in effect without change;
(2) be changed to reflect the impact of new technologies, new requirements, or new
directions; or (3) be retired or canceled.
In those instances when a new version of a Recommended Practice is issued, existing
CCSDS-related member Practices and implementations are not negated or deemed to be non-
CCSDS compatible. It is the responsibility of each member to determine when such Practices
or implementations are to be modified. Each member is, however, strongly encouraged to
direct planning for its new Practices and implementations towards the later version of the
Recommended Practice.
CCSDS 914.0-M-1 Page ii October 2008
© ISO 2013 – All rights reserved
5
---------------------- Page: 8 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
FOREWORD
Through the process of normal evolution, it is expected that expansion, deletion, or
modification of this document may occur. This Recommended Practice is therefore subject
to CCSDS document management and change control procedures, which are defined in the
Procedures Manual for the Consultative Committee for Space Data Systems. Current
versions of CCSDS documents are maintained at the CCSDS Web site:
http://www.ccsds.org/
Questions relating to the contents or status of this document should be addressed to the
CCSDS Secretariat at the address indicated on page i.
CCSDS 914.0-M-1 Page iii October 2008
© ISO 2013 – All rights reserved
6
---------------------- Page: 9 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
At time of publication, the active Member and Observer Agencies of the CCSDS were:
Member Agencies
– Agenzia Spaziale Italiana (ASI)/Italy.
– British National Space Centre (BNSC)/United Kingdom.
– Canadian Space Agency (CSA)/Canada.
– Centre National d’Etudes Spatiales (CNES)/France.
– China National Space Administration (CNSA)/People’s Republic of China.
– Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)/Germany.
– European Space Agency (ESA)/Europe.
– Federal Space Agency (FSA)/Russian Federation.
– Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil.
– Japan Aerospace Exploration Agency (JAXA)/Japan.
– National Aeronautics and Space Administration (NASA)/USA.
Observer Agencies
– Austrian Space Agency (ASA)/Austria.
– Belgian Federal Science Policy Office (BFSPO)/Belgium.
– Central Research Institute of Machine Building (TsNIIMash)/Russian Federation.
– Centro Tecnico Aeroespacial (CTA)/Brazil.
– Chinese Academy of Sciences (CAS)/China.
– Chinese Academy of Space Technology (CAST)/China.
– Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia.
– Danish National Space Center (DNSC)/Denmark.
– European Organization for the Exploitation of Meteorological Satellites
(EUMETSAT)/Europe.
– European Telecommunications Satellite Organization (EUTELSAT)/Europe.
– Hellenic National Space Committee (HNSC)/Greece.
– Indian Space Research Organization (ISRO)/India.
– Institute of Space Research (IKI)/Russian Federation.
– KFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary.
– Korea Aerospace Research Institute (KARI)/Korea.
– MIKOMTEK: CSIR (CSIR)/Republic of South Africa.
– Ministry of Communications (MOC)/Israel.
– National Institute of Information and Communications Technology (NICT)/Japan.
– National Oceanic and Atmospheric Administration (NOAA)/USA.
– National Space Organization (NSPO)/Chinese Taipei.
– Naval Center for Space Technology (NCST)/USA.
– Space and Upper Atmosphere Research Commission (SUPARCO)/Pakistan.
– Swedish Space Corporation (SSC)/Sweden.
– United States Geological Survey (USGS)/USA.
CCSDS 914.0-M-1 Page iv October 2008
© ISO 2013 – All rights reserved
7
---------------------- Page: 10 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
DOCUMENT CONTROL
Document Title Date Status
CCSDS Space Link Extension—Application October Original issue
914.0-M-1 Program Interface for Transfer 2008
Services—Core Specification,
Recommended Practice, Issue 1
EC 1 Editorial Change 1 December Updates references to
2008 recent publications
CCSDS 914.0-M-1 Page v DecemOctober 2008ber 2008
© ISO 2013 – All rights reserved
8
---------------------- Page: 11 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
CONTENTS
Section Page
1 INTRODUCTION. 1-1
1.1 PURPOSE OF THIS RECOMMENDED PRACTICE . 1-1
1.2 SCOPE . 1-1
1.3 APPLICABILITY . 1-2
1.4 RATIONALE. 1-3
1.5 DOCUMENT STRUCTURE . 1-3
1.6 DEFINITIONS . 1-7
1.7 REFERENCES . 1-9
2 DESCRIPTION OF THE SLE API . 2-1
2.1 INTRODUCTION . 2-1
2.2 SPECIFICATION METHOD AND NOTATION . 2-2
2.3 LOGICAL VIEW . 2-7
2.4 SECURITY ASPECTS OF CORE SLE API CAPABILITIES. 2-58
3 SPECIFICATION OF API COMPONENTS . 3-1
3.1 INTRODUCTION . 3-1
3.2 API PROXY . 3-1
3.3 API SERVICE ELEMENT . 3-27
3.4 SLE OPERATIONS . 3-52
3.5 SLE UTILITIES . 3-56
3.6 SLE APPLICATION . 3-63
3.7 HANDLING OF IN PROCESS THREADS AND EXTERNAL EVENTS . 3-70
4 STATE TABLES . 4-1
4.1 INTRODUCTION . 4-1
4.2 NOTATION . 4-1
4.3 GENERAL ERROR HANDLING CONVENTIONS . 4-2
4.4 STATE TABLE FOR ASSOCIATIONS . 4-2
4.5 STATE TABLES FOR SERVICE INSTANCES . 4-15
ANNEX A SPECIFICATION OF COMMON INTERFACES (Normative) . A-1
ANNEX B RESULT CODES (Normative) .B-1
ANNEX C STRUCTURE OF THE SERVICE INSTANCE IDENTIFIER FOR
VERSION 1 OF THE SLE SERVICES RAF, RCF, AND CLTU
(Normative). C-1
ANNEX D SIMPLE COMPONENT MODEL (Normative) . D-1
CCSDS 914.0-M-1 Page vi October 2008
© ISO 2013 – All rights reserved
9
---------------------- Page: 12 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
CONTENTS (continued)
Section Page
ANNEX E CONFORMANCE (Normative) .E-1
ANNEX F INTERACTION OF COMPONENTS (Informative) . F-1
ANNEX G INTERFACE CROSS REFERENCE (Informative) . G-1
ANNEX H INDEX TO DEFINITIONS (Informative) . H-1
ANNEX I ACRONYMS AND ABBREVIATIONS (Informative). I-1
ANNEX J INFORMATIVE REFERENCES (Informative) . J-1
Figure
1-1 SLE Services and SLE API Documentation . 1-5
2-1 UML Stereotypes Used in This Recommended Practice . 2-3
2-2 Top Level Decomposition of the API . 2-7
2-3 Structure of the Package API Proxy . 2-9
2-4 Reporting and Tracing by the Proxy . 2-10
2-5 Configuration Database of the Proxy. 2-20
2-6 Structure of the Package API Service Element . 2-23
2-7 Reporting and Tracing by the Service Element . 2-24
2-8 Sequential Control Interface Component Class Controlled Component . 2-39
2-9 Concurrent Control Interface . 2-43
2-10 Structure of the Package SLE Application . 2-44
2-11 Reporting and Tracing Interfaces Provided by the Application . 2-45
2-12 Operation Objects . 2-49
2-13 Operation Object Interfaces for Common Association Management . 2-53
2-14 Common SLE Operation Objects . 2-54
2-15 SLE Utilities . 2-56
4-1 Processing Context for the Association State Table . 4-3
4-2 Processing Context for the Service Instance State Table . 4-16
B-1 Structure of Result Codes .B-1
F-1 Configuration of Components . F-3
F-2 Configuration of Interfaces for Service Provisioning . F-3
F-3 Interaction of API Components . F-4
F-4 Initialization and Shutdown . F-5
F-5 Collaboration Diagram for Use of Operation Objects . F-8
F-6 Sequence Diagram for Use of Operation Objects . F-9
F-7 User Side Binding (User Initiated Bind). F-12
F-8 User Side Unbinding (User Initiated Bind) . F-13
F-9 Provider Side Binding (User Initiated Bind) . F-14
F-10 Provider Side Unbinding (User Initiated Bind) . F-16
CCSDS 914.0-M-1 Page vii October 2008
© ISO 2013 – All rights reserved
10
---------------------- Page: 13 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
CONTENTS (continued)
Table Page
C-1 Identifiers and Abbreviations for Attributes .C-3
E-1 Optional Features for the API Proxy . E-3
E-2 Optional Features for the API Service Element . E-6
E-3 Parameters That May Be Constrained by a Proxy . E-9
E-4 Parameters That May Be Constrained by a Service Element . E-9
CCSDS 914.0-M-1 Page viii October 2008
© ISO 2013 – All rights reserved
11
---------------------- Page: 14 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
1 INTRODUCTION
1.1 PURPOSE OF THIS RECOMMENDED PRACTICE
The purpose of this Recommended Practice is to define a C++ Application Program Interface
(API) for CCSDS Space Link Extension (SLE) Transfer Services, which is independent of
any specific technology used for communications between an SLE service user and an SLE
service provider.
This API is intended for use by application programs implementing SLE services. It can be
configured to support SLE service user applications or SLE service provider applications.
This API is also intended to simplify the implementation of gateways that are required to
achieve interoperability between SLE service provider and SLE service user applications
using different communications technologies.
Using this Application Program Interface Recommended Practice, API implementations
(software packages) able to run on specific platforms can be developed. Once developed,
such a package can be supplied to new users of SLE services for integration with their user or
production facilities, thus minimizing their investment to buy into SLE support.
1.2 SCOPE
1.2.1 ITEMS COVERED BY THIS RECOMMENDED PRACTICE
This Recommended Practice defines the Application Program Interface in terms of:
a) the components that provide the services of the API;
b) the functionality provided by each of the components;
c) the interfaces provided by each of the components; and
d) the externally visible behavior associated with the interfaces exported by the
components.
It does not specify:
a) individual implementations or products;
b) the internal design of the components; and
c) the technology used for communications.
This Recommended Practice defines those aspects of the Application Program Interface,
which are common for all SLE service types or for a subset of the SLE service types, e.g., all
return link services or all forward link services. It also defines a framework for specification
of service type-specific elements of the API. Service-specific aspects of the API are defined
CCSDS 914.0-M-1 Page 1-1 October 2008
© ISO 2013 – All rights reserved
12
---------------------- Page: 15 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
by supplemental Recommended Practice documents for SLE return link services (references
[10], [11], and [12]) and SLE forward link services (references [13] and [14]).
This Recommended Practice for the Application Program Interface responds to the
requirements imposed on such an API by the CCSDS SLE transfer service Recommended
Standards that were available when this Recommended Practice was released.
1.2.2 CONFORMANCE TO CCSDS RECOMMENDED STANDARDS
This version of the SLE API Recommended Practice conforms to the CCSDS Recommended
Standards for Space Link Extension Services, referenced in 1.7, with the exception of the
following optional features:
a) The negotiation procedure for version numbers in the BIND operation is not
supported. If the responder does not support the version number identified in the
BIND Invocation, it responds with a BIND Return containing a negative result and
the diagnostic ‘version number not supported’. The responder does not propose an
alternative version number.
b) Provider-initiated binding, specified by CCSDS Recommended Standards for return
link services is not included in this Recommended Practice. The management
parameters that specify the bind initiative are supported to simplify addition of this
procedure in later versions.
1.3 APPLICABILITY
For the SLE transfer services Return All Frames (RAF), Return Channel Frames (RCF), and
Forward CLTU, the API specified in this document supports two versions, namely:
a) version 1 as specified by references [C1], [C2], and[C3]; and
b) version 2 as specified by references [4], [5], and [7].
Support for version 1 of these services is included for backward compatibility purposes for a
limited time and may not be continued in future versions of this specification. Support for
version 1 of the RAF, RCF and CLTU services implies that SLE API implementations of this
specification are able to interoperate with peer SLE systems that comply with the
specification of the Transport Mapping Layer (TML) in ‘Specification of a SLE API Proxy
for TCP/IP and ASN.1’, ESOC, SLES-SW-API-0002-TOS-GCI, Issue 1.1, February 2001.
Version dependent provisions within this Recommended Practice are marked as follows:
– [V1:] for provisions specific to version 1 of RAF, RCF, or CLTU; and
– [V2:] for provisions specific to version 2 of RAF, RCF, or CLTU.
CCSDS 914.0-M-1 Page 1-2 October 2008
© ISO 2013 – All rights reserved
13
---------------------- Page: 16 ----------------------
ISO 18441:2013(E)
API FOR SLE TRANSFER SERVICES—CORE SPECIFICATION
1.4 RATIONALE
This Recommended Practice describes the services provided by a software package
implementing the API to application software using the API. It specifies the mapping of the
SLE Transfer Services specifications to specific functions and parameters of the SLE API. It
also specifies the distribution of responsibility for specific functions between SLE API
software and application software. The distribution of responsibility has been defined with
due consideration for reusability of software packages implementing the SLE API.
The goal of this Recommended Practice is to create a guide for interoperability between
a) software packages implementing the SLE API; and
b) application software using the SLE API.
This interoperability guide also allows exchangeability of different products implementing
the SLE API, as long as they adhere to the interface specification of this Recommended
Practice.
1.5 DOCUMENT STRUCTURE
1.5.1 OVERVIEW
This Recommended Practice is organized in two parts and a set of annexes.
1.5.1.1 Part I—The Descriptive Part
The descriptive part presents the API Model in section 2 using the Unified Modeling
Language (UML), see reference [J6].
1.5.1.2 Part II—The Prescriptive Part
The prescriptive part contains the specification of the API. In case of any discrepancies
between the descriptive part and the prescriptive part, the specifications in the latter shall
apply.
Section 3 contains detailed specifications of the API components and of the interfaces that
must be provided by the application.
Section 4 defines the state tables that must be implemented by the API.
CCSDS 914.0-M-1 Page 1-3 October 2008
© ISO 2013 –
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.