BS ISO 18443-2016 Space data and information transfer systems Space link extension Application program interface for return channel frames service《空间数据和信息传输系统 空间链路扩展 返回信道帧服务的应用程序接口.pdf

1、BS ISO 18443:2016Space data and informationtransfer systems Spacelink extension Applicationprogram interface for returnchannel frames serviceBSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO 18443:2016 BRITISH STANDARDNational forewordThis British Standard is th

2、e UK implementation of ISO 18443:2016. It supersedes BS ISO 18443: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 its secretary

3、.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 93381 3ICS 49.140Compliance with a British Standard cannot confer i

4、mmunity 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 18443:2016Reference number ISO 18443:2016(E) ISO 2016INTERNATIONAL STANDARDIS

5、O 18443Space data and information transfer systems Space link extension Application program interface for return channel frames service Systmes de transfert des informations et donnes spatiales Extension de liaisons spatiales Interface du programme dapplication pour service de rseau pour liaison ret

6、our Second edition 2016-11-15BS ISO 18443:2016ISO 18443: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 mechanical, including photocopying, or

7、 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, Geneva, Switzerland Tel. + 41 22 749 01 11

8、 Fax + 41 22 749 09 47 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2016 All rights reservedBS ISO 18443:2016ISO 18443:2016(E) ISO 2016 All rights reserved iiiForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies

9、(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, g

10、overnmental 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 mai

11、ntenance 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, Part 2. www.iso.org/directives Attentio

12、n 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 an

13、d/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 expressions related to conformity asses

14、sment, 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 18443 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as CCSDS 915.2-M-2, September 2015) and w

15、as 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 replaces the first edition (ISO 18443:2013

16、), which has been technically revised. BS ISO 18443:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE RCF SERVICE CCSDS 915.2-M-2 Page ii September 2015 STATEMENT OF INTENT The Consultative Committee for Space Data Systems (CCSDS) is an organization officially established by the management of its memb

17、ers. 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 Recommendations and ar

18、e 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 support infrastructure shall operate and i

19、nteroperate 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 represents the consensus of, the CCSDS mem

20、bers. 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 Practice will be reviewed by the CCSDS to

21、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 issued, existing CCSDS-related member Pract

22、ices 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 its new Practices and implementations tow

23、ards the later version of the Recommended Practice. ISO 18443:2016(E) ISO 2016 All rights reservedBS ISO 18443:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE RCF SERVICE CCSDS 915.2-M-2 Page iii September 2015 FOREWORD This document is a technical Recommended Practice for use in developing ground s

24、ystems 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 Practice specifies service type-specific

25、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 systems that are within their cognizanc

26、e. 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 document may be the subject of patent r

27、ights. 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 responsible for identifying any or all such paten

28、t 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 in Organization and Processes for the C

29、onsultative 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 at the e-mail address indicated on page

30、 i. ISO 18443:2016(E) ISO 2016 All rights reservedBS ISO 18443:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE RCF SERVICE CCSDS 915.2-M-2 Page iv September 2015 At time of publication, the active Member and Observer Agencies of the CCSDS were: Member Agencies Agenzia Spaziale Italiana (ASI)/Italy.

31、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 Space Agency (FSA)/Russian Federation. Instit

32、uto 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 Science Policy Office (BFSPO)/Belgium. C

33、entral 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. Chinese Academy of Space Technology (CAST)/Ch

34、ina. 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)/Korea. European Organization for the Exploita

35、tion 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 Research Organization (ISRO)/India. Insti

36、tute of Space Research (IKI)/Russian Federation. KFKI Research Institute for Particle differentiatesapplicability by SLEservice specificationversion; updates references.NOTE Substantive changes from the previous issue are marked with change bars in the inside margin. ISO 18443:2016(E) ISO 2016 All r

37、ights reservedBS ISO 18443:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE RCF SERVICE CCSDS 915.2-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 STRUCTURE . 1-3 1.6 DEFINITIONS, NOMENCLATURE,

38、 AND CONVENTIONS . 1-5 1.7 REFERENCES . 1-8 2 OVERVIEW . 2-1 2.1 INTRODUCTION 2-1 2.2 PACKAGE RCF SERVICE INSTANCES 2-1 2.3 PACKAGE RCF OPERATIONS . 2-5 2.4 SECURITY ASPECTS OF THE SLE RCF TRANSFER SERVICE 2-8 3 RCF SPECIFIC SPECIFICATIONS FOR API COMPONENTS 3-1 3.1 API SERVICE ELEMENT . 3-1 3.2 SLE

39、 OPERATIONS 3-6 3.3 SLE APPLICATION 3-7 3.4 SEQUENCE OF DIAGNOSTIC CODES 3-7 ANNEX A RCF 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 Documentation . 1-4 2-1 RCF Service Instances 2-2 2-

40、2 RCF Operation Object Interfaces 2-7 Table 2-1 RCF Configuration Parameters . 2-4 2-2 RCF Status Information 2-5 2-3 Mapping of RCF Operations to Operation Object Interfaces . 2-6 ISO 18443:2016(E) ISO 2016 All rights reservedBS ISO 18443:2016CCSDS RECOMMENDED PRACTICE: API FOR THE SLE RCF SERVICE

41、CCSDS 915.2-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 Extension Transfer Services. The API is intended for use by appl

42、ication 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 to add service type-specific specifications in supplementa

43、l Recommended Practices. The purpose of this document is to specify extensions to the API needed for support of the Return Channel Frames (RCF) service defined in reference 2. 1.2 SCOPE This Recommended Practice defines extensions to the SLE API in terms of: a) the RCF-specific functionality provide

44、d by API components;b) the RCF-specific interfaces provided by API components; andc) the externally visible behavior associated with the RCF interfaces exported by thecomponents.It does not specify: a) individual implementations or products;b) the internal design of the components; andc) the technol

45、ogy used for communications.This Recommended Practice defines only interfaces and behavior that must be provided by implementations supporting the Return Channel Frames service in addition to the specification in reference 3. ISO 18443:2016(E) ISO 2016 All rights reservedBS ISO 18443:2016CCSDS RECOM

46、MENDED PRACTICE: API FOR THE SLE RCF SERVICE CCSDS 915.2-M-2 Page 1-2 September 2015 1.3 APPLICABILITY The Application Program Interface specified in this document supports three versions of the Return Channel Frames service, namely: a) Generation 1 identified by the version number 1 in the BIND ope

47、ration, as specified by reference C2; b) Generation 2 identified by the version number 2 in the BIND operation, as specified by reference C3; c) Generation 3 identified by the version number 4 in the BIND operation, as specified by reference 2. NOTE The use of the term Generation follows the definit

48、ion in the API Core Specification (reference 3) where it is used to classify all SLE Transfer Services. Support for Generation 1 and Generation 2 of this service is included for backward compatibility purposes for a limited time and may not be continued in future versions of this specification. Supp

49、ort for Generation 1 (i.e., version 1 of the RCF service) implies that SLE API implementations of this specification are able to interoperate with peer SLE systems that comply with the specification of the Transport Mapping Layer (TML) in Specification of a SLE API Proxy for TCP/IP and ASN.1, ESOC, SLES-SW-API-0002-TOS-GCI, Issue 1.1, February 2001. For Generation 2 and 3 of these services, SLE API implementations of this specification are able to interoperate with peer SLE sys