BS ISO 18444-2016 Space data and information transfer systems Space link extension Application program interface for return operational control fields service《空间数据和信息传输系统 空间链接扩展 回程.pdf

1、BS ISO 18444:2016Space data and informationtransfer systems Spacelink extension Applicationprogram interface for returnoperational control fieldsserviceBSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO 18444:2016 BRITISH STANDARDNational forewordThis British Sta

2、ndard is the UK implementation of ISO 18444:2016. It supersedes BS ISO 18444:2013 which is withdrawn. The UK participation in its preparation was entrusted to TechnicalCommittee ACE/68, Space systems and operations.A list of organizations represented on this committee can beobtained on request to it

3、s secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2016. Published by BSI Standards Limited 2016ISBN 978 0 580 93382 0ICS 49.140Compliance with a British Standard cann

4、ot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 30 November 2016.Amendments/Corrigenda issued since publicationDate Text affectedBS ISO 18444:2016Reference number ISO 18444:2016(E) ISO 2016INTERNATIONAL

5、 STANDARDISO 18444Space data and information transfer systems Space link extension Application program interface for return operational control fields service Systmes de transfert des informations et donnes spatiales Extension de liaisons spatiales Interface du programme dapplication pour service de

6、s champs de contrle de retour oprationnel Second edition 2016-11-15BS ISO 18444:2016ISO 18444:2016(E) COPYRIGHT PROTECTED DOCUMENT ISO 2016 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

7、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 country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Gene

8、va, Switzerland Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2016 All rights reservedBS ISO 18444:2016ISO 18444:2016(E) ISO 2016 All rights reserved iiiForeword ISO (the International Organization for Standardization) is a worldwide fe

9、deration 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 com

10、mittee. 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

11、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. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, P

12、art 2. 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 d

13、ocument will be in the Introduction and/or on the ISO list of patent declarations received. 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 on the meaning of ISO specific terms and e

14、xpressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information ISO 18444 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as

15、CCSDS 915.5-M-2, September 2015) 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. This second edition cancels and repl

16、aces the first edition (ISO 18444:2013), which has been technically revised. BS ISO 18444:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE ROCF SERVICE CCSDS 915.5-M-2 Page ii September 2015 STATEMENT OF INTENT The Consultative Committee for Space Data Systems (CCSDS) is an organization officially es

17、tablished 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 ac

18、tions are termed Recommendations and are not in themselves considered binding on any Agency. CCSDS Recommendations take two forms: Recommended Standards that are prescriptive and are the formal vehicles by which CCSDS Agencies create the standards that specify how elements of their space mission sup

19、port infrastructure shall operate and interoperate with others; and Recommended Practices that are more descriptive in nature and are intended to provide general guidance about how to approach a particular problem associated with space mission support. This Recommended Practice is issued by, and rep

20、resents the consensus of, the CCSDS members. Endorsement of this Recommended Practice is entirely voluntary and does not imply a commitment by any Agency or organization to implement its recommendations in a prescriptive sense. No later than five years from its date of issuance, this Recommended Pra

21、ctice 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 newdirections; or (3) be retired or canceled.In those instances when a new version of a Recommended Practice is issu

22、ed, existing CCSDS-related member Practices and implementations are not negated or deemed to be non-CCSDS compatible. It is the responsibility of each member to determine when such Practices or implementations are to be modified. Each member is, however, strongly encouraged to direct planning for it

23、s new Practices and implementations towards the later version of the Recommended Practice. ISO 18444:2016(E) ISO 2016 All rights reservedBS ISO 18444:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE ROCF SERVICE CCSDS 915.5-M-2 Page iii September 2015 FOREWORD This document is a technical Recommended

24、 Practice for use in developing ground systems for space missions and has been prepared by the Consultative Committee for Space Data Systems (CCSDS). The Application Program Interface described herein is intended for missions that are cross-supported between Agencies of the CCSDS. This Recommended P

25、ractice specifies service type-specific extensions of the Space Link Extension Application Program Interface for Transfer Services specified by CCSDS (reference 3). It allows implementing organizations within each Agency to proceed with the development of compatible, derived Standards for the ground

26、 systems that are within their cognizance. Derived Agency Standards may implement only a subset of the optional features allowed by the Recommended Practice and may incorporate features not addressed by the Recommended Practice. Attention is drawn to the possibility that some of the elements of this

27、 document may be the subject of patent rights. CCSDS has processes for identifying patent issues and for securing from the patent holder agreement that all licensing policies are reasonable and non-discriminatory. However, CCSDS does not have a patent law staff, and CCSDS shall not be held responsib

28、le for identifying any or all such patent rights. Through the process of normal evolution, it is expected that expansion, deletion, or modification of this document may occur. This Recommended Standard is therefore subject to CCSDS document management and change control procedures, which are defined

29、 in Organization and Processes for the Consultative Committee for Space Data Systems (CCSDS A02.1-Y-4). Current versions of CCSDS documents are maintained at the CCSDS Web site: http:/www.ccsds.org/ Questions relating to the contents or status of this document should be sent to the CCSDS Secretariat

30、 at the e-mail address indicated on page i. ISO 18444:2016(E) ISO 2016 All rights reservedBS ISO 18444:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE ROCF SERVICE CCSDS 915.5-M-2 Page iv September 2015 At time of publication, the active Member and Observer Agencies of the CCSDS were: Member Agencie

31、s Agenzia Spaziale Italiana (ASI)/Italy. Canadian Space Agency (CSA)/Canada. Centre National dEtudes Spatiales (CNES)/France. China National Space Administration (CNSA)/Peoples Republic of China. Deutsches Zentrum fr Luft- und Raumfahrt (DLR)/Germany. European Space Agency (ESA)/Europe. Federal Spac

32、e Agency (FSA)/Russian Federation. Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil. Japan Aerospace Exploration Agency (JAXA)/Japan. National Aeronautics and Space Administration (NASA)/USA. UK Space Agency/United Kingdom.Observer Agencies Austrian Space Agency (ASA)/Austria. Belgian Federal

33、 Science Policy Office (BFSPO)/Belgium. Central Research Institute of Machine Building (TsNIIMash)/Russian Federation. China Satellite Launch and Tracking Control General, Beijing Institute of Tracking andTelecommunications Technology (CLTC/BITTT)/China. Chinese Academy of Sciences (CAS)/China. Chin

34、ese Academy of Space Technology (CAST)/China. Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia. Danish National Space Center (DNSC)/Denmark. Departamento de Cincia e Tecnologia Aeroespacial (DCTA)/Brazil. Electronics and Telecommunications Research Institute (ETRI)/Kore

35、a. European Organization for the Exploitation of Meteorological Satellites(EUMETSAT)/Europe. European Telecommunications Satellite Organization (EUTELSAT)/Europe. Geo-Informatics and Space Technology Development Agency (GISTDA)/Thailand. Hellenic National Space Committee (HNSC)/Greece. Indian Space

36、Research Organization (ISRO)/India. Institute of Space Research (IKI)/Russian Federation. KFKI Research Institute for Particle differentiatesapplicability by SLE service specification version; updates references.NOTE Substantive changes from the previous issue are marked with change bars in the insi

37、de margin. ISO 18444:2016(E) ISO 2016 All rights reservedBS ISO 18444:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE ROCF SERVICE CCSDS 915.5-M-2 Page vi September 2015 CONTENTS Section Page 1 INTRODUCTION 1-1 1.1 PURPOSE . 1-1 1.2 SCOPE 1-1 1.3 APPLICABILITY . 1-2 1.4 RATIONALE 1-2 1.5 DOCUMENT ST

38、RUCTURE . 1-3 1.6 DEFINITIONS, NOMENCLATURE, AND CONVENTIONS . 1-5 1.7 REFERENCES . 1-8 2 OVERVIEW . 2-1 2.1 INTRODUCTION 2-1 2.2 PACKAGE ROCF SERVICE INSTANCES 2-1 2.3 PACKAGE ROCF OPERATIONS 2-5 2.4 SECURITY ASPECTS OF THE SLE ROCF TRANSFER SERVICE . 2-7 3 ROCF SPECIFIC SPECIFICATIONS FOR API COMP

39、ONENTS . 3-1 3.1 API SERVICE ELEMENT . 3-1 3.2 SLE OPERATIONS 3-9 3.3 SLE APPLICATION 3-9 3.4 SEQUENCE OF DIAGNOSTIC CODES 3-10 ANNEX A ROCF SPECIFIC INTERFACES (NORMATIVE) A-1 ANNEX B ACRONYMS (INFORMATIVE) .B-1 ANNEX C INFORMATIVE REFERENCES (INFORMATIVE) C-1 Figure 1-1 SLE Services and SLE API Do

40、cumentation . 1-4 2-1 ROCF Service Instances . 2-2 2-2 ROCF Operation Object Interfaces . 2-6 Table 2-1 ROCF Configuration Parameters 2-4 2-2 ROCF Status Information . 2-5 2-3 Mapping of ROCF Operations to Operation Object Interfaces 2-7 ISO 18444:2016(E) ISO 2016 All rights reservedBS ISO 18444:201

41、6CCSDS RECOMMENDED PRACTICE: API FOR THE SLE ROCF SERVICE CCSDS 915.5-M-2 Page 1-1 September 2015 1 INTRODUCTION 1.1 PURPOSE The Recommended Practice Space Link ExtensionApplication Program Interface for Transfer ServicesCore Specification (reference 3) specifies a C+ API for CCSDS Space Link Extens

42、ion Transfer Services. The API is intended for use by application programs implementing SLE transfer services. Reference 3 defines the architecture of the API and the functionality on a generic level, which is independent of specific SLE services and communication technologies. It is thus necessary

43、to add service type-specific specifications in supplemental Recommended Practices. The purpose of this document is to specify extensions to the API needed for support of the Return Operational Control Fields (ROCF) service defined in reference 2. 1.2 SCOPE This specification defines extensions to th

44、e SLE API in terms of: a) the ROCF-specific functionality provided by API components;b) the ROCF-specific interfaces provided by API components; andc) the externally visible behavior associated with the ROCF interfaces exported by thecomponents.It does not specify: a) individual implementations or p

45、roducts;b) the internal design of the components; andc) the technology used for communications.This specification defines only interfaces and behavior that must be provided by implementations supporting the Return Operational Control Fields service in addition to the specification in reference 3. IS

46、O 18444:2016(E) ISO 2016 All rights reservedBS ISO 18444:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE ROCF SERVICE CCSDS 915.5-M-2 Page 1-2 September 2015 1.3 APPLICABILITY The Application Program Interface specified in this document supports two generations of Return Operational Control Fields s

47、ervice, namely: a) Generation 2 identified by the version number 1 in the BIND operation, as specifiedby reference C8;b) Generation 3 identified by the version number 4 in the BIND operation, as specifiedby reference 2.NOTES 1 The use of the term Generation follows the definition in the API Core Spe

48、cification (reference 3) where it is used to classify all SLE Transfer Services. 2 Support for Generation 1 is not valid in this book because the ROCF initial issue was written as part of Generation 2 of the RAF, RCF and CLTU specific version 1 recommendations. Support for Generation 2 of the servic

49、e is included for backward compatibility purposes for a limited time and may not be continued in future versions of this specification. Provisions within this Recommended Practice that are specific for a specific generation are marked as: G2: for provisions specific to Generation 2; G3: for provisions specific to Generation 3.Provisions that apply to all generations are not marked. 1.4 RATIONALE This Recommended Practice specifies the mapping of the ROCF service specificati