iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO 12175:1994/Amd 1:2015

(Amendment)

Space data and information transfer systems — Standard formatted data units — Structure and construction rules — Amendment 1

Space data and information transfer systems — Standard formatted data units — Structure and construction rules — Amendment 1

Systèmes de transfert des informations et données spatiales — Unités de données à structuration normalisée (SFDU) — Règles de structure et de construction — Amendement 1

General Information

Status
Published
Publication Date
15-Jun-2015
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
16-Jun-2015
Due Date
17-Mar-2017
Completion Date
17-Mar-2017
Ref Project

Relations

Amends
ISO 12175:1994 - Space data and information transfer systems — Standard formatted data units — Structure and construction rules
Effective Date
18-Dec-2021
ISO 12175:1994/Amd 1:2015ISO 12175:1994/Amd 1:2015
PreviousNext
Standard
ISO 12175:1994/Amd 1:2015
English language
53 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO
STANDARD 12175
First edition
1994-10-20
AMENDMENT 1
2015-07-01
Space data and information transfer
systems — Standard formatted data
units — Structure and construction
rules
AMENDMENT 1
Systèmes de transfert des informations et données spatiales — Unités
de données à structuration normalisée (SFDU) — Règles de structure
et de construction
AMENDEMENT 1
Reference number
ISO 12175:1994/Amd.1:2015(E)
©
ISO 2015
ISO 12175:1994/Amd.1:2015(E)
© ISO 2015, Published in Switzerland
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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved

Consultative
Committee for
Space Data Systems
RECOMMENDATION FOR SPACE
DATA SYSTEM STANDARDS
STANDARD FORMATTED
DATA UNITS —
STRUCTURE AND
CONSTRUCTION RULES
CCSDS 620.0-B-2
Note:
BLUE BOOK
This current
issue includes
all updates through
May 1992
Technical Corrigendum 1,
dated November 1996.
TMG 8/92
CCSDS Recommendation for SFDUs: Structure and Construction Rules
AUTHORITY
Issue: Blue Book, Issue 2
Date: May 1992
Location: CCSDS Panel 2 Meeting, May
1992, Oberpfaffenhofen, Germany
This Recommendation reflects the consensus technical agreement of the following member Agencies
of the Consultative Committee for Space Data Systems (CCSDS):
• British National Space Centre (BNSC) / United Kingdom
• Canadian Space Agency (CSA) / Canada
• Centre National D’Etudes Spatiales (CNES) / France
• Deutsche Forschungsanstalt für Luft und Raumfahrt (DLR) / FRG
• European Space Agency (ESA) / Europe
• Instituto de Pesquisas Espaciais (INPE) / Brazil
• National Aeronautics and Space Administration (NASA) / USA
• National Space Development Agency of Japan (NASDA) / Japan
The following observer Agencies also concur with this Recommendation:
• Department of Communication/Communications Research Centre (DOC/CRC)
/ Canada
• Institute for Space Astronautics and Science (ISAS) / Japan
This Recommendation is published and maintained by:
CCSDS Secretariat
Communications and Data Systems Division, (Code-OS)
National Aeronautics and Space Administration
Washington, DC 20546, USA
Issue 2 May 1992
iii
CCSDS Recommendation for SFDUs: Structure and Construction Rules
FOREWORD
This document is a technical Recommendation for the standardisation of the structure and construction
rules of Standard Formatted Data Units (SFDU), for the interchange of digital space-related data in an
open data system and has been prepared by the Consultative Committee for Space Data Systems
(CCSDS). Other aspects of the SFDU concept are described in documents listed in the Reference
section.
This Recommendation defines SFDU structures that will handle some of the problems of digital data
interchange and several construction rules that will limit the SFDUs to a practical set that can exist in
an open data system environment. It allows implementing organisations within each Agency to proceed
coherently with the development of compatible derived Standards for space data systems and widely
dispersed data users that are within their cognisance.
Through the process of normal evolution, it is expected that expansion, deletion, or modification to this
document may occur. This Recommendation is therefore subject to CCSDS document management
and change control procedures which are defined in Reference [1].
Questions relating to the contents or status of this document should be addressed to the CCSDS
Secretariat.
Issue 2 May 1992
iv
CCSDS Recommendation for SFDUs: Structure and Construction Rules
STATEMENT OF INTENT
The Consultative Committee for Space Data Systems (CCSDS) is an organisation officially established
by the management of the member space Agencies. The committee meets periodically to address data
system 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 the
committee are termed RECOMMENDATIONS and are not considered binding to any Agency.
This Recommendation is issued by, and represents the consensus of, the CCSDS Plenary body.
Agency endorsement of the Recommendation is entirely voluntary. Endorsement, however, indicates
the following understandings:
• Whenever an Agency establishes a CCSDS-related Standard, this Standard
will be in accordance with the relevant Recommendation. Establishing such
a Standard does not preclude other provisions which an Agency may develop.
• Whenever an Agency establishes a CCSDS-related Standard, the Agency will
provide other CCSDS member Agencies with the following information:
- The Standard itself.
- The anticipated date of initial operational capability.
- The anticipated duration of operational service.
• Specific service arrangements shall be made via memorandum of agreement.
Neither this Recommendation nor any ensuing Standard is a substitute for a
memorandum of agreement.
No later than five years from its date of issuance, this Recommendation 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 cancelled.
Issue 2 May 1992
v
CCSDS Recommendation for SFDUs: Structure and Construction Rules
DOCUMENT CONTROL
Document Title Date Status/
Remarks
CCSDS 620.0-B-1 Recommendation for Space Data System Feb 1988 Issue 1
Standards: Standard Formatted Data
Units -- Structure and Construction Rules,
Blue Book, Issue 1
CCSDS 620.0-B-2 Recommendation for Space Data System May 1992 Issue 2,
Standards: Standard Formatted Data see note
Units -- Structure and Construction Rules, below
Blue Book, Issue 2
Note: The major changes from Issue 1 to Issue 2 are the inclusion of techniques for the following:
• For linking a data description with its identifier (ADID).
• For delimiting data objects other than by length.
• For referencing external labelled and unlabelled data objects.
Issue 2 is forwards compatible with the whole of Issue 1.
Issue 2 May 1992
vi
CCSDS Recommendation for SFDUs: Structure and Construction Rules
CONTENTS
Sections
1 INTRODUCTION . 1
1.1 Purpose and Scope . 1
1.2 Applicability . 1
1.3 Recommended Approach to Reading the Document . 1
2 SFDU OVERVIEW . 4
2.1 Introduction . 4
2.2 The SFDU Building Block - The LABEL-VALUE-OBJECT . 4
2.3 SFDU Structuring . 5
2.3.1 Simple LVOs . 5
2.3.2 Compound LVOs . 6
2.3.2.1 Exchange Data Unit (EDU) . 6
2.3.2.2 Application Data Unit (ADU) . 7
2.3.2.3 Description Data Unit (DDU) . 7
2.4 EDU Structure Diagram . 8
3 LVO LABEL FIELD SPECIFICATIONS USED IN SFDUS . 9
3.1 LVO LABEL Specification - Version ID = 1 . 9
3.1.1 Version ID . 9
3.1.2 Authority and Description Identifier (ADID) . 9
3.1.2.1 Control Authority Identifier (CAID) . 9
3.1.2.2 Data Description Identifier (DDID) . 10
3.1.3 Class ID . 10
3.1.4 Spare 1 . 10
3.1.5 Spare 2 . 10
3.1.6 Length . 10
3.1.7 Structure Diagram . 11
3.2 LVO LABEL Specification - Version ID = 2 . 11
3.2.1 Version ID . 11
3.2.2 Authority and Description Identifier (ADID) . 11
3.2.2.1 Control Authority Identifier (CAID) . 11
3.2.2.2 Data Description Identifier (DDID) . 12
3.2.3 Class ID . 12
3.2.4 Spare 1 . 12
3.2.5 Spare 2 . 12
3.2.6 Length . 12
3.2.7 Structure Diagram . 12
3.3 LVO LABEL Specification - Version ID = 3 . 13
3.3.1 Version ID . 13
3.3.2 Authority and Description Identifier (ADID) . 13
3.3.2.1 Control Authority Identifier (CAID) . 13
3.3.2.2 Data Description Identifier (DDID) . 13
3.3.3 Class ID . 14
3.3.4 Delimitation . 14
3.3.4.1 Length (Specified in ASCII) - Delimitation ID = A . 14
3.3.4.2 Length (Specified in Binary) - Delimitation ID = B . 15
Issue 2 May 1992
vii
CCSDS Recommendation for SFDUs: Structure and Construction Rules
3.3.4.3 Marker Pattern - Delimitation ID = S . 15
3.3.4.4 Sequential End-of-File (EOF) - Delimitation ID = E . 16
3.3.4.5 Contiguous End-of-File (EOF) - Delimitation ID = C . 16
3.3.4.6 Shared End-of-File (EOF) - Delimitation ID = F . 16
3.3.5 Spare . 17
3.3.6 Delimitation Parameter . 17
3.3.7 Structure Diagram . 17
4 CLASS ID SPECIFICATIONS . 18
4.1 Structure Classes . 18
4.1.1 Exchange Data Unit - Class ID = Z . 18
4.1.2 Application Data Unit - Class ID = U . 19
4.1.3 Description Data Unit - Class ID = F . 19
4.2 Service Classes . 19
4.2.1 Replacement Service Object - Class ID = R . 19
4.2.2 Data Administration Service Object - Class ID = C . 19
4.3 Data Classes . 20
4.3.1 Application Data Object - Class ID = I . 20
4.3.2 Supplementary Data Object - Class ID = S . 20
4.3.3 Data Description Record Object - Class ID = D . 20
4.3.4 Data Entity Dictionary Object - Class ID = E . 20
4.3.5 Catalogue Attribute Object - Class ID = K . 20
4.3.6 Volume Preparation Data Object - Class ID = V . 20
4.4 Overview of Structure Class IDs . 21
5 CCSDS ADID SPECIFICATIONS . 22
5.1 Specification for ADID = CCSD0001 . 22
5.2 Specification for ADID = CCSD0003 . 22
5.3 Specification for ADID = CCSD0004 . 24
5.4 Specification for ADID = CCSD0005 . 25
5.5 Specification for ADID = CCSD0009 . 26
6 COMBINATION OF ADIDS AND CLASS IDS . 27
Annex A: Acronyms . 30
Annex B: Glossary of Terms . 32
Annex C: ASN.1 Definitions . 34
C.1 ASN.1 Definition of the LVO Structure . 34
C.2 ASN.1 Definition of the DDR for ADID = CCSD0001 . 40
C.3 ASN.1 Definition of the DDR for ADID = CCSD0003 . 41
C.4 ASN.1 Definition of the DDR for ADID = CCSD0004 . 42
C.5 ASN.1 Definition of the DDR for ADID = CCSD0005 . 43
C.6 ASN.1 Definition of the DDR for ADID = CCSD0009 . 44
Annex D: ASCII & Restricted ASCII Codes . 46
Annex E: Octet Numbering Convention and Nomenclature . 48
Annex F: Proposed Referencing Environment Specifications . 50
F.1 Basic Referencing Environment - $CCSDS1 . 50
F.2 Extended Referencing Environment - $CCSDS2 . 51
Issue 2 May 1992
viii
CCSDS Recommendation for SFDUs: Structure and Construction Rules
INDEX . 53
Figures
Figure 1-1: Example Structure Diagram . 2
Figure 2-1: The LABEL-VALUE-OBJECT Structure . 4
Figure 2-2: Structure Diagram of a Simple LVO . 6
Figure 2-3: Structure Diagram of a Compound LVO . 6
Figure 2-4: Example of the Use of ADUs . 7
Figure 2-5: Example of the Use of DDUs . 8
Figure 2-6: Structure Diagram of an EDU . 8
Figure 3-1: CCSDS LABEL Specification - Version ID = 1 . 9
Figure 3-2: Structure Diagram for an LVO with Version ID = 1 . 11
Figure 3-3: CCSDS LABEL Specification - Version ID = 2 . 11
Figure 3-4: Structure Diagram for an LVO with Version ID = 2 . 12
Figure 3-5: CCSDS LABEL Specification - Version ID = 3 . 13
Figure 3-6: Schematic of a Marker Pattern Delimited LVO . 15
Figure 3-7: Structure Diagram for an LVO with Version ID = 3 .
...

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 22670:2021(Main)
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.

  • Standard
    141 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 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
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