iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO 20104:2015

(Main)

Space data and information transfer systems — Producer-Archive Interface Specification (PAIS)

Space data and information transfer systems — Producer-Archive Interface Specification (PAIS)

ISO 20104:2015 is to provide a standard method for formally defining the digital information objects to be transferred by an information Producer to an Archive and for effectively packaging these objects in the form of Submission Information Packages (SIPs). This supports effective transfer and validation of SIP data. ISO 20104:2015 fits into the context defined by: ? The Reference Model for an Open Archival Information System (OAIS) Recommended Standard (see reference [3]). ? The Producer-Archive Interface Methodology Abstract Standard (PAIMAS) Recommended Standard (see reference [2]). ? The XML Formatted Data Unit (XFDU) Structure and Construction Rules Recommended Standard (see reference [1]). The PAIMAS Recommended Standard (see reference [2]) defines a methodology based on the four following phases: Preliminary, Formal Definition, Transfer, Validation. ISO 20104:2015 applies specifically to the implementation of the main part of the Formal Definition Phase and the Transfer Phase, taking into account part of the Validation Phase. The proposed implementation should help in the automation and management of the Transfer and Validation Phases. The proposed implementation may also be used, to some extent, for the Preliminary Phase. ISO 20104:2015 does not exclude other PAIMAS implementation Recommended Standards.

Systèmes de transfert des informations et données spatiales — Spécification de l'interface entre producteur et archives (PAIS)

General Information

Status
Published
Publication Date
10-Aug-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
9093 - International Standard confirmed
Completion Date
14-Nov-2023
Ref Project

Relations

Consolidated By
ISO 17640:2018 - Non-destructive testing of welds — Ultrasonic testing — Techniques, testing levels, and assessment
Effective Date
06-Jun-2022

Buy Standard

ISO 20104:2015 - Space data and information transfer systems -- Producer-Archive Interface Specification (PAIS)ISO 20104:2015 - Space data and information transfer systems -- Producer-Archive Interface Specification (PAIS)
PreviousNext
Standard
ISO 20104:2015 - Space data and information transfer systems -- Producer-Archive Interface Specification (PAIS)
English language
94 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 20104
First edition
2015-08-15
Space data and information transfer
systems — Producer-Archive Interface
Specification (PAIS)
Systèmes de transfert des informations et données spatiales —
Spécification de l’interface entre producteur et archives (PAIS)
Reference number
ISO 20104:2015(E)
©
ISO 2015

---------------------- Page: 1 ----------------------
ISO 20104:2015(E)

COPYRIGHT PROTECTED DOCUMENT
© 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

---------------------- Page: 2 ----------------------
ISO 20104:2015(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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
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.
ISO 20104 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as
CCSDS 651.1-B-1, February 2014) and was adopted (without modifications except those stated in clause 2 of
this International Standard) by Technical Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee
SC 13, Space data and information transfer systems.

© ISO 2015 – All rights reserved iii

---------------------- Page: 3 ----------------------
Recommendation for Space Data System Standards
PRODUCER-ARCHIVE
INTERFACE
SPECIFICATION (PAIS)
RECOMMENDED STANDARD
CCSDS 651.1-B-1
BLUE BOOK
February 2014

---------------------- Page: 4 ----------------------
ISO 20104:2015(E)
RECOMMENDED STANDARD FOR PRODUCER-ARCHIVE INTERFACE SPECIFICATION
AUTHORITY



Issue: Recommended Standard, Issue 1
Date: February 2014
Location: Washington, DC, USA

This document has been approved for publication by the Management Council of the
Consultative Committee for Space Data Systems (CCSDS) and represents the consensus
technical agreement of the participating CCSDS Member Agencies. The procedure for
review and authorization of CCSDS documents is detailed in Organization and Processes for
the Consultative Committee for Space Data Systems (CCSDS A02.1-Y-3), and the record of
Agency participation in the authorization of this document can be obtained from the CCSDS
Secretariat at the address below.


This document is published and maintained by:

CCSDS Secretariat
Space Communications and Navigation Office, 7L70
Space Operations Mission Directorate
NASA Headquarters
Washington, DC 20546-0001, USA
CCSDS 651.1-B-1 Page i February 2014
© ISO 2015 – All rights reserved

---------------------- Page: 5 ----------------------
ISO 20104:2015(E)
RECOMMENDED STANDARD FOR PRODUCER-ARCHIVE INTERFACE SPECIFICATION
STATEMENT OF INTENT
The Consultative Committee for Space Data Systems (CCSDS) is an organization officially
established by the management of its members. The Committee meets periodically to address
data systems problems that are common to all participants, and to formulate sound technical
solutions to these problems. Inasmuch as participation in the CCSDS is completely
voluntary, the results of Committee actions are termed Recommended Standards and are
not considered binding on any Agency.
This Recommended Standard is issued by, and represents the consensus of, the CCSDS
members. Endorsement of this Recommendation is entirely voluntary. Endorsement,
however, indicates the following understandings:
o Whenever a member
...

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 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 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 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 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 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 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 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 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 23103:2020(Main)
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.

  • Standard
    329 pages
    English language
    sale 15% off