1、 ISO 2015 Space data and information transfer systems Standard formatted data units Structure and construction rules AMENDMENT 1 Systmes de transfert des informations et donnes spatiales Units de donnes structuration normalise (SFDU) Rgles de structure et de construction AMENDEMENT 1 INTERNATIONAL S
2、TANDARD ISO 12175 Reference number ISO 12175:1994/Amd.1:2015(E) First edition 1994-10-20 AMENDMENT 1 2015-07-01ISO 12175:1994/Amd.1:2015(E)ii ISO 2015 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2015, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this
3、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 ISOs member body in the
4、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 copyrightiso.org www.iso.org RECOMMENDATION FOR SPACE DATA SYSTEM STANDARDS BLUE BOOK May 1992 CCSDS 620.0-B-2 TMG 8/92 STANDARD FORMATTED DATA UN
5、ITS STRUCTURE AND CONSTRUCTION RULES Note: This current issue includes all updates through Technical Corrigendum 1, dated November 1996.CCSDS Recommendation for SFDUs: Structure and Construction Rules AUTHORITY Issue: Blue Book, Issue 2 Date: May 1992 Location: CCSDS Panel 2 Meeting, May 1992, Oberp
6、faffenhofen, 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 DEtudes Spatia
7、les (CNES) / France Deutsche Forschungsanstalt fr 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 o
8、bserver 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 Divis
9、ion, (Code-OS) National Aeronautics and Space Administration Washington, DC 20546, USA Issue 2 May 1992 iiiCCSDS 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
10、 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
11、 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
12、 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 sub
13、ject 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 ivCCSDS Recommendation for SFDUs: Structure and Construction Rules STATEMENT
14、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 solutio
15、ns 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
16、 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 whic
17、h 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. Sp
18、ecific 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 sho
19、uld: (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 vCCSDS Recommendation for SFDUs: Structure and Construction Rules DOCUMENT CONTROL Document Title Date Status/ Rem
20、arks CCSDS 620.0-B-1 Recommendation for Space Data System Standards: Standard Formatted Data Units - Structure and Construction Rules, Blue Book, Issue 1 Feb 1988 Issue 1 CCSDS 620.0-B-2 Recommendation for Space Data System Standards: Standard Formatted Data Units - Structure and Construction Rules,
21、 Blue Book, Issue 2 May 1992 Issue 2, see note below 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 u
22、nlabelled data objects. Issue 2 is forwards compatible with the whole of Issue 1. Issue 2 May 1992 viCCSDS 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 .
23、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 Diag
24、ram 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) 1 0 3.1.3 Class ID 1 0 3.1.4 Spare
25、 1 1 0 3.1.5 Spare 2 1 0 3.1.6 Length . 1 0 3.1.7 Structure Diagram . 1 1 3.2 LVO LABEL Specification - Version ID = 2 1 1 3.2.1 Version ID 1 1 3.2.2 Authority and Description Identifier (ADID) . 1 1 3.2.2.1 Control Authority Identifier (CAID) 1 1 3.2.2.2 Data Description Identifier (DDID) 1 2 3.2.3
26、 Class ID 1 2 3.2.4 Spare 1 1 2 3.2.5 Spare 2 1 2 3.2.6 Length . 1 2 3.2.7 Structure Diagram . 1 2 3.3 LVO LABEL Specification - Version ID = 3 1 3 3.3.1 Version ID 1 3 3.3.2 Authority and Description Identifier (ADID) . 1 3 3.3.2.1 Control Authority Identifier (CAID) 1 3 3.3.2.2 Data Description Id
27、entifier (DDID) 1 3 3.3.3 Class ID 1 4 3.3.4 Delimitation . 1 4 3.3.4.1 Length (Specified in ASCII) - Delimitation ID = A . 1 4 3.3.4.2 Length (Specified in Binary) - Delimitation ID = B . 1 5 Issue 2 May 1992 viiCCSDS Recommendation for SFDUs: Structure and Construction Rules 3.3.4.3 Marker Pattern
28、 - Delimitation ID = S . 1 5 3.3.4.4 Sequential End-of-File (EOF) - Delimitation ID = E 1 6 3.3.4.5 Contiguous End-of-File (EOF) - Delimitation ID = C 1 6 3.3.4.6 Shared End-of-File (EOF) - Delimitation ID = F . 1 6 3.3.5 Spare 1 7 3.3.6 Delimitation Parameter . 1 7 3.3.7 Structure Diagram . 1 7 4 C
29、LASS ID SPECIFICATIONS . 1 8 4.1 Structure Classes 1 8 4.1.1 Exchange Data Unit - Class ID = Z 1 8 4.1.2 Application Data Unit - Class ID = U 1 9 4.1.3 Description Data Unit - Class ID = F 1 9 4.2 Service Classes 1 9 4.2.1 Replacement Service Object - Class ID = R 1 9 4.2.2 Data Administration Servi
30、ce Object - Class ID = C . 1 9 4.3 Data Classes 2 0 4.3.1 Application Data Object - Class ID = I 2 0 4.3.2 Supplementary Data Object - Class ID = S . 2 0 4.3.3 Data Description Record Object - Class ID = D 2 0 4.3.4 Data Entity Dictionary Object - Class ID = E 2 0 4.3.5 Catalogue Attribute Object -
31、Class ID = K 2 0 4.3.6 Volume Preparation Data Object - Class ID = V . 2 0 4.4 Overview of Structure Class IDs 2 1 5 CCSDS ADID SPECIFICATIONS 2 2 5.1 Specification for ADID = CCSD0001 . 2 2 5.2 Specification for ADID = CCSD0003 . 2 2 5.3 Specification for ADID = CCSD0004 . 2 4 5.4 Specification for
32、 ADID = CCSD0005 . 2 5 5.5 Specification for ADID = CCSD0009 . 2 6 6 COMBINATION OF ADIDS AND CLASS IDS 2 7 Annex A: Acronyms . 3 0 Annex B: Glossary of Terms . 3 2 Annex C: ASN.1 Definitions 3 4 C.1 ASN.1 Definition of the LVO Structure . 3 4 C.2 ASN.1 Definition of the DDR for ADID = CCSD0001 . 4
33、0 C.3 ASN.1 Definition of the DDR for ADID = CCSD0003 . 4 1 C.4 ASN.1 Definition of the DDR for ADID = CCSD0004 . 4 2 C.5 ASN.1 Definition of the DDR for ADID = CCSD0005 . 4 3 C.6 ASN.1 Definition of the DDR for ADID = CCSD0009 . 4 4 Annex D: ASCII 2) A method of organising data objects into a hiera
34、rchial structure to provide a complete set of information. This includes referencing of data objects that are defined externally, such as files. 1.2 Applicability This Recommendation serves as a guideline for the development of compatible agency standards in the field of digital data interchange. Th
35、e specifications in this document are to be invoked through the normal standards program of each member agency and are applicable, at a minimum, to those missions and services for which cross support based on the need for open system data interchange is anticipated. To be compatible with the CCSDS S
36、FDU concept, an agency must use the structures as defined by this Recommendation. 1.3 Recommended Approach to Reading the Document A proper understanding of this Recommendation requires familiarity with the SFDU concept, the rationale underlying the various product building and packaging techniques
37、and the specific terminology used in this document. It is recommended that Reference 3 be read prior to this Recommendation as it describes both the requirements and the rationale behind the SFDU concept, and introduces the technical material contained in this Recommendation through examples. The do
38、cument is structured as follows: Section 2 gives a general overview of the SFDU concept, and introduces the basic data structuring components; Section 3 describes the details of the LABEL-VALUE structure used by the SFDU concept and defines all its sub-fields; Section 4 describes CCSDS defined Class IDs and, where applicable, the relationships between them; Issue 2 May 1992 1
