iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO 23103:2020

(Main)

Space link extension — Cross support transfer service — Specification framework

Space link extension — Cross support transfer service — Specification framework

1.1.1 This Recommended Standard 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 f) the parameters associated with each operation. 1.1.2 It does not specify: a) individual application services, implementations, or products; b) the implementation of entities or interfaces within real systems; c) the methods or technologies required to acquire data; d) the methods or technologies required to provide a suitable environment for communications; or e) the management activities required to schedule and configure services.

Titre manque

General Information

Status
Published
Publication Date
30-Jan-2020
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
31-Jan-2020
Due Date
14-Sep-2019
Completion Date
31-Jan-2020
Ref Project

Buy Standard

ISO 23103:2020 - Space link extension -- Cross support transfer service -- Specification frameworkISO 23103:2020 - Space link extension -- Cross support transfer service -- Specification framework
PreviousNext
Standard
ISO 23103:2020 - Space link extension -- Cross support transfer service -- Specification framework
English language
329 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 23103
First edition
2020-01
Space link extension — Cross support
transfer service — Specification
framework
Reference number
ISO 23103:2020(E)
©
ISO 2020

---------------------- Page: 1 ----------------------
ISO 23103:2020(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO 2020
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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 23103:2020(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 (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 Consultative Committee for Space Data Systems (CCSDS) (as CCSDS
921.1-B-1, April 2017) and drafted in accordance with its editorial rules. It was assigned to Technical
Committee ISO/TC 20, Space vehicles, Subcommittee SC 13, Space data and information transfer systems
and adopted under the “fast-track procedure”.
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.
© ISO 2020 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 23103:2020(E)
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
CONTENTS
Section Page
1 INTRODUCTION . 1-1
1.1 PURPOSE . 1-1
1.2 SCOPE . 1-1
1.3 APPLICABILITY . 1-1
1.4 RATIONALE . 1-2
1.5 DOCUMENT STRUCTURE . 1-2
1.6 DEFINITIONS, NOMENCLATURE AND CONVENTIONS . 1-5
1.7 REFERENCES . 1-19
2 DESCRIPTION OF CROSS SUPPORT SERVICES . 2-1
2.1 OVERVIEW . 2-1
2.2 CROSS SUPPORT REFERENCE MODEL . 2-3
2.3 SERVICE MANAGEMENT . 2-4
2.4 ELEMENTS OF THE CSTS SPECIFICATION FRAMEWORK . 2-5
2.5 PRINCIPLES OF USING THE CSTS SPECIFICATION FRAMEWORK . 2-9
2.6 PROTOCOL DESCRIPTION . 2-11
3 COMMON OPERATIONS . 3-1
3.1 OVERVIEW . 3-1
3.2 GENERAL CONSIDERATIONS . 3-1
3.3 STANDARD OPERATION HEADER . 3-6
3.4 BIND (CONFIRMED) . 3-9
3.5 UNBIND (CONFIRMED) . 3-14
3.6 PEER-ABORT (UNCONFIRMED) . 3-15
3.7 START (CONFIRMED) . 3-17
3.8 STOP (CONFIRMED) . 3-19
3.9 TRANSFER-DATA (UNCONFIRMED) . 3-20
3.10 PROCESS-DATA (UNCONFIRMED / CONFIRMED) . 3-22
3.11 NOTIFY (UNCONFIRMED) . 3-24
3.12 GET (CONFIRMED) . 3-26
3.13 EXECUTE-DIRECTIVE (ACKNOWLEDGED) . 3-31
4 PROCEDURES . 4-1
4.1 OVERVIEW . 4-1
4.2 COMMON PROCEDURES BEHAVIOR . 4-1
4.3 ASSOCIATION CONTROL . 4-3
4.4 UNBUFFERED DATA DELIVERY . 4-10
CCSDS 921.1-B-1 Page vi April 2017
© ISO 2020 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 23103:2020(E)
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
CONTENTS (continued)
Section Page
4.5 BUFFERED DATA DELIVERY . 4-15
4.6 DATA PROCESSING . 4-39
4.7 BUFFERED DATA PROCESSING. 4-54
4.8 SEQUENCE-CONTROLLED DATA PROCESSING . 4-66
4.9 INFORMATION QUERY . 4-83
4.10 CYCLIC REPORT . 4-87
4.11 NOTIFICATION . 4-98
4.12 THROW EVENT . 4-109
ANNEX A IMPLEMENTATION CONFORMANCE STATEMENT
PROFORMA (NORMATIVE) . A-1
ANNEX B PRODUCTION STATUS (NORMATIVE) .B-1
ANNEX C QUALIFIED PARAMETERS (NORMATIVE) . C-1
ANNEX D OBJECT IDENTIFIERS DEFINITION (NORMATIVE) . D-1
ANNEX E COMPOSITION OF PARAMETER, EVENT, AND DIRECTIVE
NAMES AND PARAMETER AND EVENT LISTS  (NORMATIVE) .E-1
ANNEX F DATA TYPES DEFINITION (NORMATIVE) . F-1
ANNEX G SERVICE STATE TABLES (NORMATIVE) . G-1
ANNEX H SECURITY, SANA, AND PATENT CONSIDERATIONS
(INFORMATIVE) . H-1
ANNEX I INFORMATIVE REFERENCES (INFORMATIVE) . I-1
ANNEX J INDEX TO DEFINITIONS (INFORMATIVE) . J-1
ANNEX K ACRONYMS (INFORMATIVE) . K-1
ANNEX L OBJECT IDENTIFIERS (INFORMATIVE) .L-1
ANNEX M PUBLISHED IDENTIFIERS FOR FUNCTIONAL
RESOURCES REGISTERED UNDER THE
CROSSSUPPORTFUNCTIONALITIES NODE (INFORMATIVE) . M-1
Figure
1-1 Cross Support Service Documentation . 1-4
2-1 CSTS Specification Framework Concept . 2-2
2-2 Service and Procedure States (Stateful Prime Procedure) . 2-13
2-3 Service and Procedure States (Stateless Prime Procedure) . 2-14
2-4 Communications Realization of a Cross Support Transfer Service . 2-17
4-1 Services Using a Buffered Data Delivery Procedure . 4-18
4-2 Real-Time and Complete Buffered Data Delivery Service Instances
and Supporting Buffering Mechanisms . 4-19
A-1 Production Status Diagram .B-1
C-1 CSTS and Cross Support Resources Root Object Identifier Tree . D-2
C-2 ‘procedures’ Subtree . D-6
CCSDS 921.1-B-1 Page vii April 2017
© ISO 2020 – All rights reserved

---------------------- Page: 5 ----------------------
ISO 23103:2020(E)
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
CONTENTS (continued)
Figure Page
C-3 ‘fwProceduresFunctionalities’ Subtree . D-8
C-4 ‘services’ Subtree . D-9
C-5 ‘service procedures’ Subtree . D-10
C-6 ‘crossSupportFunctionalities’ Subtree . D-12
C-7 ‘agenciesFunctionalities’ Subtree . D-14
L-1 Cross Support Services Part of the CCSDS Object Identifiers Tree . L-1
L-2 CSS Object Identifiers Tree . L-1
L-3 CSTS Object Identifiers Tree . L-2
L-4 CSTS Specification Framework Object Identifiers Tree . L-3
L-5 CSTS Services Object Identifiers Tree . L-4
L-6 CSTS Published Identifiers—Object Identifiers Tree . L-6
M-1 Example Cross Support Functional Resources . M-2
M-2 Subcarrier Related Parameters of the Rtn401SpaceLinkCarrierRecpt
Functional Resource . M-3

Table
2-1 Common Operations Defined by the CSTS Specification Framework . 2-6
2-2 Common Procedures Defined by the CSTS Specification Framework . 2-8
2-3 Use of Operations by Common Procedures . 2-9
3-1 Standard Confirmed Operation Header Parameters . 3-6
3-2 Standard Unconfirmed Operation Header Parameters . 3-6
3-3 BIND Operation Parameters . 3-10
3-4 UNBIND Operation Parameters . 3-14
3-5 PEER-ABORT Operation Parameters . 3-15
3-6 START Operation Parameters . 3-18
3-7 STOP Operation Parameters . 3-19
3-8 TRANSFER-DATA Operation Parameters . 3-20
3-9 PROCESS-DATA Operation Parameters . 3-22
3-10 NOTIFY Operation Parameters . 3-24
3-11 GET Operation Parameters . 3-29
3-12 EXECUTE-DIRECTIVE Operation Parameters . 3-32
4-1 Association Control Procedure Required Operations . 4-7
4-2 Association Control Procedure Configuration Parameters . 4-7
4-3 Association Control Procedure State Table . 4-8
4-4 Procedure State Table Incoming Event Description References . 4-9
4-5 Procedure State Table Predicate Descriptions . 4-9
4-6 Procedure State Table Simple Action References . 4-9
4-7 Procedure State Table Compound Action Definitions . 4-9
4-8 Unbuffered Data Delivery Procedure Required Operations . 4-12
CCSDS 921.1-B-1 Page viii April 2017
© ISO 2020 – All rights reserved

---------------------- Page: 6 ----------------------
ISO 23103:2020(E)
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
CONTENTS (continued)
Table Page
4-9 Unbuffered Data Delivery Procedure State Table . 4-13
4-10 Procedure State Table Incoming Event Description References . 4-13
4-11 Procedure State Table Predicate Descriptions . 4-13
4-12 Procedure State Table Boolean Flags . 4-14
4-13 Procedure State Table Simple Action References . 4-14
4-14 Buffered Data Delivery Procedure Required Operations . 4-25
4-15 START Extension Parameters . 4-25
4-16 Buffered Data Delivery Procedure Configuration Parameters . 4-31
4-17 Buffered Data Delivery Procedure State Table . 4-32
4-18 Procedure State Table Incoming Event Description References . 4-34
4-19 Procedure State Table Predicate Descriptions . 4-34
4-20 Procedure State Table Boolean Flags . 4-34
4-21 Procedure State Table Simple Action References . 4-35
4-22 Procedure State Table Compound Action Definitions . 4-35
4-23 Data Processing Procedure Required Operations . 4-45
4-24 PROCESS-DATA Extension Parameter . 4-45
4-25 NOTIFY Extension Parameters . 4-46
4-26 Data Processing Procedure Configuration Parameters . 4-50
4-27 Data Processing Procedure State Table . 4-51
4-28 Procedure State Table Incoming Event Description References . 4-52
4-29 Procedure State Table Predicate Descriptions . 4-52
4-30 Procedure State Table Boolean Flags . 4-53
4-31 Procedure State Table Simple Action References . 4-53
4-32 Procedure State Table Compound Action Definitions . 4-53
4-33 Buffered Data Processing Procedure Required Operations . 4-60
4-34 Buffered Data Processing Procedure Configuration Parameters . 4-61
4-35 Buffered Data Processing Procedure State Table . 4-62
4-36 Procedure State Table Incoming Event Description References . 4-64
4-37 Procedure State Table Predicate Descriptions . 4-64
4-38 Procedure State Table Boolean Flags . 4-65
4-39 Procedure State Table Simple Action References . 4-65
4-40 Procedure State Table Compound Action Definitions . 4-65
4-41 Sequence-Controlled Data Processing Procedure Required Operations . 4-72
4-42 START Extension Parameters . 4-72
4-43 PROCESS-DATA Invocation Extension Parameters . 4-73
4-44 PROCESS-DATA Return Extension Parameters . 4-73
4-45 Sequence-Controlled Data Processing Procedure Configuration Parameters . 4-79
4-46 Sequence-Controlled Data Processing Procedure State Table . 4-80
4-47 Procedure State Table Incoming Event Description References . 4-81
4-48 Procedure State Table Predicate Descriptions . 4-82
4-49 Procedure State Table Simple Action References . 4-82
CCSDS 921.1-B-1 Page ix April 2017
© ISO 2020 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 23103:2020(E)
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
CONTENTS (continued)
Table Page
4-50 Procedure State Table Compound Action Definitions . 4-82
4-51 Information Query Procedure Required Operations . 4-85
4-52 Information Query Procedure Configuration Parameters . 4-85
4-53 Information Query Procedure State Table . 4-86
4-54 Procedure State Table Incoming Event Description References . 4-86
4-55 Procedure State Table Predicate Descriptions . 4-86
4-56 Procedure State Table Simple Action References . 4-86
4-57 Cyclic Report Procedure Required Operations . 4-92
4-58 START Extension Parameters . 4-93
4-59 Cyclic Report Procedure Configuration Parameters . 4-96
4-60 Cyclic Report Procedure State Table . 4-96
4-61 Procedure State Table Incoming Event Description References . 4-97
4-62 Procedure State Table Predicate Descriptions . 4-97
4-63 Procedure State Table Simple Action References . 4-97
4-64 Procedure State Table Compound Action Definitions . 4-97
4-65 Notification Procedure Required Operations . 4-103
4-66 START Extension Parameters . 4-103
4-67 Notification Procedure Configuration Parameters . 4-107
4-68 Notification Procedure State Table . 4-107
4-69 Procedure State Table Event Description References . 4-108
4-70 Procedure State Table Predicate Descriptions . 4-108
4-71 Procedure State Table Simple Action References . 4-108
4-72 Procedure State Table Compound Action Definitions . 4-108
4-73 Throw Event Procedure Required Operations . 4-111
4-74 Throw Event Procedure Configuration Parameters . 4-113
4-75 Throw Event Procedure State Table . 4-113
4-76 Procedure State Table Incoming Event Description References . 4-114
4-77 Procedure State Table Predicate Definitions . 4-114
4-78 Procedure State Table Simple Action References . 4-114
A-1 Production Status Semantic .B-2
A-2 Production Status Transitions .B-3
F-1 State Table for CSTSes with a Stateless Prime Procedure Instance . G-2
F-2 State Table for CSTSes with a Stateless Prime Procedure Instance:
Event Description References . G-2
F-3 State Table for CSTSes with a Stateless Prime Procedure Instance:
Predicate Descriptions . G-2
F-4 State Table for CSTSes with a Stateless Prime Procedure Instance:
Compound Action Definitions . G-3
F-5 State Table for CSTSes with a Stateful Prime Procedure Instance . G-4
CCSDS 921.1-B-1 Page x April 2017
© ISO 2020 – All rights reserved

---------------------- Page: 8 ----------------------
ISO 23103:2020(E)
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
CONTENTS (continued)
Table Page
F-6 State Table for CSTSes with a Stateful Prime Procedure Instance:
Event Description References . G-5
F-7 State Table for CSTSes with a Stateful Prime Procedure Instance:
Predicate Descriptions . G-5
F-8 State Table for CSTSes with a Stateful Prime Procedure Instance:
Compound Action Definitions . G-5
G-1 Identification of PICS . A-3
G-2 Identification of Implementation Under Test . A-4
G-3 Identification of Supplier . A-4
G-4 Identification of Specification . A-4
G-5 Required Procedures . A-5
G-6 Required PDUs . A-6
G-7 BIND Invocation Parameters . A-7
G-8 BIND Return Parameters . A-8
G-9 PEER-ABORT Invocation Parameters . A-9
G-10 UNBIND Invocation Parameters . A-9
G-11 UNBIND Return Parameters . A-10
G-12 EXECUTE-DIRECTIVE Invocation Parameters . A-11
G-13 EXECUTE-DIRECTIVE Acknowledgement Parameters . A-13
G-14 EXECUTE-DIRECTIVE Return Parameters . A-14
G-15 GET Invocation Parameters . A-16
G-16 GET Return Parameters . A-17
G-17 PROCESS-DATA Invocation Parameters . A-19
G-18 PROCESS-DATA Return Parameters . A-21
G-19 START Invocation Parameters . A-23
G-20 START Return Parameters . A-25
G-21 STOP Invocation Parameters . A-27
G-22 STOP Return Parameters . A-28
G-23 NOTIFY Invocation Parameters . A-29
G-24 TRANSFER-DATA Invocation Parameters . A-31
M-1 Specification of the Subcarrier Level Estimate Parameter . M-4
M-2 Specification of the Subcarrier Lock Status Parameter . M-5

CCSDS 921.1-B-1 Page xi April 2017
© ISO 2020 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 23103:2020(E)
CCSDS RECOMMENDED STANDARD FOR CSTS SPECIFICATION FRAMEWORK
1 INTRODUCTION
1.1 PURPOSE
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
Cross Support Transfer Services (CSTSes).
1.2 SCOPE
1.2.1 This Recommended Standard 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
f) the parameters associated with each operation.
1.2.2 It does not specify:
a) individual application services, implementations, or products;
b) the implementation of entities or interfaces within real systems;
c) the methods or technologies required to acquire data;
d) the methods or technologies required to provide a suitable environment for
communications; or
e) the management activities required to schedul
...

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 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
  • Draft
    190 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
  • Draft
    34 pages
    English language
    sale 15% off
ISO
ISO 26143:2021(Main)
Space data and information transfer systems — Space link extension (SLE) — Return operational control fields service specification

The purpose of this document is to define the Space Link Extension (SLE) Return Operational Control Fields (ROCF) service in conformance with the SLE Reference Model (reference [1]). The ROCF service is an SLE transfer service that delivers to a mission user all operational control fields from one master channel or one virtual channel. This document defines, in an abstract manner, the ROCF 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 ROCF service. NOTE – Reference [1] defines the Return Master Channel Operational Control Field (Rtn MC-OCF) service and the Return Virtual Channel Operational Control Field (Rtn VC-OCF) service as two distinct services. Subsequent study has indicated that it is preferable to define one service that provides the functionality of both. The ROCF 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-OCF and Rtn VC-OCF services and replacing them with the Rtn OCF service.

  • Standard
    144 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
  • Draft
    136 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
  • Draft
    143 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 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
  • Draft
    52 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
  • Draft
    365 pages
    English language
    sale 15% off
ISO
ISO 23104:2020(Main)
Space link extension — Cross support transfer service — Monitored data service

This Recommended Standard defines the Monitored Data service in terms of: a) the CSTS procedures that constitute the service; b) the extensions and refinements of the behavior of those CSTS procedures necessary to provide the transfer service; c) the extensions and refinements of standard CSTS operations associated with each of the procedures; d) the relationships among the procedures that constitute the service. 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 measure the values of monitored parameters and to detect the occurrence of events of interest; d) the methods or technologies required for communication; e) the management activities necessary to schedule, configure, and control the MD-CSTS; f) the specific parameters that are to be reported and events that are to be notified by the MD-CSTS.

  • Standard
    108 pages
    English language
    sale 15% off
ISO
ISO 18445:2016(Main)
Space data and information transfer systems — Space link extension — Application program interface for the forward CLTU service

ISO 18445:2016 Practice defines extensions to the SLE API in terms of: a) the CLTU-specific functionality provided by API components; b) the CLTU-specific interfaces provided by API components; and c) the externally visible behavior associated with the CLTU 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. ISO 18445:2016 defines only interfaces and behavior that must be provided by implementations supporting the forward CLTU service in addition to the specification in reference [5].

  • Standard
    103 pages
    English language
    sale 15% off