iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO 22670:2021

(Main)

Space data and information transfer systems — Space link extension (SLE) — Return-channel-frames service specification

Space data and information transfer systems — Space link extension (SLE) — Return-channel-frames service specification

The purpose of this document is to define the Space Link Extension (SLE) Return Channel Frames (RCF) service in conformance with the SLE Reference Model (reference [1]). The RCF service is an SLE transfer service that delivers to a mission user all telemetry frames from one master channel or one virtual channel. This document defines, in an abstract manner, the RCF service in terms of: the operations necessary to provide the service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to acquire telemetry frames from signals received from a spacecraft; the methods or technologies required to provide a suitable environment for communications; or the management activities required to schedule, configure, and control the RCF service. NOTE – Reference [1] defines the Return Master Channel Frames (Rtn MC Frames) service and the Return Virtual Channel Frames (Rtn VC Frames) service as two distinct services. Subsequent study has indicated that it is preferable to define one service that provides the functionality of both. The RCF service defined here does just that. It is anticipated that a future issue of reference [1] will take the same approach, deleting the Rtn MC Frames and Rtn VC Frames services and replacing them with the RCF service.

Systèmes de transfert des informations et données spatiales — Extension de liaisons spatiales (SLE) — Service de réseau pour liaison retour

General Information

Status
Published
Publication Date
29-Jun-2021
ICS
49.140 - Space systems and operations
Technical Committee
ISO/TC 20/SC 13 - Space data and information transfer systems
Drafting Committee
ISO/TC 20/SC 13 - Space data and information transfer systems
Current Stage
6060 - International Standard published
Start Date
30-Jun-2021
Due Date
14-Sep-2020
Completion Date
30-Jun-2021
Ref Project

Relations

Revises
ISO 22670:2013 - Space data and information transfer systems — Space link extension (SLE) — Return-channel-frames service
Effective Date
23-Sep-2017
ISO 22670:2021 - Space data and information transfer systems -- Space link extension (SLE) -- Return-channel-frames service specificationISO 22670:2021 - Space data and information transfer systems -- Space link extension (SLE) -- Return-channel-frames service specification
PreviousNext
Standard
ISO 22670:2021 - Space data and information transfer systems -- Space link extension (SLE) -- Return-channel-frames service specification
English language
141 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO
STANDARD 22670
Third edition
2021-06
Space data and information transfer
systems — Space link extension (SLE)
— Return-channel-frames service
specification
Systèmes de transfert des informations et données spatiales —
Extension de liaisons spatiales (SLE) — Service de réseau pour liaison
retour
Reference number
©
ISO 2021
© ISO 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2021 – All rights reserved

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 (see 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 (see 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.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the World
Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html.
This document was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as CCSDS
911.2-B-3, August 2016) and was adopted (without modifications) by Technical Committee ISO/TC 20,
Space vehicles, Subcommittee SC 13, Space data and information transfer systems.
This third edition cancels and replaces the second edition (ISO 22670:2013), which has been technically
revised.
The main changes compared to the previous edition are as follows:
— adds clarifications and corrections;
— adds production status annex.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
CCSDS RECOMMENDED STANDARD FOR SLE RCF SERVICE
CONTENTS
Section Page
1 INTRODUCTION . 1-1
1.1 PURPOSE OF THIS RECOMMENDED STANDARD . 1-1
1.2 SCOPE . 1-1
1.3 APPLICABILITY . 1-2
1.4 RATIONALE . 1-2
1.5 DOCUMENT STRUCTURE . 1-2
1.6 DEFINITIONS, NOMENCLATURE, AND CONVENTIONS . 1-5
1.7 REFERENCES . 1-13
2 DESCRIPTION OF THE RETURN CHANNEL FRAMES SERVICE . 2-1
2.1 OVERVIEW . 2-1
2.2 SPACE LINK EXTENSION REFERENCE MODEL . 2-2
2.3 SERVICE MANAGEMENT . 2-3
2.4 ARCHITECTURE MODEL—FUNCTIONAL VIEW . 2-4
2.5 ARCHITECTURE MODEL—CROSS SUPPORT VIEW . 2-7
2.6 FUNCTIONAL DESCRIPTION . 2-8
2.7 OPERATIONAL SCENARIO . 2-18
2.8 SECURITY ASPECTS OF THE SLE RCF TRANSFER SERVICE . 2-19
3 RCF SERVICE OPERATIONS . 3-1
3.1 GENERAL CONSIDERATIONS . 3-1
3.2 RCF-BIND . 3-15
3.3 RCF-UNBIND . 3-22
3.4 RCF-START . 3-26
3.5 RCF-STOP . 3-32
3.6 RCF-TRANSFER-DATA . 3-34
3.7 RCF-SYNC-NOTIFY . 3-38
3.8 RCF-SCHEDULE-STATUS-REPORT . 3-42
3.9 RCF-STATUS-REPORT . 3-46
3.10 RCF-GET-PARAMETER . 3-49
3.11 RCF-PEER-ABORT . 3-53
4 RCF PROTOCOL . 4-1
4.1 GENERIC PROTOCOL CHARACTERISTICS . 4-1
4.2 RCF SERVICE PROVIDER BEHAVIOR . 4-4
CCSDS 911.2-B-3 Page vi August 2016
CCSDS RECOMMENDED STANDARD FOR SLE RCF SERVICE
CONTENTS (continued)
Section Page
ANNEX A DATA TYPE DEFINITIONS (NORMATIVE) . A-1
ANNEX B PRODUCTION STATUS (NORMATIVE) .B-1
ANNEX C CONFORMANCE MATRIX (NORMATIVE) . C-1
ANNEX D INDEX TO DEFINITIONS (INFORMATIVE) . D-1
ANNEX E ACRONYMS (INFORMATIVE) .E-1
ANNEX F INFORMATIVE REFERENCES (INFORMATIVE) . F-1
Figure
1-1 SLE Services Documentation . 1-4
2-1 Return Frame Processing SLE-FG . 2-4
2-2 RCF Service Production and Provision . 2-7
2-3 Example of the Management and Provision of RCF Service . 2-8
2-4 Simplified RCF Service Provider State Transition Diagram . 2-11
2-5 Communications Realization of RCF Service . 2-13
2-6 Buffers and Delivery Modes . 2-18
B-1 RCF Production Status Transitions .B-1

Table
2-1 RCF Operations . 2-9
3-1 Setting of RCF Service Configuration Parameters . 3-6
3-2 RCF-BIND Parameters . 3-16
3-3 RCF-UNBIND Parameters . 3-23
3-4 RCF-START Parameters . 3-27
3-5 RCF-STOP Parameters . 3-32
3-6 RCF-TRANSFER-DATA Parameters . 3-34
3-7 RCF-SYNC-NOTIFY Parameters . 3-38
3-8 RCF-SCHEDULE-STATUS-REPORT Parameters . 3-43
3-9 RCF-STATUS-REPORT Parameters . 3-46
3-10 RCF-GET-PARAMETER Parameters . 3-49
3-11 RCF Parameters . 3-51
3-12 RCF-PEER-ABORT Parameters . 3-53
4-1 Provider Behavior . 4-6
4-2 Event Description References . 4-13
4-3 Predicate Descriptions . 4-13
4-4 Boolean Flags . 4-14
4-5 Compound Action Definitions . 4-14
B-1 Production Status Changes and Notifications .B-2
B-2 Effect of Production Status on Operations .B-3
C-1 Conformance Matrix for RCF Service (Operations) .C-1
C-2 Conformance Matrix for RCF Service (Other Requirements) .C-2
CCSDS 911.2-B-3 Page vii August 2016
CCSDS RECOMMENDED STANDARD FOR SLE RCF SERVICE
1 INTRODUCTION
1.1 PURPOSE OF THIS RECOMMENDED STANDARD
The purpose of this Recommended Standard is to define the Space Link Extension (SLE)
Return Channel Frames (RCF) service in conformance with the SLE Reference Model
(reference [1]). The RCF service is an SLE transfer service that delivers to a mission user all
telemetry frames from one master channel or one virtual channel.
NOTE – Reference [1] defines the Return Master Channel Frames (Rtn MC Frames)
service and the Return Virtual Channel Frames (Rtn VC Frames) service as two
distinct services. Subsequent study has indicated that it is preferable to define one
service that provides the functionality of both. The RCF service defined here
does just that. It is anticipated that a future issue of reference [1] will take the
same approach, deleting the Rtn MC Frames and Rtn VC Frames services and
replacing them with the RCF service.
1.2 SCOPE
This Recommended Standard defines, in an abstract manner, the RCF service in terms of:
a) the operations necessary to provide the service;
b) the parameter data associated with each operation;
c) the behaviors that result from the invocation of each operation; and
d) the relationship between, and the valid sequence of, the operations and resulting
behaviors.
It does not specify:
a) individual implementations or products;
b) the implementation of entities or interfaces within real systems;
c) the methods or technologies required to acquire telemetry frames from signals
received from a spacecraft;
d) the methods or technologies required to provide a suitable environment for
communications; or
e) the management activities required to schedule, configure, and control the RCF service.
CCSDS 911.2-B-3 Page 1-1 August 2016
CCSDS RECOMMENDED STANDARD FOR SLE RCF SERVICE
1.3 APPLICABILITY
1.3.1 APPLICABILITY OF THIS RECOMMENDED STANDARD
This Recommended Standard provides a basis for the development of real systems that
implement the RCF service. Implementation of the RCF service in a real system additionally
requires the availability of a communications service to convey invocations and returns of
RCF service operations between RCF service users and providers. This Recommended
Standard requires that such a communications service must ensure that invocations and
returns of operations are transferred:
a) in sequence;
b) completely and with integrity;
c) without duplication;
d) with flow control that notifies the application layer in the event of congestion; and
e) with notification to the application layer in the event that communications between
the RCF service user and the RCF service provider are disrupted, possibly resulting in
a loss of data.
It is the specific intent of this Recommended Standard to define the RCF service in a manner
that is independent of any particular communications services, protocols, or technologies.
1.3.2 LIMITS OF APPLI
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO
ISO 14721:2025(Main)
Space Data System Practices — Reference model for an open archival information system (OAIS)
kSIST ISO 14721:2025

This document defines the CCSDS and International Organization for Standardization (ISO) Reference Model for an Open Archival Information System (OAIS). An OAIS is an Archive system consisting of hardware, software, information, and policy-based processes and procedures put in place and operated by an organization and its staff. The organization has accepted the responsibility to preserve information and make it available for a Designated Community. The organization may be part of a larger organization. The system meets a set of mandatory responsibilities that allow an OAIS Archive to be distinguished from other uses of the term ‘archive’. The set of mandatory responsibilities an OAIS Archive must perform are defined in REF _Ref511638039 \r \h 3.2 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003500310031003600330038003000330039000000 . The term ‘Open’ in OAIS is used to imply that this Recommended Practice, as well as future related Recommended Practices and standards, are developed in open forums, and it does not imply that access to the Archive is unrestricted. The information being maintained has been deemed to need Long Term Preservation, even if the OAIS itself is not permanent. Long Term is long enough to be concerned with the impacts of changing technologies, as well as support for new media and data formats, or with a changing Knowledge Base of the Designated Community or changes within the Designated Community or its definition. Long Term may extend indefinitely. In this Reference Model there is a particular focus on digital information, both as the primary forms of information held and as supporting information for both digitally and physically preserved materials. Therefore, the model accommodates information that is inherently non-digital (e.g., a physical sample), but the modelling and preservation of such information is not addressed in detail. This Reference Model: – provides a framework for the understanding and increased awareness of archival concepts needed for Long Term digital information preservation and access; – provides the concepts needed by non-archival organizations to be effective participants in the preservation process; – provides a framework, including terminology and concepts, for describing and comparing architectures and operations of existing and future Archives; – provides a framework for describing and comparing different Long Term Preservation strategies and techniques; – provides a basis for comparing the data models of digital information preserved by Archives and for discussing how the data models and the underlying information may change over time; – provides a framework that may be expanded by other efforts to cover Long Term Preservation of information that is NOT in digital form (e.g., physical media and physical samples); – expands consensus on the elements and processes for Long Term digital information preservation and access, and promotes a larger market which vendors can support; – guides the identification and production of OAIS-related standards. The reference model addresses a full range of archival information preservation functions including ingest, archival storage, data management, access, and dissemination. It also addresses the migration of digital information to new media and forms, the information models used to represent the information, the role of software in information preservation, and the exchange of digital information among Archives. It identifies both internal and external interfaces to the Archive functions, and it identifies a number of high-level services at these interfaces. It provides various illustrative examples and some ‘best practice’ recommendations. It defines a minimal set of responsibilities for an Archive to be called an OAIS, and it also defines a maximal Archive to provide a broad set of useful terms and concepts.

  • Standard
    139 pages
    English language
    sale 15% off
ISO
ISO 16919:2025(Main)
Space data and information transfer systems — Requirements for bodies providing audit and certification of candidate trustworthy digital repositories

This document defines a CCSDS Recommended Practice (and ISO standard) on which to base the operations of the organization(s) which assess the trustworthiness of digital repositories using the latest version of CCSDS 652.0/ISO 16363 (reference REF R_652x0m2AuditandCertificationofTrustwor \h[1] 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000002900000052005F00360035003200780030006D0032004100750064006900740061006E006400430065007200740069006600690063006100740069006F006E006F0066005400720075007300740077006F0072000000 ) and provide the appropriate certification. This document specifies requirements for bodies providing audit and certification of digital repositories, based on the metrics contained within ISO/IEC 17021-1 (reference REF R_ISOIEC170212011ConformityAssessmentReq \h \* MERGEFORMAT [4] 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000002900000052005F00490053004F0049004500430031003700300032003100320030003100310043006F006E0066006F0072006D006900740079004100730073006500730073006D0065006E0074005200650071000000 ) and reference REF R_652x0m2AuditandCertificationofTrustwor \h[1] 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000002900000052005F00360035003200780030006D0032004100750064006900740061006E006400430065007200740069006600690063006100740069006F006E006F0066005400720075007300740077006F0072000000 . It is primarily intended to support the accreditation of bodies providing such certification. ISO/IEC 17021-1 provides the bulk of the requirements on bodies offering audit and certification for general types of management systems. However, for each specific type of system, specific additional requirements will be needed, for example, to specify the standard against which the audit is to be made and the qualifications which auditors require. This document provides the (small number of) specific additions required for bodies providing audit and certification of candidate trustworthy digital repositories. Trustworthy here means that they can be trusted to maintain, over the long-term, the understandability and usability of digitally encoded information placed into their safekeeping. In order improve readability the section numbers are kept consistent with those of ISO/IEC 17021-1. Some subsections are applicable as they stand, and these are simply enumerated; otherwise additions to subsections are explicitly given. In the former case the sections may consist of just a few sentences. As a result this document must be read in conjunction with ISO/IEC 17021-1. The requirements contained in this CCSDS Recommended Practice need to be demonstrated in terms of competence and reliability by any organization or body providing certification of digital repositories.

  • Standard
    23 pages
    English language
    sale 15% off
ISO
ISO 23507:2025(Main)
Space data and information transfer systems — Information preparation to enable long term use

This document deals with the aspects of a project, in particular the terminology used. Many of these terms are already used with various definitions within the target communities for this practice, for example, space, science, life sciences, libraries, records management, and archival communities. It is expected that other communities can easily map this terminology to the terminology used within those communities. The Reference Model for an Open Archival Information System (OAIS) provided a starting point and inputs from a variety of other sources were used to arrive at the terms used within this standard. This document accomplishes the following: – identifies the Additional Information to be collected or improved at various points; – forms a basis for the specification of Data Management Plans (DMPs); – forms a basis for the identification and/or development of additional standards and implementation guides, including those that address particular concerns in more detail.

  • Standard
    59 pages
    English language
    sale 15% off
ISO
ISO 16363:2025(Main)
Space data and information transfer systems — Audit and certification of trustworthy digital repositories

This document defines a CCSDS Recommended Practice on which to base an audit and certification process for assessing the trustworthiness of digital repositories. The scope of application of this document is the entire range of digital repositories.

  • Standard
    77 pages
    English language
    sale 15% off
ISO
ISO 22669:2021(Main)
Space data and information transfer systems — Space link extension (SLE) — Return-all-frames service specification

This document defines, in an abstract manner, the RAF service in terms of: the operations necessary to provide the service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to acquire telemetry frames from signals received from a spacecraft; the methods or technologies required to provide a suitable environment for communications; or the management activities required to schedule, configure, and control the RAF service.

  • Standard
    136 pages
    English language
    sale 15% off
ISO
ISO 21077:2021(Main)
Space data and information transfer systems — Digital motion imagery

The purpose of this document is to provide a common reference and framework of standards for digital motion video and imagery, and to provide recommendations for utilization of international standards for sharing or distributing motion video and imagery between spacecraft elements and ground systems. The scope of this document includes traditional real-time streaming video and television, including human and robotic spacecraft-to-spacecraft and spacecraft-to-ground systems, as well as video recorded and distributed later, either as a real-time stream or as a file transfer. In this context, real-time streaming includes all modes where video is sent from a spacecraft in a continuous stream and is intended for immediate use when received, regardless of the latency of the transmission path. Other specialized motion imagery applications, such as high-speed scientific motion imagery and multi-spectral motion imagery, are not addressed in this document. However, if a specialized imagery camera system has a requirement to interface to spacecraft systems in a video mode, it would be required to match these interfaces. Ground-systems-to-ground-systems video distribution is obviously a key component of the entire video system. However, this is not the primary focus of this document. Currently, there are significant differences in the ways mission video products are exchanged between the various space agencies on the ground. This is the result of differences in network topologies between space agencies, and agreements for video sharing. Those differences preclude there being a standard methodology for delivering video imagery between agencies. Prior to the commencement of video transmission between space agencies, system design reviews and performance testing should be done between the ground systems in use to assure operability when video imagery comes from spacecraft.

  • Standard
    34 pages
    English language
    sale 15% off
ISO
ISO 13541:2021(Main)
Space data and information transfer systems — Attitude data messages

This document specifies two standard message formats for use in transferring spacecraft attitude information between space agencies: the Attitude Parameter Message (APM) and the Attitude Ephemeris Message (AEM). Such exchanges are used for: - preflight planning for tracking or attitude estimation support; - scheduling attitude and data processing support; - carrying out attitude operations; - performing attitude comparisons; - carrying out attitude propagations and/or sensor predictions; - testing to initialize sub-system simulators (communications, power, etc.). This document includes sets of requirements and criteria that the message formats have been designed to meet. For exchanges where these requirements do not capture the needs of the participating agencies, another mechanism may be selected.

  • Standard
    52 pages
    English language
    sale 15% off
ISO
ISO 22672:2021(Main)
Space data and information transfer systems — Space link extension (SLE) — Forward space packet service specification

This document defines the Forward Space Packet (FSP) service in conformance with the transfer services specified in reference [1], Cross Support Reference Model―Part 1: SLE Services. The FSP service is a Space Link Extension (SLE) transfer service that enables a mission to send Space Packets to a spacecraft in sequence-controlled or expedited mode. This document defines, in an abstract manner, the FSP service in terms of: the operations necessary to provide the transfer service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to radiate Space Packets to a spacecraft and to acquire telemetry frames from the signals received from that spacecraft for extraction of the Operational Control Field; the methods or technologies required for communications; or the management activities necessary to schedule, configure, and control the FSP service. NOTE – While the FSP service as described in reference [1] is conceived to handle a variety of packet data structures, this version of the FSP Recommended Standard is restricted to the handling of Space Packets as defined in reference [6]. This version of the FSP Recommended Standard is specific to the transfer of Space Packets to be transmitted via the Telecommand protocol stack as defined in references [3], [4], and [5]. The Cross Support Reference Model (reference [1]) specifies that the FSP service may also be used in conjunction with the Advanced Orbiting System protocol stack, but that mode of operation is outside the scope of this version of the Recommended Standard. The FSP service is provided in the online delivery mode, as defined in reference [1]. The offline delivery mode is the subject of further study.

  • Standard
    190 pages
    English language
    sale 15% off
ISO
ISO 22671:2021(Main)
Space data and information transfer systems — Space link extension (SLE) — Forward communications link transmission unit (CLTU) service specification

This document defines the Communications Link Transmission Unit (CLTU) service in conformance with the transfer services specified in reference [1], Cross Support Reference Model—Part 1: SLE Services. The Forward CLTU service is a Space Link Extension (SLE) transfer service that enables a mission to send Communications Link Transmission Units (CLTUs) to a spacecraft. This document defines, in an abstract manner, the Forward CLTU service in terms of: the operations necessary to provide the transfer service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to radiate data to a spacecraft and to acquire telemetry frames from the signals received from that spacecraft for extraction of the Operational Control Field; the methods or technologies required for communications; or the management activities necessary to schedule, configure, and control the Forward CLTU service.

  • Standard
    143 pages
    English language
    sale 15% off
ISO
ISO 18441:2021(Main)
Space data and information transfer systems — Space link extension — Application program interface for transfer services — Core specification

This document 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. This document 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 (references [10], [11], and [12]) and SLE forward link services (references [13] and [14]). This document 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 document was released.

  • Standard
    365 pages
    English language
    sale 15% off